Which entries cap the files sent to them
Two entries publish file ceilings, and both govern what is supplied rather than what is produced. One sorts its figures by how a file arrives, the other by what the file is, and no entry in this register states an output file size. As of 2026-09-22.
| Item | What is published | Detail |
|---|---|---|
| Sorted by route | 5MB to 200MB | Data URI, URL, or an ephemeral upload |
| Sorted by asset type | 32MB to 100MB | Asset upload, image or audio, video |
| Output file size | Nothing, on any entry | The one figure a delivery check needs |
Inclusion rule. File size statements each page makes, separated into what goes in and what comes out. A storage quota is a different subject and is not recorded. Order. Loosest scheme first, then the empty column.
1An input ceiling is not a delivery guarantee
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. Neither of these two pages can be checked against either figure, because both are about the other direction.
These sheets keep both in the file column and mark which side each belongs to. A register that folded them together would let an input ceiling read as a promise about delivery, which is the error a spec sheet exists to prevent.
2The two schemes cannot be compared
A forty megabyte reference video clears one page by URL and clears the other as a video. A forty megabyte audio file clears one page by URL and fails the other by ten megabytes. Asking which is more permissive has no answer.
So the useful reading is per pipeline. Whatever a job sends, and however it sends it, picks the figure that applies, and the register keeps each scheme in its own words rather than normalising them.
3On 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 here where a file figure limits a duration figure.
At speech bitrates fifty megabytes is far more than any advertisement needs, so it never binds in practice. It is recorded because it exists, and because nothing in the duration cell hints that the two are connected.
- Ceilings on what goes in16MB 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 out
- Upload ceilings100MB for a video, 50MB for an image or an audio file, 32MB for an asset upload
4Making the ad itself
For ad work around “Ceilings on inputs”, SceneMixer's pages explain how its ad projects are produced:
Character sheets are always portrait and scene images always widescreen, whatever ratio the videos use.
SceneMixer, Vertical 9:16 or Landscape 16:9 — “Will choosing 9:16 make my character images vertical?” (read 2026-10-13)
Sixty to a hundred and twenty seconds is the working range for short drama, and that is what the outline paces for. A 90-second episode is typically seven segments of about fourteen seconds stacked together.
SceneMixer, Vertical AI Video Generator — “How long should a vertical episode be?” (read 2026-10-13)
5Sources
Format requirements come from Google Ads Help, read 2026-09-12, and tool limits from each vendor page listed on published limits, read 2026-09-22. The rule against mixing the two is on method. Nearby: Sound that arrives, Wider than widescreen, The square option.