LTX 2.3 vs LTX 2.5 (2026): Upgrade or Keep Using 2.3?

Upgrading from LTX 2.3 to LTX 2.5 can improve multi-shot continuity, fine detail, and prompt handling—but at common 720p and 1080p API tiers, it can also more than double your cost. LTX 2.5 does not yet support Retake, Extend, or Reframe either. The right choice depends on whether you are generating new footage, editing existing clips, or keeping a stable local workflow intact.

Quick Answer: Is LTX 2.5 Better Than LTX 2.3?

LTX 2.5 is the better default for new text-to-video and image-to-video work when you want native multi-shot scenes, sharper frame-level detail, a newer Gemma 4 text encoder, automatic duration, or the improved distilled workflow. Its new Diffusion Fidelity Rendering pipeline and diffusion video decoder are the most important technical upgrades.

However, LTX 2.3 is still the practical choice for lower API cost, 4K Pro API output, and API-based Retake, Extend, Reframe, or HDR-upscale workflows. It also has a broader set of mature native ComfyUI templates. If an existing 2.3 pipeline is stable and depends on those features, there is no reason to migrate every job immediately.

LTX 2.3 vs LTX 2.5 at a Glance

The table reveals the real upgrade story. LTX 2.5 advances generation quality and scene construction, but LTX 2.3 still offers a wider editing surface and lower hosted-generation cost.

What Actually Changed in LTX 2.5?

LTX 2.5 is not simply LTX 2.3 with more training data. Lightricks changed the model's text stack, decoder, checkpoint packaging, distilled workflow, duration handling, and high-fidelity rendering path.

Native Multi-Shot Generation

Previous LTX versions were designed primarily around a continuous shot. LTX 2.5 can generate multiple connected shots in one pass while attempting to preserve character identity, environment, lighting, visual style, voice, and other scene properties across cuts.

This is the clearest reason to upgrade if you create ads, trailers, narrative sequences, or social videos with intentional cuts. Generating three shots independently often causes wardrobe, location, lighting, and voice drift. A model that treats the shots as one sequence has more context for maintaining continuity.

Native multi-shot does not guarantee perfect continuity. It gives the model a better structure for the task, but complex interactions and long prompt chains can still fail.

Diffusion Fidelity Rendering

Diffusion Fidelity Rendering, or DFR, is LTX 2.5's new high-quality rendering path. The official pipeline first establishes motion, composition, and keyframes, then performs spatial detailing. Optional temporal refinement can add more frames and improve detail across time.

The practical idea is to avoid spending an identical amount of compute on every part of a scene. A static wall is easier than a moving face, reflective object, readable sign, or fast camera move. DFR is designed to allocate more work where visual complexity demands it.

A New Diffusion Video Decoder

LTX 2.5 introduces a diffusion-based video decoder intended to produce sharper faces, textures, fine edges, and on-screen text with fewer motion smears. This decoder can improve fidelity, but it also requires more decode time and memory than the lighter convolutional decoder that remains available.

That trade-off explains some apparently contradictory community reports. One user may describe LTX 2.5 as extremely fast while another complains about a slow VAE decode. They may be using different decoders, tiling settings, quantization, attention backends, resolutions, and refinement stages.

Gemma 4, Prompt Enhancement, and Auto Duration

LTX 2.3 uses a Gemma 3-based text stack. LTX 2.5 moves to a fine-tuned Gemma 4 12B encoder with a custom prompt enhancer. The goal is to retain more subjects, actions, camera instructions, lighting details, and audio cues across a complex prompt.

LTX 2.5 also adds an optional duration predictor. Instead of manually selecting a fixed frame count, the model can infer a suitable clip length from the requested action. In the API, this is exposed by sending duration: null.

There is one important limitation: automatic duration cannot be combined with a last-frame input. A first-and-last-frame sequence needs a known duration so the motion can arrive at the target frame on time.

A Better Distilled Model

Both versions offer fast distilled generation, but Lightricks says the new LTX 2.5 distilled checkpoint retains more of the full model's quality, prompt adherence, and motion consistency. The official distilled transformer uses a fixed eight-step schedule with CFG set to 1.

For most local creators, this may be more consequential than the full model. A fast checkpoint that produces more usable drafts can reduce iteration time even if the final render still uses a heavier pipeline.

Where LTX 2.3 Still Has the Advantage

The newest model does not currently cover the complete LTX 2.3 API surface.

Retake, Extend, Reframe, and HDR Upscale

As of August 15, 2026, the official API documentation lists LTX 2.5 for text-to-video, image-to-video, and audio-to-video. It does not list LTX 2.5 support for Retake, Extend, or Reframe.

LTX 2.3 Pro still supports:

