Wan 2.1 I2V 14B 480P on AMD EPYC 7002 / 7003 series NAS (16 GB)
Can the AMD EPYC 7002 / 7003 series NAS (16 GB) run Wan 2.1 I2V 14B 480P?
Barely: it runs very slowly (tight fit · CPU offload)
Very slow (tight fit · CPU offload). At Q8 GGUF it needs about 10.8 GB of 12.0 GB usable, with an estimated speed of 15.4 h.
- Best precision
Q8 GGUF- Memory mode
- Sequential CPU offload
- Time per clip
- 15.4 h
- Output
- 832×480, 81 frames, 50 steps
Download Wan 2.1 I2V 14B 480P
Recommended for the AMD EPYC 7002 / 7003 series NAS (16 GB): q8_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 q8_gguf (Q8_0) file (opens in a new tab)
huggingface.co/city96/Wan2.1-I2V-14B-480P-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-I2V-14B-480P (opens in a new tab)
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.1How it’s rated
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 quality | 33.0 / 45 | |
|---|---|---|
| Memory fit | 10.0 / 25 | |
| Speed | 0.9 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 58.8 / 100 |
Every precision on the AMD EPYC 7002 / 7003 series NAS (16 GB)
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 15.4 GB | 12.0 GB | — | — | Won't run | 74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
FP8 | 10.5 GB | 12.0 GB | 12.0 h | Sequential CPU offload | Very slowtight fit · CPU offload | 72Great quality (A) · 72 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. | Original weights (opens in a new tab) |
Q8 GGUF | 10.8 GB | 12.0 GB | 15.4 h | Sequential CPU offload | Very slowtight fit · CPU offload | 73Great quality (A) · 73 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 8.5 GB | 12.0 GB | 16.0 h | Sequential CPU offload | Very slowCPU offload | 68Good quality (B) · 68 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Other hardware that runs it
-
72Great quality (A) · 72 of 100: how capable the model is at FP8, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H100 80GB SXM
-
74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H800 80GB SXM
-
74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GH200 Grace Hopper (96 GB GPU)
-
74Great quality (A) · 74 of 100: how capable the model is at FP16, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H100 NVL
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.