Z-Image-Turbo

The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory.

We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.

Measured by a third party on their own hardware. We reproduce these figures with attribution; they are not ours and we have not verified the runs. Source: vladmandic-sd-data-benchmark.

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 3.22 GiB. The real file is 4.64 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

How much VRAM does Z-Image-Turbo need?

Q4_K_M is exactly 4,981,532,736 bytes (4.64 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.

Which quantization of Z-Image-Turbo should I use?

Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.