Vertical Video Safe Areas: What Gets Covered
Every vertical platform draws its own buttons and captions over your video. Here is how to build one conservative safe-area template that survives all of them.
You export a vertical video at 1080×1920, open the app, and find the last line of your subtitles sitting underneath the account name, the call to action hidden behind a share button, and the logo you placed in the top corner tucked under a search icon. The export was correct. The assumption behind it was not: the full frame is what you deliver, but it is not what the viewer sees unobstructed.
Every vertical platform draws its own interface over the video — engagement buttons down one side, the caption and audio attribution across the bottom, status and navigation across the top. This guide covers which regions are contested, how to build a single template that survives all of them, and how to verify it against the app you are actually publishing to rather than against a number someone published last year.
The Frame Is Not the Canvas
A useful way to think about it: the platform is compositing your video underneath its own layer. You control everything in the frame; you control nothing about what sits on top. And because that overlay is part of the app rather than part of your file, it moves whenever the app is redesigned.
Three regions are contested on effectively every vertical platform:
- The bottom. This is the busiest zone by a wide margin. The account name, the caption text you typed when uploading, the audio track attribution, and often a progress bar all live here. Caption text is the difficult part, because its height depends on how much you wrote and whether the viewer expanded it.
- One vertical edge. The engagement column — like, comment, share, and the audio thumbnail — runs up one side, usually the right in left-to-right locales. It is narrow but tall, and it covers a surprising amount of the mid-frame.
- The top. Status bars, a back arrow, a search control, or a following/for-you switcher. Less contested than the bottom, but not safe.
What is left is a tall block, offset slightly away from the engagement column, centred vertically. That block is your real canvas.
Build One Conservative Template, Not Three Exact Ones
The instinct is to measure each platform precisely and produce a version per destination. In practice that is a maintenance burden that expires quickly, because the measurements are properties of an app release rather than of a standard. A redesign silently invalidates every template you built.
The alternative is to design for the intersection: take the largest contested region you have observed on any platform you publish to, apply it everywhere, and accept the unused frame as the cost of never having to think about it again. One export, safe on all of them.
A workable starting template, expressed in proportions so it survives a change of resolution:
Two details make this template work in practice. First, keep the subject's face inside the safe block for the entire clip, not just at the first frame — a speaker who leans forward or gestures will drift into the engagement column. Second, place subtitles in the lower half of the safe block rather than at its very bottom, because the bottom region is the one that grows when a viewer expands a long caption.
Different Footage, Different Risk
The template is the same for every video, but the amount of trouble it saves you varies enormously with what you are shooting, and it is worth knowing which category you are in before you start.
A single speaker on camera is the forgiving case. The subject occupies the middle of the frame naturally, the background carries no information, and the only real risk is subtitles drifting too low. If this is most of your output, you can treat the template as a light guide rather than a hard constraint.
Screen recordings are the unforgiving case, and they are where most covered content happens. A recording of an application interface has meaningful detail spread evenly across the whole frame, including the corners, so there is no region you can afford to lose. Scaling the whole recording down to fit inside the safe block usually makes the text unreadable on a phone. The workable answer is to stop treating the recording as a single shot: crop into the specific region you are talking about, one region at a time, and let the rest of the frame go. A sequence of legible close crops communicates far more than one complete but tiny screen.
Product and demonstration footage sits in between. The object needs to be inside the safe block, but the risk is subtler — the thing you are demonstrating often happens at the edge of the frame because that is where your hands are. Watch a take back with the template overlaid before you commit to a whole shoot in that setup.
Text-heavy explainers, where the video is largely animated typography, are the case where the template is doing the most work and costs the least. Because you are placing every element deliberately, keeping all of it inside the safe block is simply a layout decision made once.
Verify Against the App, Not Against a Table
Any published pixel value, this article's included, is a snapshot of an interface that is free to change. The only measurement that reflects what your audience will see is one you take from the current app.
Framing Decisions That Follow From the Template
Once the safe block is fixed, several production choices become straightforward rather than debatable.
Shoot or crop so the subject sits slightly away from the engagement edge rather than dead centre. A perfectly centred subject looks balanced in your editor and slightly crowded in the app, because the visible area is not symmetrical.
Keep lower thirds out of the lower third. The name of the convention is a holdover from horizontal video, and in vertical it points straight at the busiest region on the screen. Put speaker identification in the middle band instead, sized larger than you would use horizontally.
Do not put anything you legally need people to read near an edge. Disclosure text, sponsorship labels and pricing belong inside the safe block at a size that survives a phone screen, which is the same argument covered in caption styling that stays legible.
When you are cropping horizontal footage rather than shooting vertically, the safe block also decides how much room you have to track a moving subject — the crop has to keep them inside a narrower box than the frame suggests. That trade-off is the subject of reframing 16:9 footage to 9:16.
Next Steps
Build the template once. Create a 1080×1920 overlay in your editor with the three contested regions filled and the safe block left clear, save it as a preset or a title, and drop it on the top track of every vertical project. Turn it off before export.
Then run the verification upload described above for the one platform you publish to most, and correct the template from what you find. From there, the remaining decisions are about the clip itself rather than the frame: what belongs in the opening seconds, covered in turning long videos into shorts, and how the rest of the workflow fits together in short-form and clip creation.
Frequently Asked Questions
VisionKut Editorial
Written by the VisionKut production team — editors, motion designers, and engineers who build and use the tools daily.
Related Articles
Caption Styling That Stays Legible on Every Background
Caption legibility is not a font choice, it is a separation problem: the text has to survive whatever the footage does behind it. Four techniques, when each is the right one, and how to size type against the canvas rather than your monitor.
Reframing 16:9 Footage to 9:16 Without Losing the Subject
Converting widescreen footage to vertical discards roughly three-quarters of the picture, and which three-quarters is the entire decision. Three methods, and the footage each one ruins.
Turn Long Videos Into Shorts Without Losing Context
Extracting a 60-second clip from a two-hour recording usually results in a disjointed mess. Here is how to isolate a self-contained idea, build a hook, and structure a short that actually makes sense on its own.
