Wan 2.2 S2V 14B (speech to video) on AMD EPYC 7002 / 7003 series NAS (64 GB)
Can the AMD EPYC 7002 / 7003 series NAS (64 GB) run Wan 2.2 S2V 14B (speech to video)?
Barely: it runs very slowly
Very slow. At Q8 GGUF it needs about 29.3 GB of 54.4 GB usable, with an estimated speed of 13.1 h.
- Best precision
Q8 GGUF- Memory mode
- Everything on GPU
- Time per clip
- 13.1 h
- Output
- 832×480, 81 frames, 40 steps
Download Wan 2.2 S2V 14B (speech to video)
Recommended for the AMD EPYC 7002 / 7003 series NAS (64 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/QuantStack/Wan2.2-S2V-14B-GGUF (opens in a new tab)
Original weights · Hugging Face
Full-precision files from Alibaba, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.
Official repo · GitHub
Reference code, inference scripts and docs from Alibaba. The weights themselves download from Hugging Face.
github.com/Wan-Video/Wan2.2 (opens in a new tab)
git clone https://github.com/Wan-Video/Wan2.2How 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.9 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 0.9 / 15 | |
| Memory use | 12.4 / 15 | |
| Match score | 72.2 / 100 |
Every precision on the AMD EPYC 7002 / 7003 series NAS (64 GB)
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 50.4 GB | 54.4 GB | 11.4 h | Everything on GPU | Very slowtight fit | 76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
FP8 | 28.1 GB | 54.4 GB | 10.3 h | Everything on GPU | Very slow | 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 29.3 GB | 54.4 GB | 13.1 h | Everything on GPU | Very slow | 75Great quality (A) · 75 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 21.6 GB | 54.4 GB | 13.7 h | Everything on GPU | Very slow | 70Great quality (A) · 70 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Other hardware that runs it
-
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H100 80GB SXM
-
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H800 80GB SXM
-
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GH200 Grace Hopper (96 GB GPU)
-
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H200 141GB SXM
-
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA B200
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.