If you've ever had a video ad fail to upload, get silently compressed into mush, or render with crushed audio inside YouTube Ads Manager, the cause is almost always the file itself. Getting the file format requirements for YouTube Shorts ads right before you export saves you from re-rendering, re-uploading, and guessing why your ad looks worse live than it did in your editor.
What File Format Does YouTube Shorts Ads Actually Require?
YouTube Shorts ads run through the same ad infrastructure as other YouTube video ads, so the file format requirements for YouTube Shorts ads follow the same baseline rules as standard YouTube video uploads, with a vertical framing on top. In practical terms, that means:
- Container: MP4 (preferred) or MOV
- Video codec: H.264 (AVC), sometimes H.265/HEVC is accepted but H.264 is the safer, more universally compatible choice
- Audio codec: AAC
- Aspect ratio: 9:16 vertical for a true full-screen Shorts placement
- Resolution: 1080×1920 is the standard target; higher resolutions will usually be downscaled
- Frame rate: a constant frame rate, typically in the 24–60fps range
None of this is unique to YouTube. It's close to what you'd use for a vertical ad on any short-form platform, which is why most teams export once and reuse the file across placements. For a deeper breakdown of why MP4 with H.264/AAC has become the default across platforms, see our guide to the ideal file format for vertical video ads.
Container, Codec, and Resolution: The Core Specs
Container: stick with MP4
MP4 is the container almost every editing tool, phone camera, and ad platform can read and write without extra conversion. MOV files (common from some editing software and screen recorders) are often accepted too, but they can carry codecs that aren't fully compatible, which forces a server-side re-encode you don't control. If you have a choice at export time, choose MP4.
Codec: H.264 video, AAC audio
H.264 is the workhorse video codec for ad uploads: broad support, predictable file sizes, and consistent playback across devices. H.265/HEVC produces smaller files at similar quality, but support for ad uploads is less consistent, so treat H.264 as the format to test first and HEVC as something to experiment with only if you're comfortable troubleshooting. On the audio side, AAC is the standard companion codec — it keeps dialogue and voiceover clear without bloating the file.
Resolution and aspect ratio
Shorts ads are watched full-screen on a phone held vertically, so a 9:16 aspect ratio at 1080×1920 is the resolution to design for. A horizontal 16:9 video dropped into a Shorts placement usually gets letterboxed with black bars or awkwardly cropped — neither looks intentional, and both waste the screen real estate you're paying for. If you're building one asset to run across Shorts, Reels, and TikTok, vertical 9:16 is the shared denominator worth standardizing on.
| Spec | Recommended | Also accepted | Avoid |
|---|---|---|---|
| Container | MP4 | MOV | AVI, WMV, or other legacy containers |
| Video codec | H.264 | H.265/HEVC (test first) | Uncommon or proprietary codecs |
| Audio codec | AAC | MP3 (container dependent) | Uncompressed PCM for final export |
| Aspect ratio | 9:16 vertical | 4:5 (will be cropped) | 16:9 horizontal for a Shorts-first placement |
| Resolution | 1080×1920 | Higher, will be downscaled | Below 720×1280 |
| Frame rate | 24–60fps constant | Platform-supported variants | Variable frame rate (VFR) |
Frame Rate, Bitrate, and File Size Considerations
Frame rate problems are sneakier than codec problems because they don't always throw an error — they just make your ad look subtly wrong. Variable frame rate (VFR) files, which are common output from screen recordings and some phone camera apps, can cause audio drift, stutter, or playback issues once re-encoded by the platform. Before exporting your final file, convert to a constant frame rate (CFR) in your editing tool. If you're unsure which rate to pick, 30fps is a safe, widely tested starting point for Shorts-style vertical ads.
Bitrate affects visual quality more than most people realize. Too low, and fast motion or text turns blocky; too high, and you risk hitting file size caps for no visual benefit. Export at a bitrate your editing software recommends for 1080×1920 footage, then visually check the result at full screen on an actual phone before uploading — not just on a laptop monitor.
File size limits differ by platform and can change, so don't assume the cap you used for one ad network applies to another. If you're repurposing the same asset across platforms, check our guides on max file size for Instagram Reels ads and max file size for Facebook video ads before you assume a single export will clear every placement.
Audio Format and Caption Files for Shorts Ads
Audio is where a lot of otherwise well-formatted files fall apart. A few practical rules:
- Export audio as AAC inside your MP4, not as an uncompressed WAV track left unconverted
- Keep dialogue, music, and sound effects balanced — a voiceover that gets buried under music reads as a formatting problem even though it's a mix problem
- Normalize loudness so your ad doesn't play noticeably louder or quieter than the content around it
- Design the ad to work with sound off, since autoplay in feeds frequently starts muted
For a full breakdown of codec choices, sample rates, and channel layout for ad audio specifically, see our guide to the recommended audio format for vertical video ads.
Captions deserve their own line item in your file checklist. You have two real options: burn captions directly into the video frame (safest for guaranteeing they appear exactly where and how you designed them) or supply a separate caption file in a format like SRT or VTT. Relying solely on auto-generated platform captions is risky — timing can be off, and wording errors in product names or offers look unprofessional. Our guide on closed caption file formats for video ads covers which file types are supported and how to prepare them correctly.
Common File Format Mistakes That Get Shorts Ads Rejected or Downgraded
Most format-related problems fall into a short list of repeat offenders:
- Uploading a horizontal 16:9 file and expecting the platform to crop it intelligently — it usually doesn't, and you lose your safe zone for text and logos
- Exporting with variable frame rate from a screen recording tool without converting to constant frame rate first
- Leaving audio as PCM/WAV inside the final export instead of compressing to AAC
- Using an exotic or legacy codec because 'it played fine on my computer' — ad platforms re-encode server-side, and unusual codecs increase the odds of a quality hit
- Ignoring on-screen safe zones for text and calls to action because the file format was focused on technical specs only, not layout
That last point matters even when every technical spec is correct. A perfectly formatted MP4 can still fail visually if your logo, captions, or call-to-action button sit where YouTube's own UI elements (progress bar, subscribe button, like/comment icons) will cover them. Pair your format checklist with our safe zone guidelines for YouTube Shorts ads so the file plays correctly and reads correctly.
A Pre-Upload Checklist for YouTube Shorts Ads
Run through this before every upload, not just your first one — specs can shift, and it's easy to export from a saved preset that's slightly out of date:
- Container is MP4 (or MOV if MP4 isn't available)
- Video codec is H.264, audio codec is AAC
- Aspect ratio is 9:16 vertical, resolution is 1080×1920
- Frame rate is constant, not variable
- File size is under the current platform cap for your placement
- Audio is normalized and the ad is understandable on mute
- Captions are burned in or attached as a compatible file, and checked for typos
- Key text and logos sit inside the safe zone, away from platform UI overlays
- The file plays back correctly on an actual phone screen, not just a desktop preview
How FrameNotion Handles File Format for You
If you'd rather not manage codecs, containers, and frame rates manually for every ad, that's one of the problems FrameNotion is built to remove. Paste a product or website link into FrameNotion, and FrameNotion AI writes a 30-second vertical ad from scratch — hook, problem, benefit, proof, offer, call to action — then renders it as an MP4 at 9:16, 1080×1920, 30fps: the exact combination of container, resolution, and frame rate covered in this guide, ready for YouTube Shorts, Reels, or TikTok without you touching export settings.
Every ad includes an AI voiceover, music cut to the beat, sound effects, and word-by-word captions baked into the frame (or music-only, or silent, depending on what you choose), so the audio and caption concerns above are already handled. If a change is needed after rendering, you can request edits to text and colors without rebuilding the ad from scratch. You can see the finished output style in our example ads, and the first one is free to try — no card required.
Frequently asked questions
Does YouTube Shorts ads accept MOV files?+
Yes, MOV is generally accepted, but MP4 is the safer default because it has more consistent codec support across editing tools and ad platforms. If you have both options at export, choose MP4.
Is H.265/HEVC a safe codec choice for Shorts ads?+
H.265 produces smaller files at similar quality, but support for ad uploads is less consistent than H.264. Treat H.264 as your default and only test H.265 if you're prepared to troubleshoot playback issues.
Can I upload a horizontal video and let YouTube crop it for Shorts?+
You can, but the result is unpredictable — important elements like text or a logo may get cropped out or letterboxed with black bars. It's better to design and export in a vertical 9:16 frame from the start.
What happens if my file has a variable frame rate?+
Variable frame rate (VFR) files, common from screen recordings, can cause audio drift or stutter once re-encoded by the platform. Convert to a constant frame rate before your final export.
Do I need a separate caption file, or is burning captions into the video enough?+
Burning captions into the frame guarantees they look exactly as designed. A separate SRT or VTT file is a good backup or alternative, but relying only on auto-generated platform captions risks timing and wording errors.
