Tongyi-MAI · image

Z-Image

Tongyi-MAI/Z-Image

Z-Image at Q4_K_M is exactly 5,066,995,776 bytes (4.72 GiB / 5.07 GB) — an effective 6.586 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
6.2B
Architecture
lumina2
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K3.74 GiB4,013,115,4565.216unsloth
Q3_K_S4.06 GiB4,360,190,0165.667unsloth
Q3_K_M4.25 GiB4,559,946,8165.927unsloth
Q4_04.27 GiB4,585,244,7365.960unsloth
Q3_K_L4.29 GiB4,604,183,6165.984unsloth
Q4_K_S4.46 GiB4,787,443,7766.223unsloth
Q4_14.52 GiB4,850,665,5366.305unsloth
Q4_K_M4.72 GiB5,066,995,7766.586unsloth
Q5_04.90 GiB5,263,542,3366.841unsloth
Q5_K_S4.93 GiB5,289,562,1766.875unsloth
Q5_15.15 GiB5,528,963,1367.186unsloth
Q5_K_M5.20 GiB5,578,099,7767.250unsloth
Q6_K5.68 GiB6,101,921,8567.931unsloth
Q8_06.73 GiB7,224,707,1369.390unsloth
BF1611.47 GiB12,311,939,13616.003unsloth
F1611.47 GiB12,311,939,13616.003unsloth

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
text encoder7.49 GiB39%yes — the usual first VRAM saving
vae0.16 GiB1%no, must be resident
denoiser11.46 GiB60%no, must be resident
Full pipeline19.11 GiBresident if nothing is offloaded

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.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

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

Architecture

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.

Questions people ask

How much VRAM does Z-Image need?
Q4_K_M is exactly 5,066,995,776 bytes (4.72 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 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.