Vidu prices three resolutions and no length
The API price page publishes 540p, 720p and 1080p as priced steps and states no duration. Its length column is empty, as it is on exactly one other page here. As of 2026-09-12.
| What a plan needs | What the page gives | Status in this register |
|---|---|---|
| A length for one generation | Nothing | Not stated |
| A resolution to budget against | 540p, 720p and 1080p | Recorded, each a priced step |
| A shape for the placement | Nothing | Not stated |
Inclusion rule. What this register reads on each axis, set against what the priced page prints. Gaps are left as gaps rather than filled from a demonstration or a reseller page. Order. The axis the plan needs most first.
1540p already meets the vertical minimum
The bottom of this ladder meets the vertical pixel minimum the one surface that publishes minimums states: vertical ads are accepted from 540x960 upward. So the cheapest step on this row is already acceptable to that placement.
That is a genuine finding about cost, and it is also as far as the page allows anyone to get. A rate per generation with no length attached does not convert into a rate per second, and a campaign is budgeted in seconds.
2Two silent rows, two different silences
The other entry with nothing in the length column publishes 4K at the top of its ladder. This one publishes 540p at the bottom of its. They sit far apart in the resolution column, and both are priced pages that decline to print a duration.
Read together they say something about the genre rather than about either vendor. A rate card exists to answer what a request costs, and on both of these pages the request is priced by quality and not by time, so time never needed a column.
3What the empty cell costs a schedule
The count of calls a slot needs is the one number these sheets compute, and it is division: the format length over the longest single generation. With the denominator missing, every row in the formats table for this entry reads not stated, which is accurate and useless in equal measure.
The register keeps the row anyway. Dropping it would report the register as smaller than it is and would hide the thing worth knowing, which is that a buyer cannot plan a schedule from this page without asking the vendor a question.
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.
- Resolutions540p, 720p and 1080ppriced per step
5Sources
Read from the Vidu API price page, checked 2026-09-12. The column itself is described on duration, and the rule that keeps surfaces and generators apart is on method. Next along this column: Wan 3.0, TikTok.