LTX-2.3 LoRAs on LTX-2.5: most run unchanged; Sume has no LoRA field
Lightricks says the large majority of LTX-2.3 LoRAs and IC-LoRAs run on LTX-2.5 unchanged, with a few exceptions to test. Sume has no LoRA field.

Most of them, according to Lightricks. The LTX-2.5 model card says that, based on its testing, the large majority of LoRAs and IC-LoRAs trained on LTX-2.3 run on LTX-2.5 without changes, that a small number of exceptions exist, and that you should validate your adapters before production use. Sume cannot load a LoRA at all: its video request schema has no such field, and model_params has an empty allowlist.
The LTX statements are from the LTX-2.5 model card, read 2026-10-02. The Sume statements are from the OpenAPI schema and Video Router.
What does Lightricks say about LoRA compatibility?
The card's training section gives two statements. The dev transformer is fully trainable, and you can reproduce published LoRAs and IC-LoRAs with the LTX-2 Trainer. Separately, adapters trained on LTX-2.3 mostly carry over, with a small number of exceptions that the card does not name.
The card does not give a percentage, and it does not say which adapters break. The practical reading is a test, not a guarantee: run each adapter you depend on against a fixed prompt set before you swap models.
| Topic | What the card says |
|---|---|
| Training base | The dev transformer is fully trainable |
| Reproducing adapters | Use the LTX-2 Trainer for published LoRAs and IC-LoRAs |
| LTX-2.3 adapters on LTX-2.5 | The large majority run without changes; a small number of exceptions |
| Before production | Validate your adapters |
How do I validate an adapter after switching to LTX-2.5?
Keep five to ten prompts and first frames that you already have reference output for. Render each with the adapter on LTX-2.5 using the same seed and settings, and compare identity, motion and text legibility against the LTX-2.3 render. An adapter that changes character likeness or drops its trigger behavior is one of the exceptions the card warns about.
Do this on the distilled and the dev checkpoint if you use both, because the card lists them as different files.
Can I use a LoRA through the Sume API?
No. The Video Router request schema sets additionalProperties to false and lists fields such as model, prompt, image_url, reference_image_urls, resolution, duration and model_params. There is no LoRA field, and model_params is documented as reserved, empty allowlist in v1, so omit it or send {}.
If you need a style fixed across clips on Sume, the documented levers are reference images (reference_image_urls) on the models that accept them, and a first frame for image-to-video. Check each model's supported_input_references in the catalog.
Sources
Related posts
More in Models
- LTX-2.5 distilled or dev transformer: which file to download
Download the distilled bf16 transformer to generate (fixed 8-step schedule, CFG 1) and the dev one to train. int8 files are ComfyUI-only. Sume lists no LTX id.
- LTX-2.5 duration predictor: optional, and Sume sets seconds
LTX-2.5 has an optional duration predictor that sets the frame count from the prompt. Sume has no such mode: you send duration in whole seconds.
- Is LTX-2.5 gated on Hugging Face? Agree, log in, then download
Yes: the LTX-2.5 repository is gated. Agree to share your contact details on the model page, run hf auth login, then hf download. It is free under $10M revenue.
- MAI-Image-2.6 output cap is 2,359,296 pixels; Sume sizes differ
MAI-Image-2.6 sets a 2,359,296-pixel ceiling and a 768-pixel minimum edge. Sume sets size per model with tiers, ratios and, for GPT models, custom pixels.
Written by Sume