vrgamedevgirl84 · video

Wan14BT2VFusioniX

vrgamedevgirl84/Wan14BT2VFusioniX

Wan14BT2VFusioniX at Q4_K_M is exactly 9,650,100,736 bytes (8.99 GiB / 9.65 GB) — an effective 5.403 bits per weight, not the nominal 4.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K4.94 GiB5,299,329,5362.967QuantStack
Q2_K5.59 GiB6,006,761,2163.363QuantStack
Q3_K_S6.07 GiB6,513,383,9363.647QuantStack
Q3_K_M6.68 GiB7,174,478,3364.017QuantStack
Q3_K_S6.92 GiB7,433,807,6164.162QuantStack
Q3_K_L7.25 GiB7,783,963,1364.358QuantStack
Q3_K_M7.54 GiB8,094,902,0164.532QuantStack
Q4_07.97 GiB8,556,468,7364.791QuantStack
Q3_K_L8.11 GiB8,704,386,8164.873QuantStack
Q4_K_S8.15 GiB8,746,523,1364.897QuantStack
Q4_18.62 GiB9,257,703,9365.183QuantStack
Q4_K_M8.99 GiB9,650,100,7365.403QuantStack
Q4_09.09 GiB9,755,420,4165.462QuantStack
Q4_K_S9.26 GiB9,945,474,8165.568QuantStack
Q5_K_S9.44 GiB10,135,886,3365.675QuantStack
Q5_09.60 GiB10,312,833,5365.774QuantStack
Q4_19.86 GiB10,587,727,6165.928QuantStack
Q5_K_M10.05 GiB10,790,427,1366.042QuantStack
Q4_K_M10.10 GiB10,849,052,4166.074QuantStack
Q5_110.26 GiB11,014,068,7366.167QuantStack
Q5_K_S10.80 GiB11,596,982,0166.493QuantStack
Q5_010.97 GiB11,773,929,2166.592QuantStack
Q6_K11.18 GiB12,002,023,9366.720QuantStack
Q5_K_M11.41 GiB12,251,522,8166.859QuantStack
Q5_111.74 GiB12,606,236,4167.058QuantStack
Q6_K12.80 GiB13,741,647,6167.694QuantStack
Q8_014.35 GiB15,404,980,7368.625QuantStack
Q8_016.44 GiB17,652,508,4169.883QuantStack
F1626.62 GiB28,577,716,73616.000QuantStack

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser112.35 GiB100%no, must be resident
Full pipeline112.35 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 7.49 GiB. The real file is 8.99 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 Wan14BT2VFusioniX need?
Q4_K_M is exactly 9,650,100,736 bytes (8.99 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of Wan14BT2VFusioniX 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.