CampaignReel

Ad placement specs against what generators output

The same six shapes, opposite defaults

Both pages publish 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. One adds adaptive as the default, letting the model choose. The other states that the field is required and that adaptive is not offered. Identical lists, opposite behaviour when nobody sets the field. As of 2026-09-22.

What an unset field returnsThe lists are identical. One page proceeds on the model's judgement and the other refuses to proceed at all, and that is the whole difference in production.Nobody set the aspect ratioAdaptive is the defaultUsable files, wrong shapesDiscovered at upload, after the generation budget isspent.The field is requiredA rejected requestDiscovered immediately, and fixed with one line.Six identical named values behind both
Fig. 1 A failed request costs a retry; a batch in shapes nobody booked costs the schedule.
What each page puts in writingFilled where the page states something in that column, hollow where it does not address it.What each page puts in writingWan 3.0MiniMaxThe six named valuesThe six named values — Wan 3.0: Identical on both pagesThe six named values — MiniMax: Identical on both pagesDefaultDefault — Wan 3.0: adaptive: the model choosesDefault — MiniMax: None; the field is requiredRisk in an unattended batchRisk in an unattended batch — Wan 3.0: Mixed shapes across one campaignRisk in an unattended batch — MiniMax: A rejected request
Fig. 2 Filled where the page states something in that column, hollow where it does not address it.
What happens when the shape field is left alone. Recorded 2026-09-22.
What the pages stateWan 3.0MiniMax
The six named valuesIdentical on both pagesIdentical on both pages
Defaultadaptive: the model choosesNone; the field is required
Risk in an unattended batchMixed shapes across one campaignA rejected request

Inclusion rule. Shape statements from each page, including the default each names. The risk column states the consequence for a booked placement rather than a vendor claim. Order. The shared list first, then the behaviour that differs.

1A failed request is cheaper than a wrong shape

The required field turns an omission into an error at submission time. The adaptive default turns the same omission into a batch of usable files in shapes nobody booked, discovered at upload.

For advertising the first failure mode is plainly preferable. It costs a retry; the second costs the generation budget and the schedule, because the pieces have to be made again after the problem is understood.

2Nothing about the lists explains the difference

Six values, both including ultrawide and square, both applying to every tier the same page publishes. If the register carried only the list, these two rows would be interchangeable, and in production they are not.

That is why the default sits in the cell rather than in a footnote. A shape column recording only which shapes exist would describe the easier half of the question and leave the half that causes rework unrecorded.

3Both rows carry the fix in one line

Set the ratio on every request. On the adaptive row that overrides the default; on the required row it is the only way to submit at all. The same discipline works on both, which is worth saying because most of this column has no documented default to override.

What differs is what happens when the discipline lapses. One row tells you immediately and the other tells you after the media is booked, and that is the whole content of this comparison.

4The rest of the column behind these two

Aspect ratio across the registerWan 3.0 is marked; MiniMax sits at the same six values, with the field required instead in the same column. Recorded 2026-09-22.Aspect ratio across the registerAspect ratioAmazon Nova Reel — Aspect ratio: Not statedAmazon Nova ReelCogVideoX — Aspect ratio: Not statedCogVideoXGoogle Veo — Aspect ratio: 16:9 and 9:16Google VeoGrok Imagine — Aspect ratio: Seven, 16:9 the defaultGrok ImagineHedra — Aspect ratio: Seven, including 9:21 and 21:9HedraHeyGen — Aspect ratio: 16:9 or 9:16HeyGenKling AI — Aspect ratio: Not statedKling AILTX-Video — Aspect ratio: Not statedLTX-VideoMiniMax — Aspect ratio: Six, required for text-to-videoMiniMaxPika — Aspect ratio: Not statedPikaPixVerse — Aspect ratio: Eight on version 6PixVerseRunway — Aspect ratio: Seven pixel pairsRunwaySceneMixer — Aspect ratio: 9:16 and 16:9SceneMixerVidu — Aspect ratio: Not statedViduWan 3.0 — Aspect ratio: Six, adaptive by defaultWan 3.0
Fig. 3 Wan 3.0 is marked; MiniMax sits at the same six values, with the field required instead in the same column. Recorded 2026-09-22.
Every generator in the register on the aspect ratio column, with Wan 3.0 marked. Recorded 2026-09-22.
GeneratorAspect ratio
Amazon Nova ReelNot stated
CogVideoXNot stated
Google Veo16:9 and 9:16
Grok ImagineSeven, 16:9 the default
HedraSeven, including 9:21 and 21:9
HeyGen16:9 or 9:16
Kling AINot stated
LTX-VideoNot stated
MiniMaxSix, required for text-to-video
PikaNot stated
PixVerseEight on version 6
RunwaySeven pixel pairs
SceneMixer9:16 and 16:9
ViduNot stated
Wan 3.0Six, adaptive by default

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. Two pages offering the same six values behave differently in production because one proceeds on its own judgement and the other stops. That is the clearest demonstration on these sheets that a default is a specification.

5Sources

Read from the Wan3.0 API reference and the MiniMax video task reference, both checked 2026-09-22. The column is described on aspect ratio, and each entry has its own cell page at Wan 3.0 and MiniMax, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Grok Imagine and Pika, LTX-Video and Wan 3.0.