Wan-AI · video

Wan2.2-I2V-A14B

Wan-AI/Wan2.2-I2V-A14B

Wan2.2-I2V-A14B at Q4_K_M is exactly 9,651,728,896 bytes (8.99 GiB / 9.65 GB) — an effective 5.404 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,300,957,6962.968QuantStack
Q2_K4.94 GiB5,300,957,6962.968QuantStack
Q3_K_S6.07 GiB6,515,012,0963.648QuantStack
Q3_K_S6.07 GiB6,515,012,0963.648QuantStack
Q3_K_M6.68 GiB7,176,106,4964.0181095QuantStack
Q3_K_M6.68 GiB7,176,106,4964.0181095QuantStack
Q4_07.97 GiB8,558,096,8964.7921095QuantStack
Q4_K_S8.15 GiB8,748,151,2964.898QuantStack
Q4_K_S8.15 GiB8,748,151,2964.898QuantStack
Q4_18.62 GiB9,259,332,0965.184QuantStack
Q4_K_M8.99 GiB9,651,728,8965.4041095QuantStack
Q4_K_M8.99 GiB9,651,728,8965.4041095QuantStack
Q5_K_S9.44 GiB10,137,514,4965.676QuantStack
Q5_K_S9.44 GiB10,137,514,4965.676QuantStack
Q5_09.61 GiB10,314,461,6965.775QuantStack
Q5_09.61 GiB10,314,461,6965.775QuantStack
Q2_K2 shards9.89 GiB10,616,642,1765.944darksidewalker
Q5_K_M10.05 GiB10,792,055,2966.0421095QuantStack
Q5_K_M10.05 GiB10,792,055,2966.0421095QuantStack
Q5_110.26 GiB11,015,696,8966.167QuantStack
Q5_110.26 GiB11,015,696,8966.167QuantStack
Q6_K11.18 GiB12,003,652,0966.7211095QuantStack
Q6_K11.18 GiB12,003,652,0966.721QuantStack
Q3_K_M2 shards12.15 GiB13,044,750,9767.303darksidewalker
Q8_014.35 GiB15,406,608,8968.6261095QuantStack
Q8_014.35 GiB15,406,608,8968.6261095QuantStack
Q4_K_M2 shards17.99 GiB19,318,184,57610.816darksidewalker
Q5_K_M2 shards20.12 GiB21,598,837,37612.093darksidewalker
Q6_K2 shards22.37 GiB24,022,030,97613.449darksidewalker
Q8_02 shards28.71 GiB30,827,944,57617.260darksidewalker

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser11.05 GiB100%no, must be resident
Full pipeline11.05 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 Wan2.2-I2V-A14B need?
Q4_K_M is exactly 9,651,728,896 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 Wan2.2-I2V-A14B 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.