HunyuanVideo I2V 13B on NVIDIA RTX Spark N1X (6144-core GPU) (48 GB)

Can the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB) run HunyuanVideo I2V 13B?

Barely: it runs very slowly (tight fit · encoder unloaded after use)

Very slow (tight fit · encoder unloaded after use). At Q4 GGUF it needs about 30.4 GB of 32.2 GB usable, with an estimated speed of 1.9 h.

Best precision: Q4 GGUF
Memory mode: Text encoder offloaded
Time per clip: 1.9 h
Output: 1280×720, 129 frames, 50 steps

Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB)

On Linux

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.

Get ComfyUI

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download HunyuanVideo I2V 13B

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB): 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/city96/HunyuanVideo-I2V-gguf (opens in a new tab)

Original weights · Hugging Face

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

huggingface.co/tencent/HunyuanVideo-I2V (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/Tencent-Hunyuan/HunyuanVideo-I2V (opens in a new tab)

git clone https://github.com/Tencent-Hunyuan/HunyuanVideo-I2V

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 66Good quality (B) · 66 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 65/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 Very slowtight fit · encoder unloaded after use: How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB): 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.	30.1 / 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.	18.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	2.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	65.6 / 100

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

Every precision on the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	31.2 GB	32.2 GB	1.9 h	Sequential CPU offload	Very slowtight fit · CPU offload	72Great quality (A) · 72 of 100: how capable the model is at FP16, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	26.6 GB	32.2 GB	1.7 h	Sequential CPU offload	Very slowCPU offload	70Great quality (A) · 70 of 100: how capable the model is at FP8, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	27.0 GB	32.2 GB	2.2 h	Sequential CPU offload	Very slowCPU offload	71Great quality (A) · 71 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	30.4 GB	32.2 GB	1.9 h	Text encoder offloaded	Very slowtight fit · encoder unloaded after use	66Good quality (B) · 66 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 65/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 FP16, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 29.3 min · Slow
70Great quality (A) · 70 of 100: how capable the model is at FP8, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 FP8 · 39.1 min · Slow (CPU offload)
72Great quality (A) · 72 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) FP16 · 27.9 min · Slow
72Great quality (A) · 72 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 80GB SXM FP16 · 27.9 min · Slow
72Great quality (A) · 72 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 H800 80GB SXM FP16 · 27.9 min · Slow
72Great quality (A) · 72 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 FP16 · 30.2 min · Slow

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.