Wan 2.1 VACE 14B on Apple iPhone 17 Pro / 17 Pro Max

Can the Apple iPhone 17 Pro / 17 Pro Max run Wan 2.1 VACE 14B?

No, it doesn’t fit (over the app memory limit)

No. Wan 2.1 VACE 14B needs about 22.0 GB even at Q4 GGUF; the Apple iPhone 17 Pro / 17 Pro Max has 7.2 GB usable.

Download Wan 2.1 VACE 14B

Recommended: q4_gguf. Every other precision has its own download link in the table below.

Quantized files · GGUF for ComfyUI

Smaller GGUF versions for ComfyUI (with the ComfyUI-GGUF node). No sign-in needed; the model’s license still applies.

Download the q4_gguf (Q4_K_S) file (opens in a new tab)

huggingface.co/QuantStack/Wan2.1_14B_VACE-GGUF (opens in a new tab)

Original weights · Hugging Face

Full-precision files from Alibaba, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/Wan-AI/Wan2.1-VACE-14B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Alibaba. The weights themselves download from Hugging Face.

github.com/Wan-Video/Wan2.1 (opens in a new tab)

git clone https://github.com/Wan-Video/Wan2.1

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 72Great quality (A) · 72 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4 GGUF, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Won't runover the app memory limit: How well it runs on the Apple iPhone 17 Pro / 17 Pro Max: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	9.8 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	0.0 / 15
Match score	9.8 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every precision on the Apple iPhone 17 Pro / 17 Pro Max

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	30.5 GB	7.2 GB	—	—	Won't runover the app memory limit	78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	24.4 GB	7.2 GB	—	—	Won't runover the app memory limit	76Great quality (A) · 76 of 100: how capable the model is at FP8, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	24.8 GB	7.2 GB	—	—	Won't runover the app memory limit	77Great quality (A) · 77 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	22.0 GB	7.2 GB	—	—	Won't runover the app memory limit	72Great quality (A) · 72 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)

Hardware that can run it

78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 26.9 min · Slow
72Great quality (A) · 72 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q4 GGUF · 38.6 min · Slow (tight fit · encoder in RAM)
78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GH200 Grace Hopper (96 GB GPU) FP16 · 25.5 min · Slow
78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 80GB SXM FP16 · 25.5 min · Slow
78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H800 80GB SXM FP16 · 25.5 min · Slow
78Great quality (A) · 78 of 100: how capable the model is at FP16, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 NVL FP16 · 27.7 min · Slow

Models that do run on the Apple iPhone 17 Pro / 17 Pro Max

49Fair quality (C) · 49 of 100: how capable the model is at FP8, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. LTX-Video 2B FP8 · 10.0 min
35Basic quality (D) · 35 of 100: how capable the model is at FP16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. AnimateDiff v3 (SD 1.5) FP16 · 8.5 min
44Fair quality (C) · 44 of 100: how capable the model is at FP8, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. CogVideoX 2B FP8 · 24.0 min

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.