tencent · video

HunyuanVideo-1.5

tencent/HunyuanVideo-1.5

HunyuanVideo-1.5 at Q4_K_M is exactly 5,090,407,648 bytes (4.74 GiB / 5.09 GB) — an effective 4.891 bits per weight, not the nominal 4.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K_S4.58 GiB4,920,538,3364.728jayn7
Q4_K_S4.58 GiB4,920,538,3364.728jayn7
Q4_K_S4.58 GiB4,920,538,3364.728jayn7
Q4_K_S4.58 GiB4,920,538,3364.728jayn7
Q4_K_S4.58 GiB4,920,538,3364.728jayn7
Q4_K_M4.74 GiB5,090,407,6484.891jayn7
Q4_K_M4.74 GiB5,090,407,6484.891jayn7
Q4_K_M4.74 GiB5,090,407,6484.891jayn7
Q4_K_M4.74 GiB5,090,407,6484.891jayn7
Q4_K_M4.74 GiB5,090,407,6484.891jayn7
Q5_K_S5.53 GiB5,940,802,7845.708jayn7
Q5_K_S5.53 GiB5,940,802,7845.708jayn7
Q5_K_S5.53 GiB5,940,802,7845.708jayn7
Q5_K_S5.53 GiB5,940,802,7845.708jayn7
Q5_K_S5.53 GiB5,940,802,7845.708jayn7
Q5_K_M5.70 GiB6,121,288,9285.881jayn7
Q5_K_M5.70 GiB6,121,288,9285.881jayn7
Q5_K_M5.70 GiB6,121,288,9285.881jayn7
Q5_K_M5.70 GiB6,121,288,9285.881jayn7
Q5_K_M5.70 GiB6,121,288,9285.881jayn7
Q6_K6.54 GiB7,024,833,7606.749jayn7
Q6_K6.54 GiB7,024,833,7606.749jayn7
Q6_K6.54 GiB7,024,833,7606.749jayn7
Q6_K6.54 GiB7,024,833,7606.749jayn7
Q6_K6.54 GiB7,024,833,7606.749jayn7
Q8_08.38 GiB8,995,313,8888.643jayn7
Q8_08.38 GiB8,995,313,8888.643jayn7
Q8_08.38 GiB8,995,313,8888.643jayn7
Q8_08.38 GiB8,995,313,8888.643jayn7
Q8_08.38 GiB8,995,313,8888.643jayn7

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
vae4.70 GiB1%no, must be resident
denoiser341.26 GiB99%no, must be resident
Full pipeline345.96 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 4.36 GiB. The real file is 4.74 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 HunyuanVideo-1.5 need?
Q4_K_M is exactly 5,090,407,648 bytes (4.74 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of HunyuanVideo-1.5 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.