LTX-2.3
Video Available lightricks/ltx-2-3 · by Lightricks · Diffusion transformer (DiT)
Pricing — 1 offering(s)
Fast · 1080p
- $0.040 / second Current 2026-07-23 → present
Fast · 1440p
- $0.080 / second Current 2026-07-23 → present
Fast · 2160p (4K)
- $0.16 / second Current 2026-07-23 → present
Pro · 1080p
- $0.060 / second Current 2026-07-23 → present
Pro · 1440p
- $0.12 / second Current 2026-07-23 → present
Pro · 2160p (4K)
- $0.24 / second Current 2026-07-23 → present
Showing the active price and any recorded history. Full pricing history is available via the paid API — see API docs.
Capability profile
Operator guidance
Route here over LTX Video 0.9.7 or Wan 2.5 when native synchronized audio or higher (1440p/4K) resolution is required — both are gaps in those cheaper open-source-lineage options. Within LTX-2.3, Fast is the cost-optimized default; Pro trades ~33% higher per-second cost for better fidelity. Still meaningfully cheaper than closed premium audio-video models like Veo 3.1 ($0.40-0.60/s) at the cost of being a smaller, less-polished model. dev/distilled open-weight checkpoints exist on Hugging Face for self-hosting, not covered by this hosted-inference doc.
Use cases
- Workloads needing synchronized audio+video from a single open-weight-adjacent model, without stitching a separate TTS/audio pipeline
- Higher-resolution (up to 4K) generation than the registry's other open-source-lineage options (Wan 2.5, LTX Video 0.9.7)
- Existing LTX-line integrations upgrading from LTX Video 0.9.7 for audio support
Limitations
- No independently published video-quality benchmark score found — capability ratings above lean 'unknown' rather than repeating unverified vendor claims
- Release date (2026-03) is based on independent secondary reporting, not a Lightricks-owned page directly confirmed this session — Lightricks' pricing/docs pages (docs.ltx.video, console.ltx.io, ltx.video) all returned HTTP 403 to automated verification
- Exact max clip duration is inconsistently reported across sources (20s vs 30s depending on endpoint/source) — recorded as 20s here from the one page directly verified