Is LTX 2.5 Free? License, the $10M Threshold, and API Costs

"Yes, it's free" is true for most people and incomplete for everyone — LTX-2.5 is open-weights under the LTX-2.x Community License, which is free for entities under $10M annual revenue and carries a paid-license requirement above that line. There is also a clause that surprises people who redistribute fine-tunes: transferring fine-tunes may require a paid license.

The license is the same family LTX-2 and 2.3 shipped under — this is a continuity story, not a new surprise. But because 2.5 is a fresh release and its model card and official page both restate the terms, this guide walks the current text: what is free, where the threshold sits, the fine-tune clause, and what the official API costs if you would rather pay per second than self-host. Checked August 13, 2026.

The short answer

The official model card states the pricing logic in one line: "Under $10M annual revenue — commercial and production use at no cost under the LTX-2.x Community License." The official page repeats it as "open weights, permissive license, no mandatory branding, free use under $10M ARR."

What the $10M threshold means in practice

The threshold is per the license text referenced by the model card (the LTX-2.x Community License, in the repository). The key mechanics, as stated:

• Revenue is measured across the whole entity, including subsidiaries and affiliates under common control — the model card says this explicitly, so a small subsidiary inside a larger group cannot route around the threshold.
• Below the line: free commercial and production use, self-hosted, no per-generation billing, no per-seat lock-in.
• At or above the line: a paid commercial use agreement, which the official page describes as including full weights, engineering support, LoRAs, and flexible deployment options.

Practically, the same three buckets as 2.3 apply: individuals and small studios are unaffected; startups approaching $10M should put this on the roadmap before it becomes true (revenue measurement is entity-wide, so "close to the line" deserves a review); enterprises treat this as a procurement conversation with Lightricks, not a blog-summary decision.

The fine-tune transfer clause

The model card includes a sentence that does most of the surprise work: "Transfer of fine-tunes may require a paid license, in accordance with the LTX-2.x Community License."

What that means for the people actually affected:

• Running a fine-tune yourself: unaffected — training and local use sit under the community license like any other use.
• Distributing/selling a fine-tune: this is the trigger. If you ship a LoRA or full fine-tune built on LTX-2.5 to others (commercially or otherwise), the transfer clause is the thing to read in the license text — and the thing to ask Lightricks about before you build a business on redistribution.
• Internal fine-tunes for your own products: the standard below-threshold commercial use applies; the clause is about transfer, not use.

This mirrors what the release page frames as the license philosophy — free to build on under the line, paid when the commercial scale (or the transfer) crosses the documented boundary. As with any license, the summary here is not legal advice: read the text in the repository before making a deployment or distribution decision.

What "open weights" does and does not mean

Open weights under the community license is not Apache 2.0 — the comparison matters because people keep asking whether 2.5 is "open source" in the OSI sense. What is documented:

• You can download and run the weights — locally, on your hardware, no API dependency, no forced branding (the official page's comparison table lists "no mandatory branding" as available, unlike several closed competitors it contrasts against)
• You can fine-tune — the dev transformer is fully trainable, and Lightricks publishes a dedicated Pre-Trained checkpoint for fine-tuning foundations
• It is gated — the Hugging Face repo requires accepting the license and an approval step before download (see our download guide); that is a friction point, not a price
• The license, not a permissive OSS license, governs derivatives — with the revenue threshold and the fine-tune transfer clause above

The API option: pricing per second

If self-hosting is not your move, the official page lists API pricing billed per second of generated video:

At the official API's claimed speed (23.7 s wall-clock for a 10-second 1080p clip, measured end-to-end on fal.run including queue time), a 10-second 1080p clip costs $1.50 in output. The same page quotes 6.8 s for a 10-second 720p clip on their 2× GB200 on-prem hardware — the number that matters if you self-host at scale, and the reason the "free under $10M" route is the cost-efficient one for everyone below the threshold.

FAQ

Is LTX 2.5 free to use commercially? Yes, under $10M annual revenue (entity-wide, including subsidiaries and affiliates), per the LTX-2.x Community License. Above the threshold, a paid commercial use agreement applies.

Is LTX 2.5 open source? Open weights under the LTX-2.x Community License — not an OSI permissive license. Free below the $10M threshold; fine-tune transfer may require a paid license.

Can I sell a fine-tune or LoRA trained on LTX 2.5? The license states transfer of fine-tunes may require a paid license. Read the license text and talk to Lightricks before building a redistribution business on it.

How much does the LTX 2.5 API cost? $0.09/sec at 720p, $0.15/sec at 1080p, $0.19/sec at 2K, $0.37/sec at 4K — billed per second of generated video. A 10-second 1080p clip is $1.50.

Why do I have to request access on Hugging Face? The repo is gated: you agree to the license terms, Lightricks approves the request, then downloads work. It is a compliance gate, not a payment gate.

Bottom line

LTX 2.5 is free for everyone under $10M annual revenue — run it, use it commercially, fine-tune it — with a paid commercial license above that line and a paid-license trigger if you transfer fine-tunes. The API exists for those who prefer paying per second ($0.09–$0.37/sec by resolution). The license is the same family as 2.3: read the text before you build a business on it. And if you just want to see what the free route produces before committing either way, generate at ltx23.app.

Sources

Verified August 13, 2026 against primary documentation:

1. Lightricks/LTX-2.5 — Hugging Face model card — $10M threshold, entity-wide revenue measurement, fine-tune transfer clause, gated repo
2. LTX-2.x Community License (repository copy) — binding terms referenced by the model card
3. LTX-2.5 official model page (ltx.io) — API pricing per second (720p/1080p/2K/4K), speed measurements, license FAQ, no-mandatory-branding comparison
4. Lightricks/LTX-2 — GitHub README — open-weights repo, fine-tuning support, license reference
5. Lightricks/LTX-2.5-Pre-Trained — Hugging Face — dedicated fine-tuning foundation checkpoint

This is a summary of the license's stated mechanics, not legal advice. Read the LTX-2.x Community License text before any commercial deployment or fine-tune distribution.