CampaignReel

Ad placement specs against what generators output

Two days against one before the file is gone

One page states that generated videos are stored on the server for two days and then removed. The other states that a video URL valid for twenty-four hours is returned. They are the two retention statements in this register, and the other thirteen rows say nothing. As of 2026-09-22.

The shorter window has the cheaper recoveryA repeat request on the two day row is subject to the tier and length conditions that page attaches. On the one day row nothing is coupled, so a repeat is a plain request.Two days, then removedA URL valid for a dayWindowLongerShorterCost of missing itA conditioned re-requestA plain re-requestRows in the register with anyclockTwo of fifteenTwo of fifteenSilence on the other thirteen is a gap, not permanence
Fig. 1 Reading the retention cell alone gets this backwards, which is why the conditions sit beside it.
The two clocks, and what each one implies. Recorded 2026-09-22.
What the pages stateGoogle VeoWan 3.0
WindowTwo daysTwenty-four hours
Form of the statementStored, then removedA URL with an expiry
Cost of missing itRe-generation under tier conditionsRe-generation, unconditioned

Inclusion rule. Retention statements each page makes about its own output. Input ceilings are a separate subject and are not recorded here. Order. The longer window first.

1A clock makes collection a scheduled step

Both windows are generous for one piece and thin for a batch. A queue that runs overnight and is reviewed the next afternoon fits inside either; one that runs on a Friday and is reviewed on a Monday fits inside neither.

The failure is quiet. Nothing errors at generation time, the pieces were produced correctly, and the problem appears when somebody opens a link. That is exactly the kind of specification that belongs in a register rather than in a footnote.

2The re-generation costs are not the same

On the two day row a repeat request is subject to the same tier and length conditions the page attaches: eight seconds needs 1080p, 4k or reference images. On the one day row nothing is coupled, so a repeat is a plain request at any tier.

So the shorter window belongs to the cheaper recovery and the longer window to the more conditioned one. Reading the retention cell alone would get that backwards.

3Silence here is not permanence

Thirteen rows say nothing about retention. That is a gap, not a guarantee, and these sheets mark it hollow rather than assuming either answer, because a pipeline built on the wrong assumption fails late and expensively.

The practical rule is the same on every row: copy the output into storage the buyer controls as soon as the job finishes. On these two rows the deadline is published; on the rest it has to be guessed at.

4The rest of the column behind these two

File across the registerGoogle Veo is marked; Wan 3.0 sits at a returned URL valid for twenty-four hours 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 Google Veo is marked; Wan 3.0 sits at a returned URL valid for twenty-four hours in the same column. Recorded 2026-09-22.
Every generator in the register on the file column, with Google Veo 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. Two days against one is not a ranking worth making. What matters is that these are the only two rows where collection can be planned from a published figure instead of from an assumption that the file will still be there.

5Sources

Read from Google's Veo documentation and the Wan3.0 API reference, both checked 2026-09-22. The column is described on file, and each entry has its own cell page at Google Veo and Wan 3.0, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Nova Reel and CogVideoX, HeyGen and Runway on size.