Instructions to use Lightricks/LTX-2.5 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Diffusion Single File
How to use Lightricks/LTX-2.5 with Diffusion Single File:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- LTX-2
How to use Lightricks/LTX-2.5 with LTX-2:
# Install the LTX-2 pipelines git clone https://github.com/Lightricks/LTX-2.git cd LTX-2 uv sync --extra natten
# Download weights from this repo # Substitute filenames from this repo's "Files and versions" if they differ hf download Lightricks/LTX-2.5 \ diffusion_models/<distilled-transformer>.safetensors \ text_encoders/gemma4-12b-with-proj-ltx-2.5-bf16.safetensors \ vae/<video-vae>.safetensors \ vae/<audio-vae>.safetensors \ latent_upscale_models/<spatial-upsampler>.safetensors \ latent_upscale_models/<temporal-upsampler>.safetensors \ --local-dir models/LTX-2.5 # DFR requires the detailing IC-LoRA (separate repo; strength is fixed at 0.5) hf download Lightricks/LTX-2.5-22b-IC-LoRA-Pixel-Spatial-Upscaler --local-dir models/LTX-2.5-22b-IC-LoRA-Pixel-Spatial-Upscaler# Distilled LTX-2.5 pipeline (fast) uv run python -m ltx_pipelines.distilled \ --transformer-path models/LTX-2.5/diffusion_models/<distilled-transformer>.safetensors \ --text-encoder-path models/LTX-2.5/text_encoders/gemma4-12b-with-proj-ltx-2.5-bf16.safetensors \ --video-vae-path models/LTX-2.5/vae/<video-vae>.safetensors \ --audio-vae-path models/LTX-2.5/vae/<audio-vae>.safetensors \ --spatial-upsampler-path models/LTX-2.5/latent_upscale_models/<spatial-upsampler>.safetensors \ --num-frames 121 \ --prompt "A beautiful sunset over the ocean" \ --output-path output.mp4 # For image-to-video, add: --image path/to/image.jpg 0 0.8# DFR pipeline (higher detail fidelity; optional temporal 2x/4x) uv run python -m ltx_pipelines.dfr_pipeline \ --transformer-path models/LTX-2.5/diffusion_models/<distilled-transformer>.safetensors \ --text-encoder-path models/LTX-2.5/text_encoders/gemma4-12b-with-proj-ltx-2.5-bf16.safetensors \ --video-vae-path models/LTX-2.5/vae/<video-vae>.safetensors \ --audio-vae-path models/LTX-2.5/vae/<audio-vae>.safetensors \ --spatial-upsampler-path models/LTX-2.5/latent_upscale_models/<spatial-upsampler>.safetensors \ --temporal-upsampler-path models/LTX-2.5/latent_upscale_models/<temporal-upsampler>.safetensors \ --detailing-lora models/LTX-2.5-22b-IC-LoRA-Pixel-Spatial-Upscaler/ltx-2.5-22b-ic-lora-pixel-spatial-upscaler-x2-1.0.safetensors \ --spatial-upscalings 1 \ --temporal-upscalings 1 \ --height 1088 \ --width 1920 \ --num-frames 121 \ --prompt "A beautiful sunset over the ocean" \ --output-path output.mp4 # For 4K: --spatial-upscalings 2 --width 3840 --height 2176 # For image-to-video, add: --image path/to/image.jpg 0 0.8 - Notebooks
- Google Colab
- Kaggle
Features improvement
Feature Request: Multi-reference character consistency (like Seedance's 50-image reference)
LTX-2.5's IC-LoRA currently focuses on motion/structure transfer (Canny, Depth, Pose) rather than direct multi-reference character consistency. Competing models like Seedance 2.5 support up to 50 reference images for strong character consistency across shots.
It would be great if LTX's next version included native support for multiple reference images (face/character sheets) to lock character identity across generations, similar to what Seedance offers. This would make LTX much stronger for AI filmmaking and character-driven storytelling workflows.
Additionally, Seedance 2.5 generates a single native clip up to 30 seconds long (with multi-round extensions up to 180 seconds in beta) at 4K resolution in one pass. It would be great to see LTX push its native single-generation length closer to this range as well, since longer coherent single-pass clips reduce the need for manual stitching in production workflows.
Thanks for the great work on LTX-2.5!
Feature Request: Multi-reference character consistency (like Seedance's 50-image reference)
LTX-2.5's IC-LoRA currently focuses on motion/structure transfer (Canny, Depth, Pose) rather than direct multi-reference character consistency. Competing models like Seedance 2.5 support up to 50 reference images for strong character consistency across shots.
It would be great if LTX's next version included native support for multiple reference images (face/character sheets) to lock character identity across generations, similar to what Seedance offers. This would make LTX much stronger for AI filmmaking and character-driven storytelling workflows.
Additionally, Seedance 2.5 generates a single native clip up to 30 seconds long (with multi-round extensions up to 180 seconds in beta) at 4K resolution in one pass. It would be great to see LTX push its native single-generation length closer to this range as well, since longer coherent single-pass clips reduce the need for manual stitching in production workflows.
Thanks for the great work on LTX-2.5!
This is actually great feature to have i hope they implement it soon . Really love ltx 2.5 .
I agree! Native support for multiple face and character references would be a valuable addition, especially for film restoration.
Being able to supply clear references from different angles could help preserve an actor’s identity across shots while keeping the original expressions, movement, and performance intact.
I created LTX Reference Restorer, a locally hosted web app to help organize this workflow: source clips, actor references, shot guides, versioned render jobs, and side-by-side comparisons.
GitHub: LTX Reference Restorer
The project includes example workflows using public-domain films such as The Great Train Robbery, St. Louis Blues, and The Hitch-Hiker, with documented Library of Congress sources.
It’s an early preview: the reference-management and baseline-upscaling workflows are tested, while actual LTX inference remains unverified. My goal is to make reference-guided restoration easier to prepare, evaluate, and improve. Having stronger multi-reference support built directly into LTX would make this kind of workflow much more useful.
Thanks to the team for continuing to develop LTX!