Can the RTX 2060 6 GB run Wan 2.2 TI2V 5B?
Download Q2_K (1.9 GB). With the model's working memory it needs about 5.7 GB, leaving 0.3 GB spare on 6 GB. Quality: heavy loss; a last resort. For better quality, Q3_K_M (2.5 GB) also runs, with about 0.3 GB spilling into system RAM — a little slower, still practical.
Using Kijai's WanVideoWrapper instead of the native nodes? Its WanVideo BlockSwap node keeps part of the model in system RAM. To run the 16-bit file (10.0 GB) on RTX 2060 6 GB, start with blocks_to_swap ≈ 25 (of 30). Each block is about 0.3 GB; raise the number if you still run out of memory, lower it for speed. estimate WanVideoWrapper →
01What to download
| Part | File | Folder | Size | |
|---|---|---|---|---|
| Model | Wan2.2-TI2V-5B-Q2_K.gguf Q2_K · QuantStack/Wan2.2-TI2V-5B-GGUF | models/unet | 1.9 GB | Download → |
| Text encoder | umt5_xxl_fp8_e4m3fn_scaled.safetensors UMT5-XXL FP8 (scaled) · Comfy-Org/Wan_2.1_ComfyUI_repackaged | models/text_encoders | 6.7 GB | Download → |
| VAE | wan2.2_vae.safetensors Wan 2.2 VAE · Comfy-Org/Wan_2.2_ComfyUI_Repackaged | models/vae | 1.4 GB | Download → |
| Total download · keep about the same free on disk | 10.0 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: 16 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 10.0 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 16.0 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 5B file on 6 GB
| File | Size | Needed | On this card | Quality | Download |
|---|---|---|---|---|---|
| 16-bit SAFETENSORS · Comfy-Org | 10.0 GB | 13.8 GB | 7.8 GB too big | the original weights | Hugging Face → |
| Q8_0 GGUF · QuantStack | 5.4 GB | 9.2 GB | 3.2 GB too big | practically identical to the original | Hugging Face → |
| Q6_K GGUF · QuantStack | 4.2 GB | 8.0 GB | 2.0 GB too big | very close to the original | Hugging Face → |
| Q5_K_M GGUF · QuantStack | 3.8 GB | 7.6 GB | spills 1.6 GB | close; small differences in fine detail | Hugging Face → |
| Q4_K_M GGUF · QuantStack | 3.4 GB | 7.2 GB | spills 1.2 GB | good; some loss in fine detail and text | Hugging Face → |
| Q3_K_M GGUF · QuantStack | 2.5 GB | 6.3 GB | spills 0.3 GB | noticeable loss of detail | Hugging Face → |
| Q2_K ← GGUF · QuantStack | 1.9 GB | 5.7 GB | fits · 0.3 GB spare | heavy loss; a last resort | Hugging Face → |
Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 3 GB working memory for this model + 0.8 GB kept free for the system.
03The text encoder
UMT5-XXL: 11.4 GB as 16-bit, 6.7 GB as FP8, 3.7 GB as GGUF Q4_K_M. 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. Use the smallest encoder file; it still fits on its own.
04About this GPU
The RTX 2060 6 GB (Turing) has no FP8 compute. FP8 files still load and save memory, but ComfyUI converts them back before the maths, so there is no speed gain — Q8_0 GGUF is the closer-to-original 8-bit choice. ComfyUI can compute INT8 files natively on NVIDIA, which is worth a try where a model offers one.
RTX 2060 6 GB: 6 GB GDDR6 · 192-bit · 336 GB/s · Turing. Everything that runs on the RTX 2060 6 GB →
05What more VRAM would change
With 10 GB you could run Wan 2.2 5B at 8-bit or better (Q8_0, 5.4 GB) with no offloading: for example on the RTX 3080 10 GB.
What changes from the RTX 2060 6 GB to the RTX 3060 12 GB → · What changes from the RTX 2060 6 GB to the RTX 5060 Ti 16 GB →
06Measured and reported results
Nobody has sent measured numbers for this pair yet. If you run Wan 2.2 5B on a RTX 2060 6 GB, send your time per image and peak VRAM and it will appear here, credited.
07Questions
How much VRAM does Wan 2.2 5B need?
Around 5.7 GB with the smallest file (Q2_K) and 9.2 GB with an 8-bit file (Q8_0), counting working memory and a small system reserve. The full 16-bit file needs about 13.8 GB.
Which Wan 2.2 5B file should I download for the RTX 2060 6 GB?
Q2_K (1.9 GB) from QuantStack/Wan2.2-TI2V-5B-GGUF. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.
Is FP8 faster than GGUF on the RTX 2060 6 GB?
No. This GPU has no FP8 compute, so ComfyUI converts FP8 weights back before the maths. FP8 only saves memory here; Q8_0 GGUF is the closer-to-original 8-bit pick.
How much do I need to download for Wan 2.2 5B on the RTX 2060 6 GB?
About 10.0 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 6 GB card, 16 GB of system RAM or more is recommended.