Google Ads Shorts: horizontal video serves with blurred edges
Google's Shorts ad specs say horizontal assets serve with blurred edges and only the first 60 seconds play in feed. Render your own 9:16 blur fit instead.

Google says horizontal video assets are supported for YouTube Shorts ads but serve with blurred edges, and it recommends vertical 9:16. If you want the framing under your control, render the vertical version yourself. Timeline 1.0 has a blur fit that places the whole 16:9 shot in a 1080x1920 frame.
What does Google's page say? (read 2026-10-09)
The page gives no file size, resolution or safe-zone numbers, so none are stated here.
| Item | What the page says |
|---|---|
| Ratio | 9:16 recommended; horizontal supported, served with blurred edges |
| Length | Up to 3 minutes; only the first 60 seconds play in feed |
| Action-oriented ads | 10 to 30 seconds |
| Video Reach campaigns | 6 to 60 seconds |
| Other campaign types | 10 to 60 seconds |
| Hosting | Video uploaded to YouTube, public or unlisted |
Why render the blur yourself?
Google's automatic fill is applied when it serves the ad. Your own render fixes what the edges look like and lets you check the result before it goes live. Use Timeline 1.0 with output 1080x1920 and fit blur: the clip is contained in the frame and the area around it is filled with a blurred version. The fit modes comparison shows the other options, cover, contain and stretch.
How do you stay inside the length windows?
- For an action-oriented ad, cut to 30 seconds or less with video_trim ($0.02 per job) before the Timeline step.
- For Video Reach, trim to a duration between 6 and 60 seconds.
- The first 60 seconds are what play in feed, so put the offer inside them even if the file is longer.
- Timeline renders cost $0.10 per output minute, rounded up, so a 30-second ad is $0.10.
Which should you ship?
Ship the vertical blur-fit render when the subject sits in the middle of a 16:9 frame. Ship the original horizontal file only if you are happy with Google's blurred edges. Probe the render with video_inspect to confirm 1080x1920 before you upload it to YouTube and attach it to the campaign.
Before launch, open the rendered file next to Google's own preview and compare how much of the subject is visible and how the edges look. If the two differ, decide which to run and keep the other as a test. The page does not give numeric safe zones, so judge by eye, and keep key text away from the frame edges.
Sources
Related posts
More in Media tools
- H3 Max Lip Sync on an 11.2 s line: $0.75, $1.20 or $2.40
An 11.2-second voice line bills 12 seconds on Sume's MiniMax H3 Max Lip Sync: $0.75 at 480p, $1.20 at 768p, $2.40 at 1080p. See the audio window and limits.
- H3 Max lip sync on a 6.2-second line: billed as 7 s, $0.44 to $1.40
MiniMax H3 Max Lip Sync on Sume bills ceil of audio seconds: a 6.2 s line is 7 s, or $0.4375 at 480p, $0.70 at 768p and $1.40 at 1080p.
- Image upscale factor 4 on a 1024 square: about 16.8 MP for $0.20
Sume image upscale allows factor 1 to 4 at $0.20 per image, with about 16 megapixels reserved. A 1024 square times 4 is 4096 square, 16.78 MP. Check the math.
- Video inspect API: 24 stills max, so 2 fps covers only 12 seconds
Sume video inspect returns at most 24 stills per call and caps fps at 2. How to size frames.fps for a 60-second clip, plus fast versus precise seek.
Written by Sume