LTX-Video publishes thirty frames a second
The card states that the released model produces thirty frames per second video at 1216x704. On this row the rate is not a texture note: it is the conversion factor for a length the page only ever expresses in frames. As of 2026-09-22.
| Statement | Value | Role of the frame rate |
|---|---|---|
| What the model produces | 30 FPS at 1216x704 | The published rate |
| Where quality holds | Frames below 257 | A ceiling the rate converts |
| Accepted frame counts | Divisible by 8, plus 1 | A rule the conversion cannot express |
Inclusion rule. Statements on the model card involving frames or frame rate. A seconds figure is not recorded, because the card does not print one. Order. The rate first, then what it is applied to.
1The highest rate here, and the smoothest motion
Thirty frames a second is what broadcast and web video mostly use, and it is nearly four times the lowest figure in this column. Motion reads as continuous, which is the expectation almost every ad placement's surrounding content sets.
As with the other two rows that publish a rate, nothing on the placement side requires it. The column records it because the difference between eight and thirty is the difference between output that looks generated and output that does not.
2Here the rate is load-bearing rather than descriptive
On the other two rows the rate is one more fixed property of a fixed format. On this one it is the only way to get from the card's frame ceiling to a length in the unit an ad slot uses, which is why the register keeps it beside the frame count rather than in a footnote.
The sheets still leave the length cell in seconds empty. The division is obvious and the result would carry a check date it does not deserve, and the divisibility rule on the same card makes the converted figure misleading in the bargain.
3Three published rates, three kinds of document
The three entries filling this column are a vendor user guide and two open-weight model cards. None of them is a rate card, and no rate card in this register mentions frame rate at all.
The reason is straightforward: frame rate is not a billing dimension. It surfaces in documents written for someone running inference, where the frame count is the quantity being budgeted, and stays invisible in documents written for someone buying a result.
4Where this cell sits in the column
| Generator | Frame rate |
|---|---|
| Amazon Nova Reel | 24 fps |
| CogVideoX | 8 fps |
| Google Veo | Not stated |
| Grok Imagine | Not stated |
| Hedra | Not stated |
| HeyGen | Not stated |
| Kling AI | Not stated |
| LTX-Video | 30 fps |
| MiniMax | Not stated |
| Pika | Not stated |
| PixVerse | Not stated |
| Runway | Not stated |
| SceneMixer | Not stated |
| Vidu | Not stated |
| Wan 3.0 | Not stated |
Inclusion rule. Every generator in the register against the frame rate column. Three rows carry a figure and twelve do not; the empty rows are the finding. Order. Alphabetical by generator name.
- What the released model produces30 FPS videos at a 1216x704 resolution
- Where the card says quality holds; length is published in framesWorks best on resolutions under 720 x 1280 and number of frames below 257not seconds
5Sources
Read from the Lightricks LTX-Video model card, checked 2026-09-22. The column itself is described on frame rate, and the rule that keeps surfaces and generators apart is on method. Next along this column: Amazon Nova Reel, CogVideoX.