CampaignReel

Ad placement specs against what generators output

HeyGen publishes three upload ceilings by asset type

The usage limits page states 100MB for a video, 50MB for an image or an audio file and 32MB for an asset upload. The ceilings are separated by what is being uploaded rather than by how, which is the opposite of the register's other file row. As of 2026-09-22.

Ceilings sorted by what is uploadedOne hundred megabytes for a video, fifty for an image or audio, thirty-two for an asset upload. The audio figure is the one that touches the duration column.Video in100MBConditioning footageRarely bindsAudio in50MBWhat drives the lengthA practical length boundAsset in32MBCategory unclearThe tightest figure hereSorted by asset type, not by routeAnd nothing at all about the file that comes back
Fig. 1 The tightest ceiling on the page is attached to the vaguest category, which is where a plan will trip.
Ceiling in the spec, by what is uploadedBars are the ceiling as each page publishes it. Placement rules and tool limits are never mixed on one axis.Ceiling in the spec, by what is uploadedA video100MB100MBAn image or an audio file50MB50MBAn asset upload32MB32MB
Fig. 2 Bars are the ceiling as each page publishes it. Placement rules and tool limits are never mixed on one axis.
The three ceilings, and what each covers. Recorded 2026-09-22.
What is uploadedCeilingWhy the figure matters here
A video100MBConditioning footage or a clip to be extended
An image or an audio file50MBAudio is what drives length on this row
An asset upload32MBThe tightest of the three

Inclusion rule. Upload ceilings this usage limits page states, grouped by asset type. Output file size is not stated on this page and is therefore not recorded. Order. Largest ceiling first.

1The audio ceiling is the one that interacts with the length

This row's duration figure is governed by a supplied audio track, and the same page caps an audio upload at fifty megabytes. So the two cells are connected: the ceiling on the input is a practical ceiling on how long a performance can be, whatever the thirty minute figure says.

Fifty megabytes is a great deal of speech at ordinary bitrates, so the interaction almost never binds in advertising, where nothing runs past a minute. It is worth recording because it is the only place in the register where a file column limits a duration column.

2Ceilings by asset type rather than by route

The register's other file row separates its ceilings by how a file arrives: a URL, a data URI, an ephemeral upload. This one separates them by what the file is. Two reasonable schemes, and a plan that carries the numbers between them without noticing will compare the wrong pair.

It also means the tightest figure here is the one attached to the vaguest category. An asset upload at thirty-two megabytes is the lowest ceiling on the page and the hardest to know in advance whether a given file falls under.

3Nothing on the page about what comes out

Output size is absent, as it is on thirteen other rows. Given output dimensions run to 4,096 pixels a side and a scene can run thirty minutes, the file that comes back can be very large, and the page states no ceiling on it.

For an ad placement that is the figure a delivery check needs. The one surface here with a published file cap states 500 MB, and whether a piece from this row clears it has to be measured on the file rather than read from either page.

4Where this cell sits in the column

File, generator by generatorWhat each generator says about files, HeyGen marked. Input ceilings and output ceilings are both recorded here. Recorded 2026-09-22.File, generator by generatorFileAmazon Nova Reel — File: Not statedAmazon Nova ReelCogVideoX — File: Not statedCogVideoXGoogle Veo — File: Held on the server for 2 daysGoogle VeoGrok Imagine — File: Not statedGrok ImagineHedra — File: Not statedHedraHeyGen — File: Upload ceilings, 32MB to 100MBHeyGenKling AI — File: Not statedKling AILTX-Video — File: Not statedLTX-VideoMiniMax — File: Not statedMiniMaxPika — File: Not statedPikaPixVerse — File: Not statedPixVerseRunway — File: Input ceilings, 5MB to 200MBRunwaySceneMixer — File: Not statedSceneMixerVidu — File: Not statedViduWan 3.0 — File: A URL valid for 24 hoursWan 3.0
Fig. 3 What each generator says about files, HeyGen marked. Input ceilings and output ceilings are both recorded here. Recorded 2026-09-22.
Every generator in the register on the file column, with HeyGen marked. Recorded 2026-09-22.
GeneratorFile
Amazon Nova ReelNot stated
CogVideoXNot stated
Google VeoHeld on the server for 2 days
Grok ImagineNot stated
HedraNot stated
HeyGenUpload ceilings, 32MB to 100MB
Kling AINot stated
LTX-VideoNot stated
MiniMaxNot stated
PikaNot stated
PixVerseNot stated
RunwayInput ceilings, 5MB to 200MB
SceneMixerNot stated
ViduNot stated
Wan 3.0A URL valid for 24 hours

Inclusion rule. Every generator in the register against the file column. Most say nothing about files at all, which is why the column is mostly hollow and worth printing. Order. Alphabetical by generator name.

5Sources

Read from the HeyGen usage limits page, checked 2026-09-22. The column itself is described on file, and the rule that keeps surfaces and generators apart is on method. Next along this column: Google Veo, Wan 3.0.