HeyGen publishes thirty minutes, then fifty of them
The usage limits page states thirty minutes per scene with fifty scenes per video. It is the largest length figure in this register, and it is stated twice: once for a unit of output and once for how many of those units one job holds. As of 2026-09-22.
| Ceiling | Value | What the unit is |
|---|---|---|
| Per scene | 30 minutes | One continuous stretch of the same setup |
| Per video | 50 scenes | How many stretches one job carries |
| Implied job length | Not stated as a single number | The page never multiplies them |
Inclusion rule. Ceilings this usage limits page states about output length. The implied product is shown as not stated because the page does not perform the multiplication itself. Order. Inner unit first, then the container, then what the page declines to state.
1Two ceilings answer two different questions
A per-scene figure answers how long one uninterrupted stretch can run. A per-video figure answers how many such stretches a single job assembles. Every other row in this column answers only the first, and leaves assembly to whatever edits the pieces afterwards.
That second ceiling is the useful one for advertising, because it says the joining step happens inside the product. A piece made of four setups is one job here, and the seams are the vendor's problem rather than an editor's.
2The register does not multiply the two
Fifty scenes of thirty minutes is a figure the page never prints, and printing it here would be publishing an inference as a vendor statement. The sheets record what a page says, so the product stays in the table as not stated.
The restraint has a practical point as well. Ceilings published separately usually interact with quotas, storage or processing time that the same page governs elsewhere, and a multiplied figure invites a plan that no single sentence on the page supports.
3What the scale means against a sixty second slot
Thirty minutes against sixty seconds is a ratio of thirty to one. Nothing in the format binds, and the interesting question moves entirely off this column: whether a presenter speaking to camera is the right form for the placement, and what the picture has to do for the fifty-five seconds after the message has landed.
The register notes that the same page publishes output dimensions as a range from 128 to 4,096 pixels a side rather than as tiers. A row this permissive on length is equally permissive on size, and both figures describe a tool built for a brief that is not an advertisement.
4Where this cell sits in the column
| Generator | Duration |
|---|---|
| Amazon Nova Reel | 6 s increments, up to two minutes |
| CogVideoX | 6 s, at 49 frames |
| Google Veo | 4, 6 or 8 s |
| Grok Imagine | 1 to 15 s |
| Hedra | 10 minutes |
| HeyGen | 30 minutes per scene |
| Kling AI | Not stated |
| LTX-Video | Frames, never seconds |
| MiniMax | 4 to 15 s |
| Pika | 5 s and 10 s, 20-25 s on Pikaframes |
| PixVerse | 1 to 15 s on version 6 |
| Runway | 5 to 15 s on Gen-4.5 |
| SceneMixer | Thirty seconds on the Wan tiers, fifteen on H3 |
| Vidu | Not stated |
| Wan 3.0 | 2 to 30 s |
Inclusion rule. Every generator with a row in this register, carrying whatever its own page states as a length. A page that states none keeps its row and says so. Order. Alphabetical by generator name.
- Longest output stated anywhere in this register30 minutes per scene, with 50 scenes per video
- Output sizeWidth and height must each be between 128 and 4,096 pixelspublished as a range not a ladder
5Sources
Read from the HeyGen usage limits page, checked 2026-09-22. The column itself is described on duration, and the rule that keeps surfaces and generators apart is on method. Next along this column: Kling AI, LTX-Video.