Quick answer
Answer the LTX 2 query with dates first.
LTX 2 is now a migration question, not a new API adoption question. LTX docs say ltx-2-fast and ltx-2-pro were deprecated on July 15, 2026, requests are automatically served by LTX-2.3 during the transition while keeping original LTX-2 pricing, and LTX-2 removal is scheduled for August 15, 2026, after which requests return an error.
Migrate before the removal date. For API jobs, decide whether the safest target is LTX-2.3 or LTX-2.5, then retest output, price, duration, audio, and any last-frame behavior. For local or open-weight experiments, use the LTX-2 repository, model cards, license terms, hardware notes, and community issues as separate proof from the deprecated hosted IDs.
Reader fit
Answer the LTX 2 query with dates first.
Visitors need to know whether LTX 2 means deprecated hosted API IDs, open-weight artifacts, or a migration path to LTX-2.3 and LTX-2.5.
| What happened to LTX 2? | The LTX API changelog says ltx-2-fast and ltx-2-pro were deprecated on July 15, 2026. LTX API Docs |
|---|---|
| Which IDs are affected? | The affected hosted API IDs are ltx-2-fast and ltx-2-pro. Loose LTX 2 references in scripts and prompts should be resolved to exact IDs. LTX API Docs |
| What happens before August 15? | During the transition, LTX-2 requests are automatically served by LTX-2.3 while remaining billed at the original LTX-2 rates until removal. LTX API Docs LTX API Docs |
| What happens on August 15, 2026? | The changelog says LTX-2 models are removed from the API and requests to the old model IDs return an error. LTX API Docs |
| What replaces it? | Hosted jobs should be retested on a named replacement such as LTX-2.3, LTX-2.5 Fast, or LTX-2.5 Pro, with price and output-drift checks. LTX API Docs LTX API Docs |
| Is open-source LTX-2 still useful? | Yes. The repository and model-card surfaces remain useful for local inference, LoRA, license, model files, hardware, token, and community issue checks. Lightricks / GitHub Lightricks on Hugging Face LTX Studio Lightricks / GitHub |
| What should Coachix prepare? | Coachix should inventory old IDs, assign a replacement route, run one small fixture, record price and output drift, and keep a fallback owner. Reddit search Google Search |
- Find ltx-2-fast and ltx-2-pro references.
- Migrate before the removal date.
- Retest with a named replacement route.
Checked facts
Facts to verify before adoption.
Use these rows to separate official signals, upstream cards, event reports, and community friction.
| Deprecation date | The LTX API changelog says ltx-2-fast and ltx-2-pro were deprecated on July 15, 2026. LTX API Docs |
|---|---|
| Removal date | The same changelog says that on August 15, 2026 LTX-2 models are removed from the API and requests to ltx-2-fast or ltx-2-pro return an error. LTX API Docs |
| Transition behavior | During the transition period, LTX-2 requests are automatically served by LTX-2.3 while remaining billed at the original LTX-2 rates until removal. LTX API Docs LTX API Docs |
| Likely hosted replacement | LTX docs list current LTX-2.5 Fast and Pro routes with text-to-video, image-to-video, and audio-to-video support; use them as a fresh evaluation target rather than a silent drop-in. LTX API Docs LTX API Docs |
| Open-source route | The Lightricks LTX-2 repository and model-card surfaces remain useful for open-weight, inference, LoRA, hardware, token, and license checks, even though the old hosted model IDs are being removed. Lightricks / GitHub Lightricks on Hugging Face LTX Studio |
| Migration verdict | Treat every saved prompt, script, and workflow that still says LTX 2 as technical debt. Replace the model ID, run a small retest, record cost and output drift, and keep a fallback. LTX API Docs LTX API Docs Lightricks / GitHub |
Evaluation worksheet
Write the adoption note before the first serious run.
For this LTX 2 migration, define the input, expected output, failure condition, reviewer, manual stop, and next action before the first run. Judge results against that note, not surface polish.
Decision helper
Choose the first LTX 2 check
Legacy API route
Start here when scripts still call ltx-2-fast or ltx-2-pro. Replace the model ID before August 15, 2026 and run one small output-drift check.
Safe sequence
Move from interest to a reviewable trace.
- 01
Search saved scripts, prompts, docs, and routing rules for ltx-2-fast, ltx-2-pro, and loose LTX 2 names.
- 02
Replace each legacy route with a named candidate such as LTX-2.3, LTX-2.5 Fast, LTX-2.5 Pro, or an open-weight LTX route.
- 03
Run one small fixture per route and compare output, price, duration, resolution, audio, artifacts, and error behavior.
- 04
Record a proceed, retry, fallback, or blocked verdict with the replacement model ID, review owner, and rollback path.
Field guide
Treat LTX 2 as a migration label now.
The broad ltx 2 query can mean a hosted API model, an open-source model family, a repository, a model card, or old launch coverage. The first job is to sort those meanings. Hosted ltx-2-fast and ltx-2-pro are the time-sensitive part because the API changelog gives exact deprecation and removal dates.
The transition behavior matters because it can hide risk. If an old LTX 2 job is temporarily served by LTX-2.3, it may appear to work until removal. That does not mean the workflow is migrated. It means the route needs a named replacement before the hard error date.
LTX-2.5 is the new evaluation path for many hosted jobs, but it still needs a real retest. Fast and Pro have different output ceilings and price rows. Image-to-video, audio-to-video, automatic duration, and last-frame behavior should be checked against the actual task rather than assumed.
Open-weight LTX-2 work is a separate route. The repository and model card can support local inference, LoRA, or research experiments, but they do not preserve deprecated hosted IDs. Keep local model proof, license proof, hardware proof, and API migration proof in separate notes.
- Find every ltx-2-fast and ltx-2-pro reference before August 15, 2026.
- Do not mistake temporary LTX-2.3 serving for a completed migration.
- Retest outputs, price, audio, duration, and fallback with a named replacement model.
Copyable handoff
Copyable prompt for an LTX 2 migration check
Audit this workflow for LTX 2 migration. Use only the current LTX docs, changelog, pricing, repository, and model-card evidence supplied. Find any ltx-2-fast, ltx-2-pro, or loose LTX 2 reference. For each route, propose LTX-2.3, LTX-2.5 Fast, LTX-2.5 Pro, open-weight LTX, MiniMax H3, or another fallback. Include deprecation date, removal date, price evidence, output-drift test, audio and duration checks, rights boundary, owner, deadline, and rollback. Return proceed, retry, fallback, or blocked.
- Do not start a new hosted workflow on ltx-2-fast or ltx-2-pro.
- Do not assume LTX-2.3 transition serving will continue after August 15, 2026.
- Do not replace LTX 2 with LTX-2.5 without retesting price, output drift, audio, duration, and resolution.
- Do not mix open-weight repository proof with hosted API availability proof.
FAQ
LTX 2 migration questions builders should answer.
Is LTX 2 deprecated?
Yes. The LTX API changelog says ltx-2-fast and ltx-2-pro were deprecated on July 15, 2026.
When is LTX 2 removed?
The LTX changelog says LTX-2 removal is scheduled for August 15, 2026, when requests to old model IDs return an error.
What should replace ltx-2-fast or ltx-2-pro?
For hosted API routes, evaluate LTX-2.3 or LTX-2.5 with a small fixture. The right target depends on output quality, price, duration, audio, resolution, and account access.
Does the LTX-2 repository still matter?
Yes, for open-weight, local inference, LoRA, license, hardware, and community setup checks. It does not make deprecated hosted API IDs safe to keep.
Should I use LTX-2.5 instead?
Often it is the right next route to test, especially when text-to-video, image-to-video, audio-to-video, visible pricing, or LTX Fast 4K output matter. Retest before replacing production jobs.
Related Coachix pages