LTX-2.5 license changed Aug 11, 2026: what differs from January
The August 11, 2026 LTX-2.x license adds a Non-Commercial carve-out, a current-version clause and provenance duties. What both texts say, side by side.

Lightricks now publishes two LTX Community License texts: LTX-2 dated January 5, 2026, and LTX-2.x dated August 11, 2026, which applies to all LTX-2.5 versions released since that date and future LTX-2.x releases. Both set the commercial line at annual revenue of at least $10,000,000. The August text adds a defined Non-Commercial Purpose carve-out, a duty to keep provenance and watermark features, and a note that older versions are used at your own risk. Compared from the license files, read 2026-10-08. This is a reading aid, not legal advice.
Side by side
The January column reflects the text of the LTX-2 license file; where I found no matching clause by searching the file, the cell says so rather than guessing.
| Topic | LTX-2 license, January 5, 2026 | LTX-2.x license, August 11, 2026 |
|---|---|---|
| Commercial line | Entities with annual revenues of at least $10,000,000 need a paid commercial license | Same $10,000,000 line; the paid license is called a Commercial Use Agreement |
| Entity size | Counts subsidiaries, affiliates and companies under common control together | Same aggregation: subsidiaries, affiliates and companies under common control count together (Section 1.6) |
| Non-Commercial Purpose | No defined carve-out found in the file | Section 2.2 lets a Commercial Entity test, evaluate or research in a non-production environment without payment |
| What is not Non-Commercial | Not defined | Revenue-generating use, use that touches end users, and training or distilling a model for commercial use |
| Provenance and watermarks | No matching clause found in the file | Do not remove or circumvent watermarking, metadata or latent disclosures; revocation if you do |
| Versions | Applies to LTX-2 | Applies to LTX-2.5 versions released since August 11, 2026 and later LTX-2.x |
What the Non-Commercial carve-out allows
Section 2.2 is narrow. It covers an individual using the weights for research, hobby or private study with no link to a business, and a company using them for testing, evaluation or R&D in a non-production or development environment, provided it receives no direct or indirect payment from that use. A staging server that your paying customers never touch is inside the carve-out, by the text. A feature that ships to users, or a model trained for a commercial product, is outside it.
That second case matters for fine-tuning. The text names training, fine-tuning or distilling a model for commercial use as not Non-Commercial, so a company above the threshold needs the paid agreement before that work starts.
The provenance clause in practice
The August text points to the EU AI Act and the California AI Transparency Act by name and requires you to maintain, not remove, disable, alter or circumvent, the transparency features that ship with the model or are applied to outputs, including any latent disclosure. If Lightricks believes you modified the model so it can no longer include a required disclosure, it may revoke the license on notice. A pipeline that re-encodes or strips metadata is worth a review against that sentence.
What to record
Keep a short license log for any LTX deployment:
- The license date you downloaded under (January 5 or August 11, 2026) and the repository commit.
- Whether your entity, with affiliates, is at or above $10,000,000 in annual revenue.
- Whether each use is production, end-user facing, or training; those fall outside Section 2.2.
- Sume does not list LTX models in its video catalog, so a Sume job is not covered by either text; it follows the terms of whichever listed model you call.
How to read this table
The two files are separate documents with separate dates, so a copy of the weights you downloaded earlier stays under the text you accepted then. The August file says it applies to LTX-2.5 versions released since August 11, 2026 and to future LTX-2.x releases. Whether an older download can be re-licensed is a question for counsel and for Lightricks, not for this post.
Sources
Related posts
More in Models
- LTX-2.5 quick start downloads 66 GiB: the five files and a disk plan
The LTX-2 README quick start pulls about 66 GiB for five LTX-2.5 files, including a 12B Gemma text encoder. What to budget, and what Sume lists instead.
- Mac or Windows team: which open video models need Linux and CUDA?
HunyuanVideo and HunyuanVideo-1.5 list Linux; LTX-2.5's fastest decoder is Linux plus CUDA; H3 has a Mac route. What each page says and a hosted option.
- MAI-Transcribe-2: 60 languages, 17 more than 1.5, and the Sume hint
Microsoft lists 60 languages for MAI-Transcribe-2, 43 for MAI-Transcribe-1.5, so 17 new ones. Sume STT takes a language_code hint or auto-detects.
- MAI-Transcribe-2-Streaming runs in 4 regions, MAI-Voice in 14
Microsoft lists four regions for MAI-Transcribe-2-Streaming and 14 for MAI-Voice-2.1; three overlap. Sume's STT and TTS requests have no region field.
Written by Sume