CampaignReel

Ad placement specs against what generators output

HeyGen publishes a pixel range, not a ladder

The usage limits page states that width and height must each be between 128 and 4,096 pixels. No named tiers appear, so the cell holds a permitted region rather than a list of choices, and everything inside it is reachable. As of 2026-09-22.

Free dimensions inside two shapesWidth and height run from 128 to 4,096 pixels, which sounds like any frame at all. The shape list on the same page is two values, and that is the statement a placement check uses.What the page permitsDimensions: 128 to 4,096Any even pixel count, so a crop step can be skippedShapes: 16:9 or 9:16The binding statement, and the one a surface checksSquare: not statedA 1:1 placement cannot be confirmed from this pageWhat actually binds
Fig. 1 Read alone the size cell looks permissive and the shape cell looks strict; both readings need the other.
The bounds, and what they permit that a ladder would not. Recorded 2026-09-22.
PropertyWhat the page statesWhat it allows
WidthBetween 128 and 4,096 pixelsAny value inside, not a named step
HeightBetween 128 and 4,096 pixelsThe same range, stated independently
Aspect ratios16:9 or 9:16Only two shapes, despite the free dimensions

Inclusion rule. Output size statements on this usage limits page. Upload ceilings for input files are a different column and are recorded on the file axis. Order. Width, then height, then the constraint that narrows both.

1Bounds and ladders are not the same kind of fact

A ladder says which sizes exist. Bounds say which sizes are refused. Everything between 128 and 4,096 is permitted here, so a placement asking for an exact pixel size can be served exactly rather than at the nearest rung above it.

That has a real consequence for delivery. Several rejections at upload come from odd pixel counts after a crop, and a row that accepts arbitrary dimensions can be asked for the even numbers a platform expects rather than cropped into them afterwards.

2The shape list narrows what the bounds appear to offer

Two dimensions free between 128 and 4,096 sounds like any shape at all. The same page publishes two aspect ratios, sixteen by nine and nine by sixteen, and that list is the binding statement. The bounds govern size within those shapes rather than shape itself.

Reading one column without the other is how this row gets misread. A square placement is not served by a page that permits 1024 by 1024 pixels and lists no square ratio, and the register keeps both cells filled so the contradiction is visible.

34,096 is the highest number in this column

The upper bound exceeds every named tier in the register, including the two 4k figures, which sit near 3,840 on their long side. Nothing in the advertising formats read here needs it, so the figure is another instance of a ceiling that is accurate and inert.

Its comparative value is in what it says about the product. A page that bounds output between a thumbnail and something larger than 4k is describing a general-purpose renderer, not an advertising tool, and every other figure on the row reads the same way.

4Where this cell sits in the column

Resolution, generator by generatorWhat each generator prints as a resolution, HeyGen 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, HeyGen marked. Units differ by row and are not converted. Recorded 2026-09-22.
Every generator in the register on the resolution column, with HeyGen 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.

5Sources

Read from the HeyGen usage limits page, 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: Kling AI, LTX-Video.