CampaignReel

Ad placement specs against what generators output

Ceilings sorted by route against ceilings by asset

One page caps inputs by route: 5MB as a data URI, 16MB by URL, 200MB as an ephemeral upload. The other caps them by asset type: 32MB for an asset, 50MB for an image or audio, 100MB for a video. Both are the only rows in this register with a file figure at all. As of 2026-09-22.

Ceilings on two different axesOne page sorts its ceilings by how a file arrives and the other by what the file is. A figure carried across compares a route to an asset type.Sorted by routeSorted by assetA 40MB reference videoClears, by URLClears, as a videoA 40MB audio fileClears, by URLFails, by ten megabytesOutput file sizeNot statedNot statedTwo reasonable schemes and no common axis
Fig. 1 Asking which page is more permissive has no answer until the pipeline is described.
How each page organises its ceilings. Recorded 2026-09-22.
What the pages stateRunwayHeyGen
Organising principleHow the file arrivesWhat the file is
Tightest figure5MB, as a data URI32MB, for an asset upload
Loosest figure200MB, ephemeral upload100MB, for a video

Inclusion rule. Input ceilings each page states, grouped as each page groups them. Neither page states an output file size, so no such figure is recorded. Order. The principle first, then the extremes of each scheme.

1Two reasonable schemes, not comparable

Asking which row is more permissive is not answerable. A 40MB reference video clears one page by URL and clears the other as a video, and a 40MB audio file clears one page by URL and fails the other by ten megabytes.

So the useful reading is per pipeline rather than per vendor. Whatever a job actually sends, and however it sends it, decides which figure on which page applies, and the register keeps both schemes in their own words.

2On one row the file ceiling touches the length

The asset-type row is the one whose output length follows a supplied audio track, and the same page caps an audio upload at fifty megabytes. That is the only place in this register where a file column limits a duration column.

At ordinary speech bitrates fifty megabytes is far more than any advertisement needs, so the interaction never binds here. It is worth recording because it exists at all, and because nothing in the duration cell hints at it.

3What both pages leave out is the same thing

Neither states an output file size. The one surface in this register with a published file rule caps an upload at 500 MB and sets a bitrate floor of 516 kbps, and neither of these pages can be checked against either figure.

That is the general shape of the file column on these sheets: requirements on the surface side, input ceilings and retention clocks on the generator side, and no overlap. The only way to close it is to measure the delivered file.

4The rest of the column behind these two

File across the registerRunway is marked; HeyGen sits at three ceilings sorted by what is being uploaded in the same column. Recorded 2026-09-22.File across the registerFileAmazon 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. 2 Runway is marked; HeyGen sits at three ceilings sorted by what is being uploaded in the same column. Recorded 2026-09-22.
Every generator in the register on the file column, with Runway 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 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. Both rows publish file ceilings and neither can be compared to the other without deciding which axis the numbers are on. A plan that carries the figures across will compare a route to an asset type and get a wrong answer.

  • Ceilings on what goes in
    16MB for an image and 32MB for a video by URL, 5MB and 16MB as a data URI, 200MB for an ephemeral uploadnot on what comes outRunway API, input parameters / recorded 2026-09-22
  • Upload ceilings
    100MB for a video, 50MB for an image or an audio file, 32MB for an asset uploadHeyGen documentation, usage limits / recorded 2026-09-22

5Sources

Read from the Runway API input reference and the HeyGen usage limits page, both checked 2026-09-22. The column is described on file, and each entry has its own cell page at Runway and HeyGen, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: CogVideoX and LTX-Video, LTX-Video and PixVerse.