Comfy-Org · text

z_image_turbo

Comfy-Org/z_image_turbo

z_image_turbo at Q4_K_M is exactly 4,511,501,376 bytes (4.20 GiB / 4.51 GB)

From the file· summed from 1 file(s)
Parameters
84M
Architecture
pig
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
F160.16 GiB167,788,73616.014gguf-org
Q2_K3.14 GiB3,374,477,376gguf-org
Q3_K_S3.53 GiB3,790,810,176gguf-org
Q3_K_M3.69 GiB3,967,066,176gguf-org
Q3_K_L3.85 GiB4,132,954,176gguf-org
Q4_K_S4.04 GiB4,335,245,376gguf-org
Q4_K_M4.20 GiB4,511,501,376gguf-org
Q4_14.52 GiB4,850,650,176gguf-org
Q5_K_S4.68 GiB5,023,910,976gguf-org
Q5_K_M4.83 GiB5,189,798,976gguf-org
Q5_04.83 GiB5,189,798,976gguf-org
Q5_15.15 GiB5,528,947,776gguf-org
Q6_K5.50 GiB5,910,490,176gguf-org
IQ4_XS2 shards6.03 GiB6,479,583,808gguf-org
Q4_02 shards6.31 GiB6,774,843,904gguf-org
IQ4_NL2 shards6.31 GiB6,774,854,208gguf-org
Q8_02 shards10.71 GiB11,499,170,304gguf-org

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 0.04 GiB. The real file is 4.20 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_turbo need?
Q4_K_M is exactly 4,511,501,376 bytes (4.20 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.