Safe export settings for vertical video ads mean one thing: a file that plays full-screen, in sharp focus, with working audio and captions, on every placement you plan to run it in. Get the export wrong and a good ad looks soft, gets letterboxed, loses its captions at the edges, or gets auto-compressed into mush by the platform. This guide gives you the exact numbers to start from, the safe zones to protect, and a short checklist to run before you ever hit upload.
What "safe" actually means for an export
"Safe" isn't about avoiding a platform ban. It's about avoiding three quiet failure modes that cost you performance without any warning: the platform re-compressing your file so hard that text blurs, the aspect ratio getting cropped or letterboxed because the source wasn't true vertical, and on-screen elements landing where a profile picture, caption bar or call-to-action button will sit on top of them.
None of these show up when you watch the file on your own screen. They only show up once the ad is live inside the app, next to someone else's UI. That's why safe export settings for vertical video ads are a production step, not an afterthought — you're exporting for a frame that isn't fully in your control.
The safe export recipe (core settings)
If you only remember one block from this article, make it this table. These are starting-point settings to test against your own footage and each platform's current spec page — treat them as the safe default, not an absolute law.
| Setting | Safe default | Why |
|---|---|---|
| Resolution | 1080×1920 pixels | Matches the native vertical frame most feeds use; avoids upscaling artifacts |
| Aspect ratio | 9:16 | The standard full-screen vertical format across TikTok, Reels and Shorts |
| Frame rate | 30 fps, constant (not variable) | Variable frame rate can cause audio drift or stutter after a platform re-encodes the file |
| Video codec | H.264 (MP4 container) | Broadly compatible and re-encodes cleanly on upload |
| Audio codec | AAC, stereo | Standard, low-risk pairing with H.264 in an MP4 |
| Bitrate | High bitrate as a starting point to test, then compare file quality after upload | Low bitrate shows compression first on skin tones, gradients and small text |
| Color profile | Standard (Rec. 709) rather than a log or HDR profile unless the platform explicitly supports it | Avoids washed-out or oversaturated color after re-encoding |
If you're exporting for Meta ads specifically, it's worth cross-checking this against our Video Ad Export Settings for Social Platforms guide, which breaks down the small differences between feed, Stories and Reels placements.
Safe zones: where text, logos and captions should never sit
Every vertical placement reserves space at the top and bottom of the screen for profile names, captions, like/share buttons, or a "swipe up" prompt. If your call to action or offer text lands in that zone, it gets covered the moment the ad goes live — and you won't notice until someone checks it on an actual phone, inside the actual app.
- Keep critical text (hook, offer, CTA) inside the middle roughly 70-75% of the vertical frame.
- Treat the bottom 10-15% of the frame as reserved for platform UI — captions, buttons, usernames.
- Treat the top 8-10% of the frame the same way — status bars and profile elements often sit there.
- Center your logo rather than placing it in a corner; corners are the first thing platform overlays cover.
- Design captions assuming the sound is off — if that's new to your process, Visual Storytelling for Silent Video Ads is a good companion read.
A fast way to test this: export your file, then watch it inside the actual app on a phone rather than only reviewing it in your editor's preview window. The editor rarely shows you the UI overlays that will sit on top of it.
Codec, bitrate and frame rate: the rules of thumb that actually matter
Most export problems trace back to three decisions, so get these right first and the rest is minor polish.
Pick a fixed frame rate and stick to it through the whole pipeline
If your footage was shot at 24 fps and your timeline is set to 30 fps, you can get judder or dropped frames once the platform re-encodes it. Set your project frame rate to match your source footage where possible, and export at a constant frame rate — not variable — so audio and captions stay locked to the picture.
Don't re-export an already-compressed file
Every encode loses some quality. If you export an MP4, then open that same MP4 to trim ten seconds and export again, you're compounding compression loss on top of whatever the platform does on upload. Keep your original edit (project file or a high-bitrate master) and make all adjustments from that master, exporting fresh each time.
Test one high-bitrate master per platform rather than one file for everything
A single export tuned as a safe, high-quality master usually looks fine everywhere, but if you have the time, export one version, upload it as a draft to each platform, and compare how the platform's own re-encode treats fine text and gradients. This matters more for ads with dense on-screen copy — see Font Size Guidelines for Muted Video Ads if your creative leans on a lot of text.
Platform quirks worth checking before export
The core 1080×1920, 30fps, H.264/AAC recipe works almost everywhere, but a few differences are worth a quick check against each platform's current spec page before you finalize an export:
- TikTok and Shorts feeds are built around true full-screen 9:16 — anything shot or cropped from a 16:9 source will show visible letterboxing or pillarboxing.
- Meta placements (Feed, Stories, Reels) can display slightly different crops of the same vertical file, so keep your hook and CTA text centered rather than edge-anchored.
- Stories-style placements often auto-advance on a timer, which changes how much runtime you have to make the point — our Video Ad Length for Stories Ads guide covers runtime choices by goal if you're deciding how long to cut the export.
- File size caps vary by platform and change over time — check the current limit on the ad platform itself rather than assuming your last export size still applies.
If you want the fuller spec breakdown — resolution tables, minimum/maximum duration, aspect ratio tolerances — the Vertical Video Ad Specs for Mobile guide goes deeper than export settings alone.
Common export mistakes that quietly hurt performance
These show up constantly in ad accounts and almost never get flagged by the platform — the ad just underperforms and nobody traces it back to the export.
- Exporting at 1080×1350 or another non-vertical ratio and letting the platform crop it automatically, cutting off the hook or the CTA.
- Leaving the frame rate on "variable" or "same as source" without checking what the source actually was.
- Using a low or auto bitrate setting meant for quick previews, not final delivery.
- Burning in captions right at the very bottom edge of the frame, where they get covered by platform UI.
- Forgetting to check mute playback — if your message depends entirely on the voiceover, it can fail completely with the sound off. The Caption Styles for Sound-Off Video Ads guide is useful here.
A pre-export checklist you can run in under a minute
- Confirm resolution is 1080×1920 and aspect ratio is a true 9:16 — not cropped from 16:9 or 1:1.
- Confirm frame rate is constant (not variable) and matches your source footage where possible.
- Confirm codec is H.264 video with AAC audio, in an MP4 container.
- Check that text, logo and CTA sit inside the middle 70-75% of the frame vertically.
- Watch the final export on an actual phone, inside the actual app if possible, before scheduling it live.
- Keep the original master file so you can re-export cleanly if a platform spec changes.
How FrameNotion fits into this
FrameNotion exports every ad as a 1080×1920, 30 fps MP4 by default — the same safe baseline described above — so you're not guessing at resolution or frame rate for every new creative. You paste a product link or upload a poster, FrameNotion AI writes and renders a full 30-second vertical ad with voiceover, music and word-by-word captions, and checks its own rendered frames before handing you the file. Because the ad is made to work on mute as well as with sound, and because every ad also comes out as 4:5, 1:1 and 16:9, you get a consistent, safe export across formats without re-cutting anything by hand. FrameNotion doesn't publish directly to ad platforms or report on performance — you still upload and run the ad yourself — but the export itself is already built to the settings this guide recommends. You can see finished examples on the examples page or check what's included on pricing.
Frequently asked questions
What export settings are safest if I'm running the same ad on TikTok, Reels and Shorts?+
Start with 1080×1920, 30 fps constant frame rate, H.264 video with AAC audio in an MP4 container. This single recipe works cleanly across all three without separate exports, as long as your source footage is true vertical rather than a cropped 16:9 or 1:1 clip.
Does a higher bitrate always mean a safer export?+
Not necessarily. A high bitrate protects detail in text, gradients and skin tones before the platform re-encodes the file, but an unnecessarily large file can also slow upload or hit a platform's size cap. Treat a high bitrate as a safe starting point to test, then compare how it looks after the platform's own compression.
Why does my exported video look sharp in my editor but blurry once it's live?+
The platform re-encodes every upload on its own servers, and a low or auto bitrate export gives that process very little detail to work with, so the compression becomes visible. Exporting at a higher, fixed bitrate from a clean master usually fixes this.
Should I use variable frame rate to keep file size small?+
It's safer not to. Variable frame rate can cause audio drift or playback stutter once a platform re-encodes the file. A constant frame rate at 30 fps (or matching your source footage) is the more reliable choice for ad delivery.
Do I need different exports for feed placements versus Stories-style placements?+
Usually one well-made 9:16 master works for both, since the core resolution and frame rate are the same. The main thing to check is that your text and CTA sit inside a safe central zone, since Stories-style UI elements can sit slightly differently than feed UI.