Where a model name decides the ceiling
Three entries attach a limit to an identifier rather than to a tier. One needs a particular model ID past six seconds, one publishes different duration rules per version, and one splits its resolution ladder between two models on the same page. As of 2026-10-25.
| Item | What is published | Detail |
|---|---|---|
| A model ID past the first beat | One entry | Requests on the other ID are capped at six seconds |
| A duration rule per version | One entry | One to fifteen on the newer pair, fixed values on the older |
| A ladder split between two models | One entry | 768P and 2K on one, 480P and 768P on the other |
Inclusion rule. Entries whose own page attaches a length or resolution limit to a named model or version. A limit attached to a priced tier is recorded separately. Order. As each condition appears in the documentation.
1An identifier in the shot list, not in the plumbing
A model name usually reads as an implementation detail. On these three rows it decides what can be asked for, so it belongs beside the length in a brief rather than inside a configuration file nobody reviews.
The failures are quiet. A request against the wrong identifier comes back short or at a resolution nobody chose, and the error mentions neither versions nor tiers.
2The condition can sit in prose rather than in a table
On one of these entries the model table gives the ceiling and a separate sentence gives the identifier needed to reach it. Read apart, the ceiling looks unconditional.
These sheets keep the two in one row for that reason. A length that exists only on one identifier is a length with a precondition, and the precondition belongs beside the number.
3Two models on one page are not a ranking
On the entry that splits its ladder, the model with the higher duration floor is also the one missing the top resolution. The suffix on its name suggests more of everything and the figures do not support that ordering on either column.
A register carrying one line per vendor would be wrong for half the requests made against that page. It is the clearest argument on these sheets for recording the identifier as part of the cell.
- Which model ID reaches past one shotTo generate videos longer than six seconds, you must use amazon.nova-reel-v1:1 as the model ID
- 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
- Resolutions768P and 2K on MiniMax-H3; 480P and 768P on H3-Max, where 2K is not supportedstated per model
4Making the ad itself
For ad work around “Identifiers and ceilings”, SceneMixer's pages explain how its ad projects are produced:
Paste a scene or a short script and SceneMixer gives you a storyboard — numbered shots with framing and seconds — and then a moving version of each segment, which you can join into a rough cut of the scene.
SceneMixer, Using SceneMixer for Previs and Animatics Before a Live-Action Shoot (read 2026-10-13)
The shot seconds in the storyboard add up to the segment length, so editing them changes it.
SceneMixer, Fixing One Shot Without Redoing Everything — “Can I change the duration of a segment?” (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: Nothing about shape, Cards, not products, Thirty seconds in calls.