LTX and Luma: pipeline hooks
LTX and Luma document different things on five of the nine hooks: editing hand-off, downloads, file formats, SDKs and job signals. From 4 source pages, read 2026-09-25; no maker pays to be listed.
| Feature | LTX | Luma |
|---|---|---|
| Public API | An API for its own models | An API for its own models |
| Agent and automation hooks | Not documented in the docs read | Not documented in the docs read |
| Highest resolution named | 4K | 4K |
| Hand-off to editing software | XML export for editing | EXR for compositing |
| Subtitle files | Not documented in the docs read | Not documented in the docs read |
| The finished file | A link or file that expires | Not documented in the docs read |
| File formats named | MP4 | EXR |
| Official SDKs | Not documented in the docs read | SDKs in two or more languages |
| Finished-job signal | A status polled until done | A webhook or callback URL |
Inclusion rule. The nine hooks every tool in the register is read for. Order. The order hooks take on every tool page.
1Where they part
LTX documents downloads, which Luma's pages leave out. Luma documents SDKs, which LTX's pages leave out. For API access the two match: an API for its own models. For resolution the two match: 4K. For editing hand-off, LTX names XML export for editing and Luma EXR for compositing. For file formats, LTX names MP4 and Luma EXR. For job signals, LTX names a status polled until done and Luma a webhook or callback URL. Neither documents agent hooks or subtitle files.
2From each tool's documentation
Hand-off to editing software
Post-production/editing is allowed via XML export
Forward Festival Berlin, rules of the LTX sixty-second film contest
Native HDR Generation and 16-bit EXR Export so AI work composites alongside live-action plates in your users' Resolve or Nuke.
Luma, API page
The finished file
Output URLs expire independently of job status.
LTX, API documentation: async jobs
Luma's documentation read says nothing here.
Finished-job signal
We recommend waiting at least 5 seconds between polls.
LTX, API documentation: async jobs
It will get status updates (dreaming/completed/failed)
Luma, API documentation: Python video generation
- RequirementsEditing through an XML export, as the rules of its own film competition put it
- Features16-bit EXR export for compositing in Resolve or Nuke
- RetentionOutput URLs that expire, to be downloaded or re-hosted once a job completes
- Polling guidanceAsync jobs polled for status, at least five seconds apart
- CallbacksA callback URL that receives status updates and the video
3A third tool on getting the file out, beside LTX and Luma
| Field | SceneMixer | Source |
|---|---|---|
| The finished file | A full-quality download and a share link; the browser plays a lighter copy | SceneMixer, guide to compositing and sharing an episode |
Inclusion rule. Fields on which SceneMixer's pages state something; most toolkit fields are not its subject. Order. The order fields take on every tool page.