LTX-2 (19B, video + audio) on Intel Xeon E-2100 / E-2200 NAS (32 GB)

Can the Intel Xeon E-2100 / E-2200 NAS (32 GB) run LTX-2 (19B, video + audio)?

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 24.5 GB of 26.2 GB usable and takes about 17.0 h per clip.

Best precision: Q4 GGUF
Memory mode: Text encoder offloaded
Time per clip: 17.0 h
Output: 1280×704, 121 frames, 40 steps

Download LTX-2 (19B, video + audio)

Recommended for the Intel Xeon E-2100 / E-2200 NAS (32 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/unsloth/LTX-2-GGUF (opens in a new tab)

Original weights · Hugging Face

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

huggingface.co/Lightricks/LTX-2 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/Lightricks/LTX-2 (opens in a new tab)

git clone https://github.com/Lightricks/LTX-2

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 76Great quality (A) · 76 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 68/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 Intel Xeon E-2100 / E-2200 NAS (32 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.	34.3 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); 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.	0.8 / 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	68.1 / 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 Intel Xeon E-2100 / E-2200 NAS (32 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	25.6 GB	26.2 GB	—	—	Won't run	82Great quality (A) · 82 of 100: how capable the model is at FP16, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	19.0 GB	26.2 GB	15.8 h	Sequential CPU offload	Very slowCPU offload	80Great quality (A) · 80 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`	19.5 GB	26.2 GB	20.2 h	Sequential CPU offload	Very slowCPU offload	81Great quality (A) · 81 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`	24.5 GB	26.2 GB	17.0 h	Text encoder offloaded	Very slowtight fit · encoder unloaded after use	76Great quality (A) · 76 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)

Other hardware that runs it

82Great quality (A) · 82 of 100: how capable the model is at FP16, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 4.9 min · Runs well
80Great quality (A) · 80 of 100: how capable the model is at FP8, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. AMD Ryzen AI Max+ 395 (128 GB) FP8 · 11.5 min · Runs well
76Great quality (A) · 76 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q4 GGUF · 7.0 min · Runs well (encoder in RAM)
80Great quality (A) · 80 of 100: how capable the model is at FP8, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 FP8 · 7.8 min · Runs well (CPU offload)
80Great quality (A) · 80 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. AMD Radeon RX 7900 XTX FP8 · 8.7 min · Runs well (CPU offload)
82Great quality (A) · 82 of 100: how capable the model is at FP16, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GH200 Grace Hopper (96 GB GPU) FP16 · 4.6 min · Runs well

Quick answers

How much memory does LTX-2 (19B, video + audio) need on the Intel Xeon E-2100 / E-2200 NAS 32GB?

At Q4 GGUF it needs about 24.5 GB. The Intel Xeon E-2100 / E-2200 NAS 32GB has 26.2 GB usable.

How long does LTX-2 (19B, video + audio) take on the Intel Xeon E-2100 / E-2200 NAS 32GB?

About 17.0 h per clip at Q4 GGUF and default settings, an estimate scaled from a reference timing by this hardware’s compute speed.

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.