Which entries tie a length to a resolution
Two entries couple the length column to the resolution column. One needs a high tier to reach its longest run; the other blocks its longest run at the top tier. Everywhere else in this register the two columns can be read separately. As of 2026-10-25.
| Item | What is published | Detail |
|---|---|---|
| Longest run needs a high tier | One entry | Eight seconds only at 1080p, 4k or with references |
| Longest run blocked at the top tier | One entry | On two older versions, ten seconds cannot use 1080p |
| Columns readable separately | Thirteen entries | No stated dependence either way |
Inclusion rule. Entries whose own page states a dependence between a length value and a resolution value. A dependence on a model identifier or a version alone is recorded separately. Order. The two coupled entries first.
1The same engineering pressure, two policies
Both conditions are about compute per frame: either the frames or the seconds have to give. One vendor decided the long run belongs to the expensive tiers, the other that the expensive tier cannot afford the long run.
Neither is unreasonable and together they are a hazard. A planner who learns the rule on one row will look for a condition that does not exist on the other, or will assume a tier buys a length when it removes one.
2What the coupling costs at the budget line
On the row that requires a tier, a slot filled in eight second pieces is filled at 1080p or above whether or not the placement asked for it. The duration parameter made the resolution decision, and it shows up as a cost.
On the row that blocks a tier, the effect runs the other way: a 1080p delivery on the older versions is capped at eight seconds, so the piece count rises and each piece is charged at the top rung.
3Reading the columns separately is still right
Thirteen entries state no dependence at all, so a register that folded length and resolution into one verdict would be describing two rows and misdescribing thirteen.
These sheets keep every column on its own and print the condition in the cell it removes a value from. That is the only arrangement where a reader who starts in either column arrives at the same answer.
- 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
- Video duration row1~15 on v6 and c1stated per model version
- Fixed-price tables for the older versions; ten seconds is not supported at 1080p5/8/10 on v5.5 and v5.6, where 1080p cannot use 10
- Resolutions720p, 1080p (8s length only), 4k (8s length only)tied to the length
4From brief to placement
For ad work around “Length tied to a tier”, SceneMixer's pages explain how its ad projects are produced:
A segment is one generation, and its length is the sum of its shots’ seconds.
SceneMixer, How to Change a Segment’s Duration, and Which Tiers Accept 30 Seconds (read 2026-10-13)
Video is 16:9 landscape by default, with 9:16 vertical available; you set it once per project. Segments are typically 4 to 15 seconds, and some model tiers go to 30.
SceneMixer, AI Short Drama Generator — “What length and aspect ratio does it output?” (read 2026-10-13)
5Sources
Format requirements come from Google Ads Help, read 2026-09-12, and tool limits from each vendor page listed on published limits, read 2026-09-22 and 2026-10-25. The rule against mixing the two is on method. Nearby: Who publishes a rate, How long output stays, Floors, not just ceilings.