Safe zones in Stories and Reels: the visual guide that stops your text getting covered
You design a story on your laptop, with the file open full-screen on a large monitor, and it looks perfect: text centred, logo at the bottom, everything breathing well. You upload it, open it on your own phone to check — and the system clock covers the first line of text. Or the reply button covers the logo. That's not a mistake you made: it's that you designed without accounting for the safe zone.
What a safe zone actually is
The file you upload to a Story or Reel is shown in full — 1080×1920 pixels of image, uncropped. What happens is that on top of that image, the app itself draws its interface: the clock and battery icon at the top, the username and any stickers you've added, and at the bottom the "send message" bar or reaction buttons. That interface is not part of your file, but it takes up real space on screen — and it varies slightly between Instagram, TikTok and Facebook, and between iPhone and Android.
The strips that are almost always at risk
As a practical and conservative guideline: leave a free margin with no important content in the top 14% of the image (where the status bar lives, and on Instagram the publisher's name) and in the bottom 20% (where interaction buttons and the reply field fall). This isn't an officially identical figure across all three apps, but it works as a safety buffer in any of them — better to have too much margin than to discover covered text after publishing.
Where you can safely approach the edge
The central third of a Story or Reel is by far the most reliable space: no app places fixed interface elements there. If your main message — the headline, the face, the product — lives in that central strip, you're already safe from most overlaps, even if you add secondary elements closer to the edge.
Why the desktop editor deceives you
The reason this error is so common is that almost no one designs or reviews the story in the same context where it will be seen. On a computer there's no system clock over the image, so everything appears correct. The only check that truly works is previewing the file inside the phone, with the app open, before publishing — or using a visual safe zone guide while adjusting the frame, instead of trusting that "it will look fine".
SMALLADAPT draws this guide directly on the preview when you choose Story or Cover — try it here and enable it in the adjustment step to see exactly which zone is at risk before downloading.
