Instructions to use RuneXX/LTX-2.3-Workflows with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LTX-2
How to use RuneXX/LTX-2.3-Workflows 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 RuneXX/LTX-2.3-Workflows \ 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.3-Workflows # 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.3-Workflows/diffusion_models/<distilled-transformer>.safetensors \ --text-encoder-path models/LTX-2.3-Workflows/text_encoders/gemma4-12b-with-proj-ltx-2.5-bf16.safetensors \ --video-vae-path models/LTX-2.3-Workflows/vae/<video-vae>.safetensors \ --audio-vae-path models/LTX-2.3-Workflows/vae/<audio-vae>.safetensors \ --spatial-upsampler-path models/LTX-2.3-Workflows/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.3-Workflows/diffusion_models/<distilled-transformer>.safetensors \ --text-encoder-path models/LTX-2.3-Workflows/text_encoders/gemma4-12b-with-proj-ltx-2.5-bf16.safetensors \ --video-vae-path models/LTX-2.3-Workflows/vae/<video-vae>.safetensors \ --audio-vae-path models/LTX-2.3-Workflows/vae/<audio-vae>.safetensors \ --spatial-upsampler-path models/LTX-2.3-Workflows/latent_upscale_models/<spatial-upsampler>.safetensors \ --temporal-upsampler-path models/LTX-2.3-Workflows/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
How to use GemmaAPITextEncode node in LTX 2.3 Workflow
Hello RuneXX,
Thank you for sharing the detailed LTX 2.3 workflows - it is well structured and works reliably.
I have been using your LTX-2.3_-_I2V_T2V_Basic_Custom_Audio.json workflow, and it runs perfectly on my setup. However, I am exploring ways to reduce memory usage.
Specifically, I am interested in integrating the GemmaAPITextEncode node into your workflow. Could you please guide me on how to properly configure it.
Will check how the GemmaAPITextEncode is in Comfy, see if it can be easily added ;-)
Tested it, works fine. +
I'll add and upload to the workflow you wnated, but if you want to try yourself its basically just bypass all the clip and prompt nodes that are in the workflow (select nodes and ctrl+b to bypass)
Then get the API key you need https://console.ltx.video/
And instead connect like this_
Or even simpler, just prompt directly in the GemmaAPI node itself:
At the bottom of that node, i think it looks in the checkpoint folder if i remember right.
So copy 2.3_text_projection_bf16.safetensors over to the checkpoint folder also, so that this gemma node can see it
EDIT:
Checked, yes it looks for ltx-2.3_text_projection_bf16.safetensors in the checkpoint folder.
So add the file there as well, and enter your api key. And all should work ;-)
At the bottom of that node, i think it looks in the checkpoint folder if i remember right.
So copy 2.3_text_projection_bf16.safetensors over to the checkpoint folder also, so that this gemma node can see itEDIT:
Checked, yes it looks for ltx-2.3_text_projection_bf16.safetensors in the checkpoint folder.
So add the file there as well, and enter your api key. And all should work ;-)
Works perfectly, thanks brother


