CampaignReel

Ad placement specs against what generators output

Wan 3.0 returns a URL that expires in a day

The reference states that a video URL valid for twenty-four hours is returned. That is the shortest published window on these sheets, and it is the only statement this page makes about the finished file. As of 2026-09-22.

A day, and then the URL is goneThe reference says a video URL valid for twenty-four hours comes back. Any campaign asset has to be copied into storage the buyer controls inside that window.Is the file fetched inside the dayIt isA durable copyDelivery checks and version history then live on thebuyer's own storage.It is notGenerate againCheap on this row, since no tier condition attaches tothe length.The shortest published collection window on these sheets
Fig. 1 A returned URL with an expiry is a statement that the vendor is not the archive.
What each page puts in writingFilled where the page states something in that column, hollow where it does not address it.What each page puts in writingFor how longWhat has to happen inside the windowWhat has to happeninside the windowA video URLA video URL — For how long: 24 hoursA video URL — What has to happen inside the window: The file is fetched and stored somewhere durableA file sizeA file size — For how long: Not statedA file size — What has to happen inside the window: Nothing; the figure does not exist on the pageA container or codecA container or codec — For how long: Not statedA container or codec — What has to happen inside the window: Delivery format is measured rather than read
Fig. 2 Filled where the page states something in that column, hollow where it does not address it.
What the reference says the job hands back. Recorded 2026-09-22.
What comes backFor how longWhat has to happen inside the window
A video URL24 hoursThe file is fetched and stored somewhere durable
A file sizeNot statedNothing; the figure does not exist on the page
A container or codecNot statedDelivery format is measured rather than read

Inclusion rule. Statements this API reference makes about the returned result. Input constraints for conditioning media are a different subject and are not carried on this sheet. Order. What the page states first.

1A day is short enough to design around

Twenty-four hours means collection is part of the job rather than a housekeeping task. A queue that generates overnight and is reviewed the next afternoon is inside the window; one that generates on Friday and is reviewed on Monday is not.

On this row the re-generation that follows a missed window is comparatively cheap, because the page attaches no tier condition to its length. It is still a piece of work repeated, and the cause will not be visible in any other column.

2The clock and the combined duration rule are the two operational facts here

The same page states that input plus output must not exceed thirty seconds, which governs extension jobs. Read together, the two statements describe a workflow: extend inside an allowance, then fetch inside a day.

Neither appears in the length column or the resolution column, and both decide whether a pipeline works. They are the reason the file column exists on these sheets at all, given how few rows publish a size.

3What a URL says about where the file lives

A returned URL with an expiry is a statement that the vendor is not the archive. Any campaign asset has to be copied into storage the buyer controls, and that copy is where delivery checks and version history then live.

Thirteen rows in this register say nothing on this question. The two that do are the only ones where a plan can be built on published behaviour rather than on an assumption that the file will still be there tomorrow.

4Where this cell sits in the column

File, generator by generatorWhat each generator says about files, Wan 3.0 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, Wan 3.0 marked. Input ceilings and output ceilings are both recorded here. Recorded 2026-09-22.
Every generator in the register on the file column, with Wan 3.0 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 Wan3.0 API reference, 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: TikTok, Runway.