Wan-AI · video

Wan2.1-FLF2V-14B-720P

Wan-AI/Wan2.1-FLF2V-14B-720P

Wan2.1-FLF2V-14B-720P at Q4_K_M is exactly 11,343,816,128 bytes (10.56 GiB / 11.34 GB) — an effective 5.535 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
16.4B
Architecture
wan
null layers
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q3_K_S7.38 GiB7,928,571,3283.869city96
Q3_K_M8.00 GiB8,589,665,7284.191city96
Q4_09.55 GiB10,250,184,1285.002city96
Q4_K_S9.72 GiB10,440,238,5285.094city96
Q4_110.32 GiB11,082,491,3285.408city96
Q4_K_M10.56 GiB11,343,816,1285.535city96
Q5_K_S11.26 GiB12,091,745,7285.900city96
Q5_011.43 GiB12,268,692,9285.986city96
Q5_K_M11.87 GiB12,746,286,5286.219city96
Q5_112.20 GiB13,101,000,1286.393city96
Q6_K13.26 GiB14,236,411,3286.947city96
Q8_016.90 GiB18,147,272,1288.855city96
BF1631.00 GiB33,286,088,12816.241city96
F1631.00 GiB33,286,088,12816.241city96

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser76.58 GiB100%no, must be resident
Full pipeline76.58 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 8.59 GiB. The real file is 10.56 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 Wan2.1-FLF2V-14B-720P need?
Q4_K_M is exactly 11,343,816,128 bytes (10.56 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.1-FLF2V-14B-720P 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.