Z-Image-Turbo_clear
VAE: Z-Image_clear_vae
Compare to Z-Image-Turbo (Original)
Z-Image-Turbo_clear | Z-Image-Turbo


The Z-Image-Turbo_clear model is a fine-tuned version of Z-Image-Turbo that improves details compared to the original.
For better results, please use it with the dedicated VAE, Z-Image_clear_vae.
Model Format and Quality
Generally, model size and image quality are proportional.
FP32 > FP16 ≒ BF16 > MXFP8 > FP8_svd_scaled > FP8
Generation time varies greatly depending on whether the model can be loaded into VRAM, and the supported formats are determined by the GPU generation.
MXFP8 is the latest standard designed for the RTX 5000 series. On unsupported GPUs, however, fallback mechanisms will actually slow down processing, so their use is not highly recommended.
For a comparison of image quality and generation time by format, please see this page.
If you are unsure which precision to use, it is safest to choose the BF16 format.
Recomended Settings
Sampler:
euler
res_multistep
Scheduler: beta
Steps: 9
ModelSamplingAuraFlow: shift 7.5 (3-9)
Upscaler
your choice, examples:
Tips (External Sites)
License
Description
FAQ
Comments (6)
pre-RTX 2000 getting black outputs
FB16
@Kongyiji12825ijjj
Yes, the FP16 format is inherently less stable than BF16, so this kind of issue can sometimes occur depending on your environment (especially with older GPUs).
I am unsure whether your specific defect is originating from the Sampler or the VAE, but if you can successfully generate images using the FP32 or BF16 format, please use one of those instead.
SDXL VAE case: https://huggingface.co/madebyollin/sdxl-vae-fp16-fix
where can I find a workflow for this?
Uploaded a PNG image containing the ComfyUI workflow to Hugging Face.
https://huggingface.co/easygoing0114/Z-Image-Turbo_clear/blob/main/README.md#workflow
@easygoing0114 great. thanks!

