CampaignReel

Ad placement specs against what generators output

Runway publishes pixel pairs instead of tiers

The input reference publishes seven pixel pairs rather than a resolution ladder: 1280:720, 1584:672, 1104:832 landscape, 720:1280, 832:1104, 672:1584 portrait and 960:960 square. One field carries both the size and the shape. As of 2026-09-22.

One field answering two columnsA pixel pair states the size and implies the shape at once. That is more precise than a tier name and harder to line up beside fourteen rows that publish names.Pick a pairSeven values acrosslandscape, portrait andsquareSize and shapeat onceCheck the floorThe pixels can be comparedto a placement minimumdirectlyA confirmed fitCompare across rowsOnly by arithmetic thisregister declines to publish
Fig. 1 The largest long side on the page is 1584 pixels, which a tier name would have hidden entirely.
The pairs, grouped by the shape they imply. Recorded 2026-09-22.
GroupPairs the page listsWhat the numbers also say
Landscape1280:720, 1584:672, 1104:832The long side never exceeds 1584
Portrait720:1280, 832:1104, 672:1584The same three shapes, transposed
Square960:960A single pair, with no wider or narrower option

Inclusion rule. Values the image-to-video ratio field accepts according to this reference. The pairs are recorded as printed and are not converted into named tiers or named ratios. Order. As the reference groups them: landscape, portrait, then square.

1A pair collapses two columns into one

Every other row in this register answers size in one place and shape in another, and a buyer reads two cells. Here one field settles both, which is tidier to request against and harder to compare, because neither the resolution column nor the shape column has a value to line up beside the rest.

This register keeps the pairs as printed in both columns rather than deriving tiers and ratios from them. The arithmetic is easy; the point is that the vendor did not publish the result of it, and a derived figure would carry the same check date as a read one.

2The transposition is exact, which says something useful

Each landscape pair has a portrait twin with the numbers swapped. That symmetry means a campaign can be planned in shapes rather than in sizes, and the vertical version of a widescreen placement is the same request with two values exchanged.

It also bounds the output more tightly than a ladder would suggest. The largest long side on the page is 1584 pixels, which is under 1080p on its long axis, so this row sits lower in the column than a tier name would have implied.

3What the field is documented for matters

The pairs are published for the image-to-video path, where an input frame already has a shape. That is the path most serial advertising uses, because a conditioning frame is how a cast holds its appearance between separately generated pieces.

So the field is not an afterthought on this row: it is the interface a campaign actually meets. The register records it in the shape column and the size column alike, and marks in both that the figure is a pixel pair rather than a name.

4Where this cell sits in the column

Resolution, generator by generatorWhat each generator prints as a resolution, Runway marked. Units differ by row and are not converted. Recorded 2026-09-22.Resolution, generator by generatorResolutionAmazon Nova Reel — Resolution: 1280x720Amazon Nova ReelCogVideoX — Resolution: 720 x 480 onlyCogVideoXGoogle Veo — Resolution: 720p / 1080p / 4kGoogle VeoGrok Imagine — Resolution: 480p / 720p / 1080pGrok ImagineHedra — Resolution: 540p / 720p / 1080pHedraHeyGen — Resolution: 128 to 4,096 px each sideHeyGenKling AI — Resolution: 720p / 1080p / 4KKling AILTX-Video — Resolution: 1216x704LTX-VideoMiniMax — Resolution: 480P / 768P / 2KMiniMaxPika — Resolution: 480p / 720p / 1080pPikaPixVerse — Resolution: 360p / 540p / 720p / 1080pPixVerseRunway — Resolution: Pixel pairs, not tiersRunwaySceneMixer — Resolution: 480P / 720P / 1080PSceneMixerVidu — Resolution: 540p / 720p / 1080pViduWan 3.0 — Resolution: 480P / 720P / 1080PWan 3.0
Fig. 2 What each generator prints as a resolution, Runway marked. Units differ by row and are not converted. Recorded 2026-09-22.
Every generator in the register on the resolution column, with Runway marked. Recorded 2026-09-22.
GeneratorResolution
Amazon Nova Reel1280x720
CogVideoX720 x 480 only
Google Veo720p / 1080p / 4k
Grok Imagine480p / 720p / 1080p
Hedra540p / 720p / 1080p
HeyGen128 to 4,096 px each side
Kling AI720p / 1080p / 4K
LTX-Video1216x704
MiniMax480P / 768P / 2K
Pika480p / 720p / 1080p
PixVerse360p / 540p / 720p / 1080p
RunwayPixel pairs, not tiers
SceneMixer480P / 720P / 1080P
Vidu540p / 720p / 1080p
Wan 3.0480P / 720P / 1080P

Inclusion rule. Every generator in the register, carrying the resolution figure its own page prints, whether that is a ladder, a range or a single pair of numbers. Order. Alphabetical by generator name.

  • Gen-4.5 image-to-video
    Landscape 1280:720, 1584:672 and 1104:832, portrait 720:1280, 832:1104 and 672:1584, square 960:960shape given as a pixel pair rather than a ratioRunway API, input parameters / recorded 2026-09-22
  • Gen-4.5
    Durations are 5-15 seconds on Gen-4.5, for text-to-video and image-to-video alikestated per endpointRunway API, input parameters / recorded 2026-09-22

5Sources

Read from the Runway API input reference, checked 2026-09-22. The column itself is described on resolution, and the rule that keeps surfaces and generators apart is on method. Next along this column: Vidu, Wan 3.0.