Runway publishes five to fifteen on Gen-4.5
The input reference publishes durations of five to fifteen seconds on Gen-4.5, stated once for text-to-video and image-to-video together. The pricing guide charges per second of output, so on this row the duration parameter is also the invoice. As of 2026-09-22.
| Property | What the page states | What it means for a request |
|---|---|---|
| Range on Gen-4.5 | 5 to 15 seconds | Any whole value inside it |
| Input mode | The same range for text and image conditioning | No re-planning between modes |
| Billing | Per second of output | A longer request costs proportionally more |
Inclusion rule. Duration statements in the input reference for the current model, with the billing basis from the same vendor's pricing guide. Earlier model generations are not recorded here. Order. The parameter, then what it does not depend on, then what it does.
1One range for both input modes is worth stating
Several rows in this register vary their length by model, by version or by resolution. This one states the range once and applies it to a prompt and to a conditioning image alike, which means a sequence can mix the two without re-checking the arithmetic.
For serial advertising that mixing is the normal case. An establishing beat comes from a prompt and the shots with a cast in them come from reference frames, and a shared range keeps the shot list in one unit across both.
2Per-second billing makes the length a budget line
Where a vendor charges per second, the duration parameter stops being free in both senses. Fifteen seconds costs three times five, and the difference between a draft and a final is measured in the same unit as the difference between two cuts.
That pushes iteration towards the bottom of the range. Composition, lighting and cast can be settled at five seconds and the length raised once, which is cheaper than discovering at fifteen that the framing was wrong.
3Fifteen seconds against the formats that exist
Four other rows share this ceiling, and it puts a sixty second non-skippable at four calls and three joins. A thirty second window is two calls, and the five to six second bumper is one with a floor of five that lands almost exactly on the format.
The bumper case is the neat one: the shortest legal request here is the length of the shortest ad format, so nothing is paid for and discarded. That coincidence does not hold on the rows whose floor is a fixed six seconds or an increment of six.
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.
- Gen-4.5Durations are 5-15 seconds on Gen-4.5, for text-to-video and image-to-video alikestated per endpoint
- How generation is billedCharged per second of output, with gen4_turbo at 5 credits per second and gen4.5 at 12
5Sources
Read from the Runway API input reference, 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: SceneMixer, Vidu.