LTX-2.5 Lands Open Weights With Native Multi-Shot — And It's Actually Fast

TL;DR: LTX released LTX-2.5 today — an open-weights video model that generates a 10-second 720p clip in 6.8 seconds on dual GB200s, ships native multi-shot generation, and integrates into ComfyUI on day one. It's the fastest practical video model available to indie builders, and the licensing terms (free under $10M ARR) make it immediately usable for most studios.

LTX-2.5 is not the biggest name in AI video. It's not trying to be.

The model comes from LTX, the open-world-model spinoff of Lightricks — a Jerusalem-based company better known for Facetune and Videoleap. Lightricks has been bootstrapped and profitable since the consumer-app days, which means LTX's incentive structure is different from the VC-fueled frontier labs. CEO Zeev Farbman is blunt about it: "We're definitely not doing this as philanthropy." The strategy is open weights with a revenue gate — free under $10M ARR, paid above.

Today's release lands that strategy on the strongest technical ground yet.

What's new in LTX-2.5

The headline number is speed: LTX says a 10-second 720p image-to-video clip takes 6.8 seconds on dual NVIDIA GB200 hardware. That's faster than real time. The LTX API tier produces 1080p in 23.7 seconds — still faster than competitors on the same task. LTX's own benchmarks put Google's Gemini Omni Flash at 52 seconds for the same job, Veo 3.1 at 70 seconds for an 8-second clip, and MiniMax-H3 at 180 seconds. Treat these as vendor-reported; the same caveat applies to LTX's 67% win rate in blind preference tests, which the company itself labels preliminary.

The technically more interesting feature is native multi-shot. A single generation produces multiple connected shots, with character, scene, lighting, visual style, and voice held consistent across cuts. This is the problem that has plagued every earlier T2V/I2V model — you could generate a single beautiful shot, but stitching shots together broke identity. LTX-2.5 generates the whole sequence in one pass.

Other notable changes:

• A new diffusion video decoder that reduces artifacts in high-motion footage and reconstructs fine detail like text and faces
• A custom Gemma 4 language backbone with prompt enhancement for multi-subject scenes
• A pretrained checkpoint tuned for physical AI and robotics — a base for teams to fine-tune on domain data that looks nothing like cinematic video
• A substantially improved distilled model that delivers near-full quality at lower cost, optimized for NVIDIA RTX GPUs

What this means for builders

The combination that matters: open weights + day-one ComfyUI integration + multi-shot + speed. Indie builders, game studios, and prototype teams can pull the weights today and run them locally on any GPU with at least 16GB of VRAM. The model supports text-to-video, image-to-video, and audio-to-video in both portrait and landscape.

Two variants are available. ltx-2-5-fast tops out at 4K with 24/25/48/50 FPS support, optimized for speed and lower cost. ltx-2-5-pro caps at 1080p but is tuned for higher fidelity. Both support the automatic duration mode — send "duration": null and the model picks clip length from the prompt itself.

The revenue gate is the part to watch. Most studios and indie teams fall under $10M ARR — they get free use. Larger companies negotiate a license. The gate means LTX can grow with its users without chasing VC returns, and it means builders can ship product without license anxiety in the early years.

The competitive landscape is now structurally clearer. Closed API leaders (Veo, Kling, Gemini Omni Flash) are still ahead on raw benchmark scores, but open-weights alternatives are no longer a generation behind. For anyone who needs on-prem deployment, data control, or fine-tuning access, LTX-2.5 is now the default starting point.

The take

LTX isn't chasing AGI or frontier-model rankings. They're shipping a video model that builders can actually deploy today, with the licensing structure to make it sustainable. The multi-shot feature alone is worth the upgrade for anyone doing narrative work. The speed numbers will hold up; the preference-test win rates are less certain.

For most indie builders and studios, this is the model to start with. The closed-API alternatives only win when you specifically need their distribution, brand safety, or a feature LTX-2.5 hasn't shipped yet.