• Retake: regenerate a selected region of an existing video.
• Extend: add generated footage before or after an existing clip.
• Reframe: expand a video into a new aspect ratio by generating missing areas.
• HDR upscale: convert supported SDR video into an HDR-oriented output.

If one of those operations is central to an automated workflow, stay on LTX 2.3 for that stage. A mixed pipeline is perfectly reasonable: generate new scenes with 2.5, then use a supported 2.3 editing endpoint when required.

4K Pro Through the API

LTX 2.3 Fast and Pro both support API output up to 4K. LTX 2.5 Fast supports up to 4K, but LTX 2.5 Pro currently tops out at 1080p in the official API support matrix.

This is easy to misread because LTX 2.5 has a native 4K HDR local production story. Model-level and local-pipeline capabilities are not identical to the options exposed by a hosted API endpoint.

Lower API Cost

LTX 2.5 costs more per generated second at every directly comparable 720p and 1080p tier. At the prices published on August 15, 2026:

Text-to-video and image-to-video use the same per-second pricing at these tiers. Prices can change, so verify the official pricing page before budgeting a production run.

This does not automatically make LTX 2.3 cheaper per usable result. If LTX 2.5 needs fewer retries for your particular shot, the total cost gap may narrow. For a realistic budget, start with the published unit prices, then track how many retries your own prompts need.

Visual Quality, Motion, and Prompt Following

LTX 2.5 has the stronger official quality stack, but that does not mean every prompt or workflow improves immediately.

Where LTX 2.5 Looks Stronger

Across launch-week ComfyUI and Stable Diffusion discussions, users most often highlighted:

• Faster-feeling iteration in distilled or optimized workflows.
• Sharper individual frames and less muddy fine detail.
• Better subject likeness in some image-to-video tests.
• Native multi-shot continuity.
• A stronger quality-to-speed balance than LTX 2.3 distilled.

Treat those observations as directional rather than guaranteed. Results vary with hardware, workflow settings, decoder choice, LoRA strength, and refinement settings.

Where LTX 2.5 Still Struggles

The same discussions repeatedly flagged:

• Incorrect object physics or unnatural movement.
• Camera motion that overshoots or loses scene logic.
• Prompt enhancer failures on difficult instructions.
• Slow diffusion-decoder or tiled-VAE stages on some setups.
• First-and-last-frame interpolation that can smear or treat endpoints like separate shots.
• Workflow-template and model-placement confusion during the first days of release.

Some users prefer their tuned LTX 2.3 first/last-frame workflow over the simpler 2.5 launch template. That does not prove the 2.5 model is worse at interpolation; it shows that a mature, tuned 2.3 graph can outperform an early default 2.5 graph for a narrow task.

Bottom line: LTX 2.5 has the stronger quality ceiling and a more advanced generation stack. LTX 2.3 can still be more predictable when you already have a proven workflow, especially for controlled interpolation or editing tasks.

What Changes for ComfyUI and Local Use

Both versions are natively supported in ComfyUI, but their model packaging differs.

LTX 2.3 uses a checkpoint that bundles the transformer, video and audio VAEs, and text projection, while the Gemma 3 encoder is downloaded separately. LTX 2.5 uses a split, Comfy-aligned pack with separate transformer, Gemma 4 text encoder, video VAE, audio VAE, duration head, and optional spatial or temporal upscalers.

The official LTX 2.5 quick start downloads roughly 66 GiB for a representative distilled setup. That is download size, not a simple minimum-VRAM specification. Practical memory use changes with checkpoint precision, CPU or disk offloading, decoder choice, attention backend, resolution, duration, and whether spatial or temporal refinement is enabled.

ComfyUI currently documents six native LTX 2.3 workflows—T2V, I2V, FLF2V, image-audio-to-video, IC-LoRA control, and ID-LoRA—versus three launch workflows for LTX 2.5: T2V, I2V, and FLF2V. The 2.5 model can do more than those three templates, but the older version currently has the broader documented template library.

Do not mix files casually. LTX 2.3 and 2.5 checkpoints and core components are not interchangeable. Lightricks says the large majority of 2.3 LoRAs and IC-LoRAs run on 2.5 without changes, but explicitly recommends validation before production use.

Which Model Should You Choose?

For a practical migration, do not replace every node and endpoint at once:

1. Keep the same reference image, prompt, aspect ratio, duration, and seed where the workflows allow it.
2. Compare the distilled versions first because that is where most iteration happens.
3. Evaluate motion, identity, prompt coverage, audio, and decode time separately.
4. Test first/last-frame and LoRA workflows independently from ordinary T2V or I2V.
5. Retain LTX 2.3 for editing endpoints until equivalent 2.5 support appears.

