Wan 2.1 I2V 14B 480P on NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)
Can the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) run Wan 2.1 I2V 14B 480P?
Yes, but slowly
Slow. At FP16 it needs about 46.5 GB of 102 GB usable, with an estimated speed of 33.1 min.
- Best precision
FP16- Memory mode
- Everything on GPU
- Time per clip
- 33.1 min
- Output
- 832×480, 81 frames, 50 steps
Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)
On Linux
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Download Wan 2.1 I2V 14B 480P
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/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.3 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 4.5 / 15 | |
| Memory use | 10.5 / 15 | |
| Match score | 73.3 / 100 |
Every precision on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 46.5 GB | 102 GB | 33.1 min | Everything on GPU | Slow | 74Great quality (A) · 74 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 | 26.2 GB | 102 GB | 29.8 min | Everything on GPU | Slow | 72Great quality (A) · 72 of 100: how capable the model is at FP8, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 27.2 GB | 102 GB | 38.0 min | Everything on GPU | Slow | 73Great quality (A) · 73 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 20.6 GB | 102 GB | 39.7 min | Everything on GPU | Slow | 68Good quality (B) · 68 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 64/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.