Fitting Runway output into YouTube ad formats

Runway publishes durations of five to fifteen seconds for Gen-4.5, output shapes as pixel pairs rather than ratios, and ceilings on the files that go in. Billing is per second of output, which is what makes the duration figure worth checking before a shot list is written. As of 2026-09-22.

Inclusion rule. Formats from Google's own help page, matched only against limits the tool vendor publishes. Where either side does not state a value, the row says so rather than estimating. Order. Shortest format first, as on the placements page.

1How much each tool puts in writing

Inclusion rule. Tools with a sheet on this site, counted by how many separate output limits their own pages state. A limit mentioned only in a launch post is not counted. Order. Alphabetical by tool name.

Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.

Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.

Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.

2Shape published as a pixel pair answers two questions at once

Landscape 1280:720, portrait 720:1280, square 960:960 and four more pairs is a list of output dimensions dressed as a list of ratios, and it is more information than a ratio alone. A page saying 16:9 leaves the height open; a page saying 1280:720 has answered the shape question and the size question in the same token.

The cost is that the resolution column on this row has nothing conventional in it. There is no 480p or 1080p ladder to compare against the other entries here, so a sheet that lines up tiers across vendors cannot line this one up, and the row says so rather than translating the pairs into a rung they were not written as.

3Input ceilings are published, which almost nothing else here does

16MB for an image and 32MB for a video by URL, 5MB and 16MB as a data URI, 200MB for an ephemeral upload. Those are the file figures a campaign actually collides with when it feeds a product shot or a reference clip into a generation, and they are absent from nearly every other page in this register.

They belong to the input side, so the file column on the output half of the match stays as empty here as everywhere else. That asymmetry is worth naming: the vendor documents what it will accept from a customer with more precision than it documents what it hands back, while the ad platform documents the reverse.

4Sources

Output limits read from the input parameters page at docs.dev.runwayml.com, checked 2026-09-22. Format requirements are from Google Ads Help, and the matching rule is on method. Next along the register: SceneMixer, Wan 3.0. The whole set of 15 is on published limits, and the sheets for each are indexed at tools.

• Gen-4.5
  Durations are 5-15 seconds on Gen-4.5, for text-to-video and image-to-video alikestated per endpointRunway API, input parameters / recorded 2026-09-22
• Gen-4.5 image-to-video
  Landscape 1280:720, 1584:672 and 1104:832, portrait 720:1280, 832:1104 and 672:1584, square 960:960shape given as a pixel pair rather than a ratioRunway API, input parameters / recorded 2026-09-22
• 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
• How generation is billed
  Charged per second of output, with gen4_turbo at 5 credits per second and gen4.5 at 12Runway API, pricing and costs / recorded 2026-09-22