Wan 3.0 defaults to adaptive before naming six shapes
The reference lists adaptive as the default and then 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. A request that says nothing about shape gets a shape the model picked, which is the opposite of how the other explicit row in this column behaves. As of 2026-09-22.
| Setting | Who decides the shape | Suitability for a booked placement |
|---|---|---|
| adaptive, the default | The model, per request | Unsafe: the output shape is not known in advance |
| A named ratio | The request | Safe: the shape is fixed before generation |
| Omitting the field | Falls back to adaptive | Same risk as choosing it deliberately |
Inclusion rule. Values the aspect ratio parameter accepts on this reference page, with the default it names. The judgement column states the consequence for a placement, not a vendor claim. Order. The default first, because it is what an incomplete request gets.
1An adaptive default is the one shape a placement cannot accept
Every ad surface this register reads accepts specific shapes. A file whose shape was chosen by the model is a file whose acceptance was chosen by the model, and a batch generated without the field set can come back in several shapes across one campaign.
The fix is trivial and has to be deliberate: set the ratio on every request. It is worth a page because the failure is silent. Nothing errors, the pieces look correct on their own, and the problem appears when they are uploaded against a spec.
2Six named values sit behind the default
Once the field is set, this row publishes the same six shapes as the other explicit entry in the column, from twenty-one by nine to nine by sixteen with a square option in between. Nothing is missing; the difference between the two rows is entirely in what happens when nobody chooses.
Read together they show that a default is a specification. Two pages offering identical lists behave differently in production because one refuses to proceed and the other proceeds on its own judgement.
3Shape is unconditional here, unlike on two other rows
No tier or length condition attaches to any of the six values on this page. A vertical thirty second piece at 480P is a request the reference supports on its face, and the same is true at 1080P.
That independence is the property that makes this row the common answer for a long vertical placement. The work it leaves is administrative rather than technical: making sure the field is never left to the default in a pipeline that generates many pieces unattended.
4Where this cell sits in the column
| Generator | Aspect ratio |
|---|---|
| Amazon Nova Reel | Not stated |
| CogVideoX | Not stated |
| Google Veo | 16:9 and 9:16 |
| Grok Imagine | Seven, 16:9 the default |
| Hedra | Seven, including 9:21 and 21:9 |
| HeyGen | 16:9 or 9:16 |
| Kling AI | Not stated |
| LTX-Video | Not stated |
| MiniMax | Six, required for text-to-video |
| Pika | Not stated |
| PixVerse | Eight on version 6 |
| Runway | Seven pixel pairs |
| SceneMixer | 9:16 and 16:9 |
| Vidu | Not stated |
| Wan 3.0 | Six, adaptive by default |
Inclusion rule. Every generator in the register, carrying whatever its own page says about output shape. Six rows say nothing and are marked hollow rather than dropped. Order. Alphabetical by generator name.
- Aspect ratios offeredadaptive, the default, then 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16
- Resolution tiers1080P, 720P and 480P
5Sources
Read from the Wan3.0 API reference, checked 2026-09-22. The column itself is described on aspect ratio, and the rule that keeps surfaces and generators apart is on method. Next along this column: PixVerse, Grok Imagine.