LTX-2, LTX-2.3 and LTX-2.5 in ComfyUI: match files, encoders, VAEs and licence to the version
Official pages describe three LTX releases for ComfyUI, each with its own checkpoints, text encoder and VAE layout. This reference records those differences, the documented size rules and the licence conditions as the agreement texts state them.
Model identity and license record
Lightricks · LTX
Model-family license reference ↗This is a family-level reference, not a license determination for every file or revision. Check the exact publisher page for the model version you use.
No specific model file is recorded here; this entry is a reference, not a direct download.
Purpose and scope
This reference keeps files, encoders, VAEs and licence terms of LTX-2, LTX-2.3 and LTX-2.5 apart, as official pages described them on 2026-10-06.
Source-supported context
Versions. ComfyUI has separate tutorial pages for LTX-2 Source 1, LTX-2.3 Source 2 and LTX-2.5 Source 3. The repository calls LTX-2.5 recommended and LTX-2.3 legacy, still run by its pipelines Source 7. The LTX-2 and LTX-2.3 cards Source 4 Source 5 describe DiT-based audio-video models; checkpoint names carry 19b (LTX-2) and 22b (LTX-2.3, LTX-2.5) (Sources 1-3).
What each ComfyUI page lists. The LTX-2 page names ltx-2-19b dev, dev-fp8 and distilled checkpoints and x2 spatial and temporal upscalers; it lists no text encoder or VAE (Source 1). The LTX-2.3 page places fp8 dev and distilled checkpoints (from the Lightricks/LTX-2.3-fp8 repository) in checkpoints, a Gemma 3 12B text encoder in text_encoders, an x2 upscaler in latent_upscale_models and LoRAs in loras, lists no separate VAE, and offers T2V, I2V, first-last-frame and other templates (Source 2); the repository says LTX-2.3 checkpoints bundle the VAEs (Source 7). The LTX-2.5 page lists a distilled int8 transformer in diffusion_models, a Gemma 4 12B int8 text encoder in text_encoders, separate video and audio VAEs in vae, an x2 spatial upscaler, and T2V, I2V and first-last-frame templates (Source 3). The repository says stock Gemma 4 is not a substitute for the LTX-2.5 encoder (Source 7).
Size rules and memory. The LTX-2 and LTX-2.3 cards state that width and height must be divisible by 32 and the frame count by 8 plus 1 (Source 4) (Source 5); the gated LTX-2.5 card could not be read, so that rule is unverified for 2.5. The repository's fp8-cast and offload options belong to its own command-line code, not ComfyUI (Source 7). No fetched ComfyUI page gives a VRAM figure.
Licence. The repository's licence index Source 10 says the LTX-2 Community License (dated January 5, 2026) applies to LTX-2 versions, including LTX-2.3 until August 11, 2026, and the LTX-2.x Community License (dated August 11, 2026) applies to LTX-2.5 versions released since then and future LTX-2.x releases. The LTX-2.3 card's metadata links the first, its "Direct use license" line the second (Source 5); check which applies to your files. In both texts, entities with annual revenues of at least $10,000,000 ("Commercial Entities") must obtain a paid licence (Section 2.1 of the 2.x text) Source 8 Source 9. The 2.x text excepts a defined "Non-Commercial Purpose" (Section 2.2) that excludes revenue-generating use (Source 8). Attachment A item 20 in both bars use in products that directly compete with Lightricks without a separate commercial licence (Source 8) (Source 9).
Before you start
1. Treat the three versions as different packages: files, directories, encoders and VAEs differ.
2. Expect to update ComfyUI; the tutorials ask for the latest version.
3. Decide who reads the licence text.
Steps and checks
The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.
Step 1. Pick the version first, using the matching ComfyUI tutorial page and template, and record it before any download.
Step 2. Record each file by role, documented directory and repository source; do not carry a filename between versions.
Step 3. Check repository access: the LTX-2.5 tutorial describes a gated repository needing approved access [Source 3], and Hugging Face metadata showed no gate for the other repositories; confirm your account has access.
Step 4. Apply the model-card rules (width and height divisible by 32, frame count divisible by 8 plus 1) and keep the first request small.
Step 5. Record which licence agreement applies and whether your organisation might be a "Commercial Entity"; have the licence text, not this summary, reviewed by whoever handles contracts.
Step 6. Record the ComfyUI build used, and re-check templates after updates.
Completion check
The template loads without missing-model prompts, every recorded file has a version, role, directory and source, and a short request following the divisibility rules saves a clip. A saved clip is no evidence about memory or licence suitability.
Limitations and cautions
This is not legal advice. Licence statements paraphrase the raw agreement texts; confirm them in the originals. Your jurisdiction and contracts matter. The dates above are licence dates, not release dates; no release dates are stated. The LTX-2.5 card text was not readable (gated), so statements about it rest on the ComfyUI page, repository and file metadata. Earlier LTX-Video releases were not covered.
Original sources
- ComfyUI docs: LTX-2 — checked 2026-10-06.
- ComfyUI docs: LTX-2.3 — checked 2026-10-06.
- ComfyUI docs: LTX-2.5 — checked 2026-10-06.
- Hugging Face: Lightricks/LTX-2 — checked 2026-10-06.
- Hugging Face: Lightricks/LTX-2.3 — checked 2026-10-06.
- Hugging Face: Lightricks/LTX-2.5 — checked 2026-10-06.
- GitHub: Lightricks/LTX-2 — checked 2026-10-06.
- LTX-2.x Community License (LICENSE-2_x) — checked 2026-10-06.
- LTX-2 Community License (LICENSE-2) — checked 2026-10-06.
- Licence index (LICENSE) — checked 2026-10-06.
Prepared 2026-10-06 from the sources above. No GPU run, quality measurement or runtime guarantee is supplied.
Related troubleshooting and guides
Was this page helpful?
Anonymous. Only a yes/no counter is stored; no account, IP address or device details.
Sources & references
Editorial research from the cited public sources, dated 2026-10-06. This site did not run or test the workflow described.
01ComfyUI docs: LTX-2Source checked: 2026-10-0602ComfyUI docs: LTX-2.3Source checked: 2026-10-0603ComfyUI docs: LTX-2.5Source checked: 2026-10-0604Hugging Face: Lightricks/LTX-2Source checked: 2026-10-0605Hugging Face: Lightricks/LTX-2.3Source checked: 2026-10-0606Hugging Face: Lightricks/LTX-2.5Source checked: 2026-10-0607GitHub: Lightricks/LTX-2Source checked: 2026-10-0608LTX-2.x Community License (LICENSE-2_x)Source checked: 2026-10-0609LTX-2 Community License (LICENSE-2)Source checked: 2026-10-0610Licence index (LICENSE)Source checked: 2026-10-06Report an issue · b3b4c453-f248-5349-92bb-87022d0f243a
Related reading
Pages linked to this one by the editors.
Distinguish 5B TI2V from the 14B text/image-to-video routes. A shared Wan 2.2 label does not make weights, VAE, encoder and latents freely interchangeable.
- Wan 2.2
This guide follows the 5B TI2V image-input path specifically. The model-family reference explains alternatives; this page handles input, execution stages and output verification.
- Wan 2.2
Establish the runnable range of a particular setup, not a universal minimum-VRAM claim derived from a model name.
A model name can cover bundled checkpoints, split weights, quantized variants, text encoders and VAEs. Preserve enough identity information to know which artifact a workflow actually used.