Veo ties two of its three resolutions to a length
The documentation publishes 720p, 1080p and 4k, and annotates the upper two with the length they require. Tiers on this row are bound to the duration parameter, and the annotation runs in both directions depending on which column is read first. As of 2026-09-22.
| Tier | Length available | What the pairing removes |
|---|---|---|
| 720p | 4 or 6 seconds | Eight seconds is out of reach |
| 1080p | 8 seconds only | Four and six second requests at this tier |
| 4k | 8 seconds only | Four and six second requests at this tier |
Inclusion rule. Resolution values this documentation page states for Veo 3.1, with the length condition the same page attaches to each. Reference-image routes to the same lengths are noted in the prose rather than the table. Order. Cheapest tier first, which is also the least constrained on length.
1Both upper tiers carry a length note
Two other entries in this register couple length and resolution, and each does it with a single condition. This one annotates two of its three tiers, so the coupling is the rule rather than an exception at the edge of the ladder.
Read from the resolution side the effect is severe: a 1080p request is an eight second request. A four second insert at 1080p is not on the page, and a sequence that mixes lengths is a sequence that mixes tiers unless reference images are supplied.
24k on an eight second ceiling is a narrow product
This is one of two 4k figures in the register, and the other sits on a priced page with no length beside it at all. Here the top tier exists and is bounded to eight seconds, which makes it a tier for single shots rather than for sequences.
Against the formats that exist, eight seconds of 4k covers a bumper with room and reaches a quarter of the thirty second window. A campaign that wanted the whole window at that tier is four requests, four joins and four times the tier rate.
3What a buyer should read first on this row
The resolution column looks like the choice and is mostly the consequence. The decision is made in the length column, or by whether reference images are part of the production at all, and the tier follows from it.
These sheets keep the columns separate so that the dependence is visible rather than averaged away. A single verdict about this row would have to pick which column leads, and the honest answer is that the page makes the other one follow.
4Where this cell sits in the column
| Generator | Resolution |
|---|---|
| Amazon Nova Reel | 1280x720 |
| CogVideoX | 720 x 480 only |
| Google Veo | 720p / 1080p / 4k |
| Grok Imagine | 480p / 720p / 1080p |
| Hedra | 540p / 720p / 1080p |
| HeyGen | 128 to 4,096 px each side |
| Kling AI | 720p / 1080p / 4K |
| LTX-Video | 1216x704 |
| MiniMax | 480P / 768P / 2K |
| Pika | 480p / 720p / 1080p |
| PixVerse | 360p / 540p / 720p / 1080p |
| Runway | Pixel pairs, not tiers |
| SceneMixer | 480P / 720P / 1080P |
| Vidu | 540p / 720p / 1080p |
| Wan 3.0 | 480P / 720P / 1080P |
Inclusion rule. Every generator in the register, carrying the resolution figure its own page prints, whether that is a ladder, a range or a single pair of numbers. Order. Alphabetical by generator name.
- Resolutions720p, 1080p (8s length only), 4k (8s length only)tied to the length
- 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
5Sources
Read from Google's Veo documentation, checked 2026-09-22. The column itself is described on resolution, and the rule that keeps surfaces and generators apart is on method. Next along this column: Grok Imagine, Hedra.