Downloading and configuring the full local stack is unnecessary if you only want to compare the basic workflows. You can start with the LTX text-to-video workspace or animate a reference in the image-to-video workspace. Check the model label and available controls before generating, because endpoint support can change independently from the open model release.

Prompting Differences That Matter

Both versions respond best to chronological, literal direction rather than disconnected keyword lists. LTX 2.5's native multi-shot ability makes explicit shot structure more useful.

LTX 2.3 Single-Shot Prompt

A medium tracking shot follows a cyclist riding through a rain-soaked city street at night. The cyclist leans into a left turn while water sprays from the tires. Neon shop signs reflect on the pavement. The camera stays at waist height and moves smoothly beside the bicycle. Natural traffic ambience, tire spray, and distant thunder. One continuous shot, no cuts.

LTX 2.5 Multi-Shot Prompt

A cyclist in a yellow rain jacket waits beneath a neon shop sign at night. Shot 1: wide establishing shot as heavy rain falls across the street. Cut to Shot 2: close-up as the cyclist looks left and grips the handlebars. Cut to Shot 3: low tracking shot as the bicycle accelerates through a puddle. Preserve the rider's face, yellow jacket, bicycle, blue-magenta lighting, rain intensity, and natural city ambience across every shot.

Do not overload a short duration with too many cuts. Two or three clear shots usually give actions more room to complete than a dense list of five or six edits.

FAQ

Is LTX 2.5 a direct replacement for LTX 2.3?

Not for every workflow. LTX 2.5 is the recommended newer generation model, but LTX 2.3 still supports official API editing endpoints and hosted configurations that 2.5 does not currently offer.

Is LTX 2.5 faster than LTX 2.3?

The improved distilled checkpoint is designed for efficient eight-step generation, and several early users report faster iteration. Exact end-to-end speed depends on the decoder, refinement pipeline, resolution, attention backend, quantization, offloading, and hardware. The higher-quality diffusion decoder can make the decode stage slower than the lighter convolutional option.

Does LTX 2.5 produce better video quality?

It has the stronger official fidelity stack: DFR, a diffusion video decoder, Gemma 4 prompt encoding, native multi-shot, and improved distillation. Early community results often look sharper, but physics, camera motion, and prompt adherence can still fail. A tuned 2.3 workflow may remain better for a specific task.

Can LTX 2.5 generate 4K video?

Yes. The local model stack supports 4K HDR-oriented production workflows, and the official LTX 2.5 Fast API supports up to 4K. The LTX 2.5 Pro API currently supports only 720p and 1080p.

Does LTX 2.5 support first and last frames?

Yes. LTX 2.5 supports first-and-last-frame generation in ComfyUI and via the image-to-video API's last-frame input. Automatic duration cannot be used at the same time because the endpoint needs a fixed length to reach the final frame.

Do LTX 2.3 LoRAs work with LTX 2.5?

Lightricks says most LTX 2.3 LoRAs and IC-LoRAs work on LTX 2.5 without changes, with some exceptions. Validate every adapter on representative prompts before using it in production.

Why is LTX 2.5 more expensive through the API?

The official pricing page does not give a single causal explanation, but the new version adds a more advanced rendering, decoding, and prompt-processing stack. Published per-second prices are higher at comparable tiers. Total project cost still depends on how many attempts are needed to get a usable result.

Should I uninstall LTX 2.3 after upgrading?

No. Keep 2.3 until your 2.5 workflows, LoRAs, decoder settings, and outputs are validated. It is also still required for API tasks such as Retake, Extend, Reframe, and HDR upscale.

Final Verdict

Choose LTX 2.5 for new generation work; keep LTX 2.3 as a cost-efficient and editing-capable fallback. LTX 2.5 is the more ambitious model, with native multi-shot generation, DFR, a diffusion decoder, Gemma 4 prompt handling, auto duration, and a better distilled path. Those changes make it the stronger foundation for future local workflows.

LTX 2.3 remains valuable because software migrations are about the whole pipeline, not just the newest checkpoint. Its API is cheaper, its Pro variant reaches 4K, its editing endpoints are broader, and its ComfyUI ecosystem has had more time to mature.

The best upgrade strategy is therefore selective: move T2V and I2V experiments to 2.5, compare them against your own stable 2.3 presets, and keep 2.3 wherever it still offers a feature, price, or workflow advantage.

Sources and Further Reading

• LTX 2.5 Hugging Face model card
• LTX 2.5 ComfyUI workflows
• LTX 2.3 ComfyUI workflows
• LTX 2.5 launch discussion on r/StableDiffusion
• LTX 2.5 ComfyUI launch discussion
• Early LTX 2.5 first/last-frame discussion