Can the Mac 16 GB run Wan 2.1 I2V 14B 480P?
Nothing fits entirely, but Q3_K_M (8.6 GB) overflows by only about 0.2 GB. ComfyUI keeps that part in system RAM automatically: slower than a full fit, but usable.
01What to download
| Part | File | Folder | Size | |
|---|---|---|---|---|
| Model | wan2.1-i2v-14b-480p-Q3_K_M.gguf Q3_K_M · city96/Wan2.1-I2V-14B-480P-gguf | models/unet | 8.6 GB | Download → |
| Text encoder | umt5-xxl-encoder-Q8_0.gguf UMT5-XXL GGUF Q8_0 · city96/umt5-xxl-encoder-gguf | models/text_encoders | 6.0 GB | Download → |
| VAE | wan_2.1_vae.safetensors Wan 2.1 VAE · Comfy-Org/Wan_2.1_ComfyUI_repackaged | models/vae | 0.3 GB | Download → |
| Also needed | clip_vision_h.safetensors CLIP Vision H · Comfy-Org/Wan_2.1_ComfyUI_repackaged | models/clip_vision | 1.3 GB | Download → |
| Total download · keep about the same free on disk | 16.1 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. On a Mac, FP8 text encoders do not load, so a 16-bit one is listed — or a GGUF one, loaded with “CLIPLoader (GGUF)” from the ComfyUI-GGUF nodes. 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.
Shared memory: about 22.1 GB of your 16 GB. On this machine the model, the text encoder, the VAE and the operating system all use the same memory. That is about 6.1 GB more than there is. It still runs: while the model works, the system compresses or swaps the idle text encoder, so loading and changing the prompt get slower. A smaller file or text encoder avoids that. calculated
02Every Wan 2.1 I2V 480P file on 12.7 GB
| File | Size | Needed | On this card | Quality | Download |
|---|---|---|---|---|---|
| 16-bit SAFETENSORS · Comfy-Org | 32.8 GB | 37.1 GB | 24.4 GB too big | the original weights | Hugging Face → |
| Q8_0 GGUF · city96 | 18.1 GB | 22.4 GB | 9.7 GB too big | practically identical to the original | Hugging Face → |
| Q6_K GGUF · city96 | 14.2 GB | 18.5 GB | 5.8 GB too big | very close to the original | Hugging Face → |
| Q5_K_M GGUF · city96 | 12.7 GB | 17.0 GB | 4.3 GB too big | close; small differences in fine detail | Hugging Face → |
| Q4_K_M GGUF · city96 | 11.3 GB | 15.6 GB | 2.9 GB too big | good; some loss in fine detail and text | Hugging Face → |
| Q3_K_M ← GGUF · city96 | 8.6 GB | 12.9 GB | spills 0.2 GB | noticeable loss of detail | Hugging 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. FP8 and INT8 files are left out on a Mac: Apple GPUs cannot compute FP8, so ComfyUI either fails to load them or converts them back to 16-bit, which saves no memory. Use a 16-bit or GGUF file.
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.7 GB the FP8 encoder fits on its own, so prompt encoding stays fast.
04About this GPU
A Mac with 16 GB shares that memory between the CPU and the GPU. On current macOS the GPU may use about 12.7 GB of it by default (older macOS versions: about 11.5 GB); that is the figure used here. ComfyUI can go past it, but macOS then starts compressing and swapping memory and everything slows down. ComfyUI runs on Apple GPUs through PyTorch's MPS backend. 16-bit and GGUF files work; FP8 and INT8 files do not save memory on a Mac, so they are skipped. Speed is the catch: even the fastest Macs are several times slower per image than a desktop RTX card. Chips sold with 16 GB: M1, M1 Pro, M2, M2 Pro, M3, M4, M5, M6 (memory bandwidth 68.25–200 GB/s — the higher, the faster). Everything about Macs and local AI →
Mac 16 GB: 16 GB unified · ~12.7 GB for the GPU · 68.25–200 GB/s · Apple Silicon. Everything that runs on the Mac 16 GB →
05What more VRAM would change
With 24 GB you could run Wan 2.1 I2V 480P at 8-bit or better (Q8_0, 18.1 GB) with no offloading: for example on the RTX 4090 24 GB, RTX 3090 24 GB, RX 7900 XTX 24 GB.
06Measured and reported results
Nobody has sent measured numbers for this pair yet. If you run Wan 2.1 I2V 480P on a Mac 16 GB, send your time per image and peak VRAM and it will appear here, credited.
07Questions
How much VRAM does Wan 2.1 I2V 480P need?
Around 12.9 GB with the smallest file (Q3_K_M) and 20.7 GB with an 8-bit file (FP8), counting working memory and a small system reserve. The full 16-bit file needs about 37.1 GB.
Which Wan 2.1 I2V 480P file should I download for the Mac 16 GB?
Q3_K_M (8.6 GB) from city96/Wan2.1-I2V-14B-480P-gguf. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.
Is FP8 faster than GGUF on the Mac 16 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.1 I2V 480P on the Mac 16 GB?
About 16.1 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 12.7 GB card, 32 GB of system RAM or more is recommended.