tencent · image

HunyuanImage-2.1

tencent/HunyuanImage-2.1

HunyuanImage-2.1 at Q4_K_M is exactly 9,236,273,920 bytes (8.60 GiB / 9.24 GB) — an effective 4.234 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
17.5B
Architecture
pig
null layers
Context
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K5.26 GiB5,643,631,3602.587QuantStack
Q2_K_S6.06 GiB6,512,021,7282.985calcuis
Q2_K6.14 GiB6,596,331,1363.023QuantStack
Q3_K_S6.64 GiB7,128,451,8403.267QuantStack
Q3_K_M6.80 GiB7,304,968,9603.348QuantStack
IQ2_XS6.98 GiB7,498,592,0323.437calcuis
IQ2_M7.12 GiB7,643,098,9123.503calcuis
Q3_K_S7.70 GiB8,267,586,1763.790QuantStack
Q3_K_M7.77 GiB8,339,036,8003.822QuantStack
Q3_K_S8.42 GiB9,045,262,8164.146calcuis
Q4_K_S8.45 GiB9,070,140,1604.157QuantStack
Q4_08.45 GiB9,070,140,1604.157QuantStack
Q4_K_M8.60 GiB9,236,273,9204.234QuantStack
Q3_K_L9.16 GiB9,834,590,8804.508calcuis
Q4_19.30 GiB9,983,875,8404.576QuantStack
Q4_09.80 GiB10,521,312,8964.823QuantStack
Q4_K_S9.80 GiB10,527,735,4244.825QuantStack
Q4_K_M9.92 GiB10,653,777,5364.883QuantStack
Q5_010.15 GiB10,897,611,5204.995QuantStack
Q5_K_S10.15 GiB10,897,611,5204.995QuantStack
Q5_K_M10.31 GiB11,074,128,6405.076QuantStack
Q4_110.79 GiB11,581,890,1765.309QuantStack
Q5_111.00 GiB11,811,347,2005.414QuantStack
Q5_011.77 GiB12,642,467,4565.795QuantStack
Q5_K_S11.77 GiB12,642,467,4565.795QuantStack
Q5_K_M11.84 GiB12,710,706,8165.826QuantStack
Q6_K11.96 GiB12,839,299,8405.885QuantStack
Q5_112.76 GiB13,703,044,7366.281QuantStack
Q6_K13.87 GiB14,896,194,1766.828QuantStack
Q8_015.26 GiB16,380,025,6007.508QuantStack
IQ3_XXS2 shards16.25 GiB17,446,890,6247.997calcuis
IQ3_S2 shards16.52 GiB17,735,904,3848.130calcuis
Q8_017.70 GiB19,005,931,1368.712QuantStack
Q4_K_S2 shards20.15 GiB21,633,729,4089.916calcuis
Q5_K_S2 shards24.16 GiB25,944,851,32811.892calcuis
BF1628.02 GiB30,086,060,80013.790QuantStack
F1628.02 GiB30,086,060,80013.790QuantStack
F163 shards36.54 GiB39,237,175,71217.985calcuis
Q2_K6 shards37.85 GiB40,643,683,90418.630calcuis
Q3_K_M5 shards39.63 GiB42,553,362,75219.505calcuis

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
vae1.51 GiB100%no, must be resident
Full pipeline1.51 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 9.14 GiB. The real file is 8.60 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
Attention heads
KV heads
Head dim
Hidden size
Vocab
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does HunyuanImage-2.1 need?
Q4_K_M is exactly 9,236,273,920 bytes (8.60 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of HunyuanImage-2.1 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.