Wan 2.2 S2V 14B (speech to video) on NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)
Can the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB) run Wan 2.2 S2V 14B (speech to video)?
Barely: it runs very slowly (CPU offload)
Very slow (CPU offload). At FP8 it needs about 11.3 GB of 16.0 GB usable, with an estimated speed of 43.0 min.
- Best precision
FP8- Memory mode
- Sequential CPU offload
- Time per clip
- 43.0 min
- Output
- 832×480, 81 frames, 40 steps
Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)
On Linux
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Download Wan 2.2 S2V 14B (speech to video)
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.
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.5 / 45 | |
|---|---|---|
| Memory fit | 12.0 / 25 | |
| Speed | 4.0 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 64.5 / 100 |
Every precision on the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 17.0 GB | 16.0 GB | — | — | Won't run | 76Great quality (A) · 76 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 | 11.3 GB | 16.0 GB | 43.0 min | Sequential CPU offload | Very slowCPU offload | 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 11.7 GB | 16.0 GB | 54.9 min | Sequential CPU offload | Very slowCPU offload | 75Great quality (A) · 75 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 9.0 GB | 16.0 GB | 57.3 min | Sequential CPU offload | Very slowCPU offload | 70Great quality (A) · 70 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 60/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.