Veo publishes three lengths, one of them conditional
Veo 3.1 publishes eight, six and four seconds, and attaches a condition to the longest of them: eight seconds only at 1080p or 4k, or when reference images are used. The length column and the resolution column cannot be read apart on this row. As of 2026-09-22.
| Length | Available when | Cost of the condition |
|---|---|---|
| 8 seconds | At 1080p or 4k, or with reference images | The cheapest tier is ruled out |
| 6 seconds | Stated without a condition | None |
| 4 seconds | Stated without a condition | None |
Inclusion rule. Lengths this documentation page states for Veo 3.1 and Veo 3.1 Fast, with the condition the page attaches to each. A length available on an earlier model version is not listed. Order. Longest first, which is the order the condition becomes relevant in.
1A coupled figure cannot be read one column at a time
This is the clearest case in the register of two axes that refuse to separate. Reading the length cell alone gives eight seconds; reading the resolution cell alone gives three tiers. Reading them together gives a smaller product: eight seconds is unavailable at 720p, so the cheapest rung and the longest run cannot be had at once.
For a media plan that matters at the budget line rather than the spec line. A slot filled in eight second pieces is being filled at 1080p or above whether or not the placement asked for it, and the resolution decision was made by the duration parameter.
2Reference images buy the same length by another route
The page offers a second way to reach eight seconds: supply reference images. That is a production choice rather than a quality tier, and for serial advertising it is the choice most likely to be made anyway, because references are how a cast holds its appearance across separately generated pieces.
So the condition often costs nothing in practice. It is still worth recording, because a text-only request at 720p is capped at six seconds and a shot list written against eight will come back short without any error to explain it.
3Eight seconds against the slots that exist
Eight is the smallest ceiling in this column among rows that publish a range or a menu at all. A five to six second bumper is one run with room to spare. A thirty second window is four runs, and a sixty second non-skippable is eight, which is the second highest join count in the register.
That count is what the condition compounds. Eight pieces at 1080p is eight pieces priced above the cheapest rung, and the arithmetic that started as a duration question has become a cost question without changing a single figure.
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.
- Veo 3.1 and Veo 3.1 Fast8 seconds, 6 seconds, 4 seconds, with 8 seconds only if 1080p or 4k or using reference images
- Resolutions720p, 1080p (8s length only), 4k (8s length only)tied to the length
5Sources
Read from Google's Veo documentation, 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: Grok Imagine, Hedra.