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

Can the Arc B580 12 GB run Wan 2.2 I2V A14B?

Video model · 14B12 GB GDDR6 · 192-bit · 456 GB/s · BattlemageData 2026-09-25
Tight
Only just.

Download Q3_K_M (7.2 GB). With the model's working memory it needs about 11.5 GB, leaving 0.5 GB spare on 12 GB. Quality: noticeable loss of detail. For better quality, Q4_K_M (9.7 GB) also runs, with about 2.0 GB spilling into system RAM — a little slower, still practical.

Best fileQ3_K_M
File size7.2 GB
VRAM needed~11.5 GB
System RAM32 GB+
Memory map · Arc B580 12 GB11.5 GB / 12 GB
06 GB12 GB
Weights Q3_K_M · 7.2 GBWorking memory · 3.5 GBReserve · 0.8 GBFree · 0.5 GB
calculated from real file sizes plus working memory. Not yet measured on this setup. How this works.

Using Kijai's WanVideoWrapper instead of the native nodes? Its WanVideo BlockSwap node keeps part of the model in system RAM. To run the FP8 file (14.3 GB) on Arc B580 12 GB, start with blocks_to_swap ≈ 20 (of 40). Each block is about 0.4 GB; raise the number if you still run out of memory, lower it for speed. estimate WanVideoWrapper →

01What to download

PartFileFolderSize
ModelWan2.2-I2V-A14B-HighNoise-Q3_K_M.gguf
high-noise model (early steps)
Q3_K_M · QuantStack/Wan2.2-I2V-A14B-GGUF
models/unet7.2 GBDownload →
ModelWan2.2-I2V-A14B-LowNoise-Q3_K_M.gguf
low-noise model (late steps)
Q3_K_M · QuantStack/Wan2.2-I2V-A14B-GGUF
models/unet7.2 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 →
Total download · keep about the same free on disk21.3 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 files, 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 21.3 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 27.3 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 I2V file on 12 GB

FileSizeNeededOn this cardQualityDownload
16-bit
SAFETENSORS · Comfy-Org
28.6 GB32.9 GB20.9 GB too bigthe original weightsHugging Face →
Q8_0
GGUF · QuantStack
15.4 GB19.7 GB7.7 GB too bigpractically identical to the originalHugging Face →
FP8
SAFETENSORS · Comfy-Org
14.3 GB18.6 GB6.6 GB too bigpractically identical to the originalHugging Face →
Q6_K
GGUF · QuantStack
12.0 GB16.3 GB4.3 GB too bigvery close to the originalHugging Face →
Q5_K_M
GGUF · QuantStack
10.8 GB15.1 GB3.1 GB too bigclose; small differences in fine detailHugging Face →
Q4_K_M
GGUF · QuantStack
9.7 GB14.0 GBspills 2.0 GBgood; some loss in fine detail and textHugging Face →
Q3_K_M ←
GGUF · QuantStack
7.2 GB11.5 GBfits · 0.5 GB sparenoticeable loss of detailHugging Face →
Q2_K
GGUF · QuantStack
5.3 GB9.6 GBfits · 2.4 GB spareheavy loss; a last resortHugging Face →

Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 3.5 GB working memory for this model + 0.8 GB kept free for the system. Wan 2.2 A14B uses two files of this size (high-noise and low-noise); only one sits in VRAM at a time, both must fit in system RAM.

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 12 GB the FP8 encoder fits on its own, so prompt encoding stays fast.

04About this GPU

Intel Arc GPUs run ComfyUI through PyTorch's native XPU support on Windows 11 and Linux. Memory works the same as on NVIDIA, so the fit verdicts apply. FP8 files save memory but give no speed-up, and some custom nodes are NVIDIA-only.

Arc B580 12 GB: 12 GB GDDR6 · 192-bit · 456 GB/s · Battlemage. Everything that runs on the Arc B580 12 GB →

05What more VRAM would change

With 20 GB you could run Wan 2.2 I2V at 8-bit or better (Q8_0, 15.4 GB) with no offloading.

What changes from the Arc B580 12 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 I2V on a Arc B580 12 GB, send your time per image and peak VRAM and it will appear here, credited.

07Questions

How much VRAM does Wan 2.2 I2V need?

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

Which Wan 2.2 I2V file should I download for the Arc B580 12 GB?

Q3_K_M (7.2 GB) from QuantStack/Wan2.2-I2V-A14B-GGUF. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.

Is FP8 faster than GGUF on the Arc B580 12 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 I2V on the Arc B580 12 GB?

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