Two pages couple length to a tier in opposite directions
One page states eight seconds only at 1080p or 4k. The other states that on versions 5.5 and 5.6 a ten second request cannot use 1080p. Both couple length to resolution and the conditions point opposite ways, which is the trap in this pair. As of 2026-10-25.
| What the pages state | Google Veo | PixVerse |
|---|---|---|
| At the cheapest tier | The longest run is out of reach | The longest run is available |
| At the top tier | The longest run is required | The longest run is blocked |
| Where the condition lives | On two of three tiers | On two of four model versions |
Inclusion rule. Length conditions each page attaches to a resolution. Conditions that apply to reference images rather than tiers are described in the prose rather than the table. Order. The cheapest tier first, then the top one.
1Same engineering pressure, opposite resolutions
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.
Read as policy neither is odd. Read as a spec they are a hazard, which is why the register keeps each condition in the same cell as the value it removes rather than in a note further down the page.
2The conditions attach to different things
On one row the condition is a tier: 1080p and 4k are eight seconds only, and reference images offer a second route to the same length. On the other it is a version: the newest pair take one to fifteen seconds unconditionally and the older pair do not.
So one plan has to name a tier and the other has to name a version, and on both rows the identifier is a specification field rather than a housekeeping detail.
3Where a plan should actually look
If the placement is vertical short-form at the cheapest tier, the second row gives fifteen seconds and the first gives six. If the placement wants 1080p, the first row gives eight seconds and the second gives eight on its older versions.
Neither answer is available from the duration column alone. These sheets separate the columns so the dependency is visible, and this pair is the clearest case for why a single verdict per vendor would be useless.
4The rest of the column behind these two
| 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 this register carries, on the one column this pair disagrees about. Rows that state nothing keep their place and are marked hollow. Order. Alphabetical by generator name.
Why these two. Both rows make length and resolution depend on each other, and they disagree about which direction. That is the one pairing in this register where carrying a rule from one row to the other produces a confidently wrong plan.
- 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
- 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
5Sources
Read from Google's Veo documentation and the PixVerse pricing page, checked 2026-09-22 and 2026-10-25 respectively. The column is described on duration, and each entry has its own cell page at Google Veo and PixVerse, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Kling AI and Vidu, Pika and SceneMixer.