YouTube Shorts safe zones: what the interface covers up

Nothing about a Short is harder to fix after the fact than composition. The colour can be graded, the audio can be replaced, the caption can be rewritten — but if your subject or your subtitles sit underneath the interface, the only fix is re-exporting the video.

And the interface covers more of the frame than almost anyone expects.

What is actually on top of your video

A Short plays at 1080 × 1920 — 9:16, full bleed, no letterboxing. But the player draws its own controls over that frame, and three regions are effectively unusable:

Region	Roughly	What sits there
Top bar	Top ~11%	Back arrow, search, camera
Right rail	Right ~22%, vertically centred	Like, comment, share, sound disc, channel avatar
Bottom block	Bottom ~22%	Channel name, caption text, progress bar, music strip

Convert those to pixels on a 1080 × 1920 export and the numbers get uncomfortable:

• Top bar: about 210 px down from the top
• Bottom block: about 420 px up from the bottom
• Right rail: about 240 px in from the right edge

That leaves a genuinely clear area of roughly 820 × 1,290 px, offset left of centre. You are designing inside about 51% of the pixels you exported.

You can see this rather than imagine it — drop a frame into the Shorts safe zone checker and the covered regions are drawn straight over your own image.

The bottom third is where Shorts go wrong

If you fix one thing, fix this one. Almost every composition mistake in the format is the same mistake: subtitles burned into the bottom of the frame, where the channel name, the caption and the progress bar all live.

It happens because every editing tool defaults there. Lower thirds are correct for landscape video, where nothing else occupies the bottom of the frame. In vertical they are wrong, and the default has never caught up.

The result is a video where the most important text — the words carrying the point — is partly hidden behind the platform’s own text. Viewers do not report this. They just leave.

Move subtitles up. Slightly below the vertical centre is the standard compromise: high enough to clear the bottom block, low enough to still read as subtitles, and left enough to clear the right rail.

The right rail is the second trap

The action buttons run down the right side, vertically centred. They cover about a fifth of the width, and they are opaque enough that anything behind them is gone.

This matters for two things people routinely put there:

• A subject framed right of centre. Standard landscape composition often puts a face or product on the right third. In vertical that is directly under the like button.
• Long subtitle lines. A line of text spanning the full width does not get hidden by the right rail — it gets overlapped, which is worse, because the last two words of every line become unreadable and the viewer keeps trying.

Keep text lines to roughly 75% of the frame width, starting from the left margin. That single constraint solves the right rail entirely.

Design left of centre, on purpose

Because the right rail eats a fifth of the width and the left edge is clear, the true optical centre of a Short is not the centre of the file. It sits a little left.

For faces, products and any single focal subject, composing slightly left of the file’s centre reads as centred to the viewer. Composing at the exact centre reads as slightly crowded against the buttons — most people cannot say why, but they feel it.

Crops are how good footage ends up in bad places

Most safe-zone failures do not come from bad composition. They come from reformatting.

Take a 1920 × 1080 landscape video, crop it to 9:16, and everything that was comfortably inside the landscape frame is now scaled up and pushed outward. A lower-third caption that sat neatly at the bottom of a landscape frame ends up in the bottom block. A subject on the right third ends up under the sound disc.

If you are repurposing landscape footage:

1. Reframe rather than crop. Choose what the vertical frame is of, then position it — do not accept a centre crop and hope.
2. Rebuild the text. Never carry burned-in landscape captions into a vertical export. Re-add them at vertical-safe positions, or better, use a caption file. Our subtitle converter will turn an existing SRT into the format your editor wants, and captions added as a file are positioned by the player rather than baked into the wrong place.
3. Check the export, not the timeline. Editors preview at a size and aspect that hides the problem. Export a still and check it against the real overlay.

If you need to resize or pad a still to exact Short dimensions before checking it, the image resizer does it in the browser without uploading anything.

What the safe zones do not tell you

Two honest caveats, because a lot of safe-zone content is presented with false precision.

These regions move. The overlay changes with the app version, the device, whether the video uses a sound, whether there is a pinned comment, and — most of all — how long your caption is. A three-line caption pushes the bottom block substantially higher than a one-line caption. Nobody’s fixed pixel figure is correct in every case, including ours.

Shorter captions buy you frame. This is the lever almost nobody uses. Your caption text is what determines how tall the bottom block grows. Writing a one-line caption instead of a three-line one gives you back real estate at the bottom of the frame for free.

A short checklist before you export

• Export at 1080 × 1920, 9:16, nothing else.
• Nothing important in the top 11% or the bottom 22%.
• Text lines end by about 75% of the width.
• Subject composed slightly left of the file centre.
• Subtitles above the midpoint, not in the lower third.
• Caption written short, so the bottom block stays small.
• One frame checked against a real overlay before you publish, not after.

None of this makes a bad Short good. It just stops a good one being unreadable, which is a much more common problem than it should be.