Migrating from LTX-2 to LTX-2.3

Updated July 07, 2026 22:36

LTX-2 is being deprecated on July 15, 2026 and removed on August 15, 2026 — the hard deadline to switch. Update your integration to use LTX-2.3 model IDs before then. We recommend migrating as soon as possible rather than waiting for the deadline.

What's changing and when

July 15, 2026 — LTX-2 is deprecated. Requests using ltx-2-fast or ltx-2-pro are automatically routed to LTX-2.3 and billed at LTX-2 rates.
August 15, 2026 — LTX-2 is fully removed. Requests using LTX-2 model IDs will return an error. This is the hard deadline — migrate before then to avoid disruption.

The transition period between July 15 and August 15 is there to give you time to migrate — not to delay it. We recommend updating your integration now so you're not rushing before the removal date.

How to migrate

Update the model field in your API requests:

Replace ltx-2-fast with ltx-2-3-fast
Replace ltx-2-pro with ltx-2-3-pro

No other changes are required. LTX-2.3 is a drop-in replacement — all existing parameters and endpoints continue to work.

Will my outputs change?

LTX-2.3 is our latest model, with improved quality, performance, and capabilities over LTX-2. If your workflow depends on consistent output style, test your prompts against LTX-2.3 before August 15 to check for any differences.

What happens if I don't migrate in time?

After August 15, requests specifying ltx-2-fast or ltx-2-pro will fail with an error. Update your integration before then to avoid any disruption to your product or workflow.

For full migration details, see the LTX-2 deprecation notice in the developer docs.