Datasheet for local AI49 models98 GPUsData read 2026-09-25
No adsNo tracking
Check my GPU →

Can the RTX 4060 8 GB run Wan 2.2 Animate 14B?

Video model · 17.3B8 GB GDDR6 · 128-bit · 272 GB/s · Ada LovelaceData 2026-09-25
Offload
Not entirely in VRAM, but it can still run.

The smallest sensible file, Q4_K_M (11.5 GB), needs about 16.8 GB — 8.8 GB more than RTX 4060 8 GB has. ComfyUI can still run it by streaming part of the model from system RAM. How much slower that is depends on your ComfyUI version, the file format and the PCIe link — see the note below.

Best fileQ4_K_M
File size11.5 GB
VRAM needed~16.8 GB
System RAM32 GB+
Memory map · RTX 4060 8 GB16.8 GB needed · 8.8 GB over 8 GB
08 GB17 GB
Weights Q4_K_M · 11.5 GBWorking memory · 4.5 GBReserve · 0.8 GBSpills to system RAM · 8.8 GB
calculated from real file sizes plus working memory. Not yet measured on this setup. How this works.

Worth trying on this GPU: with an up-to-date ComfyUI, Dynamic VRAM (on by default for NVIDIA since March 2026) streams whatever does not fit from system RAM, and ComfyUI's own start-up message recommends native FP8/INT8 files over GGUF, saying they “will be faster even if they are larger than your memory”. So before settling for a heavily compressed GGUF, try the native FP8 file (17.3 GB). The file recommended above is the best one that fits entirely — the safe choice on older ComfyUI versions, AMD and Intel. Comfy blog: Dynamic VRAM →

01What to download

PartFileFolderSize
ModelWan2.2-Animate-14B-Q4_K_M.gguf
Q4_K_M · QuantStack/Wan2.2-Animate-14B-GGUF
models/unet11.5 GBDownload →
Text encoderumt5_xxl_fp8_e4m3fn_scaled.safetensors
UMT5-XXL FP8 (scaled) · Comfy-Org/Wan_2.1_ComfyUI_repackaged
models/text_encoders6.7 GBDownload →
VAEwan_2.1_vae.safetensors
Wan 2.1 VAE · Comfy-Org/Wan_2.2_ComfyUI_Repackaged
models/vae0.3 GBDownload →
Also neededclip_vision_h.safetensors
CLIP Vision H · Comfy-Org/Wan_2.1_ComfyUI_repackaged
models/clip_vision1.3 GBDownload →
Total download · keep about the same free on disk19.8 GB

Alternatives: UMT5-XXL FP16 (11.4 GB). The 16-bit text encoder is a little more faithful; the smaller one is chosen here because it loads faster and needs less RAM. Sizes read from Hugging Face (2026-09-25). “Download” links start the file directly; the file name links are the same files the official ComfyUI workflows use.

System RAM: 32 GB or more. ComfyUI keeps the model file, the text encoder and the VAE in system RAM and moves them to the GPU as needed. With this set of files that is about 19.8 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 25.8 GB in total. With less RAM it still runs, but Windows starts swapping to disk and loading gets very slow. calculated

02Every Wan 2.2 Animate file on 8 GB

FileSizeNeededOn this cardQualityDownload
16-bit
SAFETENSORS · Comfy-Org
34.5 GB39.8 GB31.8 GB too bigthe original weightsHugging Face →
FP8
SAFETENSORS · Kijai
17.3 GB22.6 GB14.6 GB too bigpractically identical to the originalHugging Face →
Q8_0
GGUF · QuantStack
18.7 GB24.0 GB16.0 GB too bigpractically identical to the originalHugging Face →
INT8
SAFETENSORS · Comfy-Org
18.4 GB23.7 GB15.7 GB too bigpractically identical to the originalHugging Face →
Q6_K
GGUF · QuantStack
14.6 GB19.9 GB11.9 GB too bigvery close to the originalHugging Face →
Q5_K_M
GGUF · QuantStack
13.0 GB18.3 GB10.3 GB too bigclose; small differences in fine detailHugging Face →
Q4_K_M ←
GGUF · QuantStack
11.5 GB16.8 GB8.8 GB too biggood; some loss in fine detail and textHugging Face →
Q3_K_M
GGUF · QuantStack
8.6 GB13.9 GB5.9 GB too bignoticeable loss of detailHugging Face →
Q2_K
GGUF · QuantStack
6.5 GB11.8 GB3.8 GB too bigheavy loss; a last resortHugging Face →

Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 4.5 GB working memory for this model + 0.8 GB kept free for the system.

03The text encoder

UMT5-XXL + CLIP Vision H: 11.4 GB as 16-bit, 6.7 GB as FP8, 3.7 GB as GGUF Q4_K_M (plus CLIP Vision H (1.3 GB) for the input image). ComfyUI encodes the prompt first and can push the encoder out of VRAM before sampling, so it does not have to fit together with the model. On 8 GB the FP8 encoder fits on its own, so prompt encoding stays fast.

04About this GPU

The RTX 4060 8 GB is an Ada Lovelace GPU with hardware FP8, so ComfyUI can compute Comfy-Org's FP8 files natively: small and fast. (Plain FP8 files use FP8 maths with the --fast fp8_matrix_mult option.)

RTX 4060 8 GB: 8 GB GDDR6 · 128-bit · 272 GB/s · Ada Lovelace. Everything that runs on the RTX 4060 8 GB →

05What more VRAM would change

With 24 GB you could run Wan 2.2 Animate at 8-bit or better (FP8, 17.3 GB) with no offloading: for example on the RTX 4090 24 GB, RTX 3090 24 GB, RX 7900 XTX 24 GB.

What changes from the RTX 4060 8 GB to the RTX 5060 Ti 16 GB → · What changes from the RTX 4060 8 GB to the RTX 3090 24 GB →

06Measured and reported results

Nobody has sent measured numbers for this pair yet. If you run Wan 2.2 Animate on a RTX 4060 8 GB, send your time per image and peak VRAM and it will appear here, credited.

07Questions

How much VRAM does Wan 2.2 Animate need?

Around 11.8 GB with the smallest file (Q2_K) and 22.6 GB with an 8-bit file (FP8), counting working memory and a small system reserve. The full 16-bit file needs about 39.8 GB.

Which Wan 2.2 Animate file should I download for the RTX 4060 8 GB?

Q4_K_M (11.5 GB) from QuantStack/Wan2.2-Animate-14B-GGUF. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.

Is FP8 faster than GGUF on the RTX 4060 8 GB?

It can be. This GPU has FP8 hardware, and ComfyUI computes FP8 natively for files made for it (Comfy-Org's fp8_scaled files), or for any FP8 file with the --fast fp8_matrix_mult option. GGUF files are unpacked on the fly, which costs some speed.

How much do I need to download for Wan 2.2 Animate on the RTX 4060 8 GB?

About 19.8 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 8 GB card, 32 GB of system RAM or more is recommended.