There's a specific failure mode that brand designers dread more than almost anything else in paid advertising: the campaign goes live, and someone at the morning standup pulls up the Facebook feed on their phone and the logo is partially hidden behind the platform's "Sponsored" label. The brand mark that your creative team spent weeks getting right is now sitting underneath UI chrome it was never designed to interact with.
Safe-zone violations are preventable. They're also surprisingly common, especially on teams that haven't formalized the calculation into their pre-export process.
What Safe Zones Are and Why They Exist
A safe zone is a region of your asset where you guarantee that no brand-critical elements will be placed. It's a buffer that accounts for two things: the crop behavior of the destination platform, and the UI overlays that platforms render on top of your creative.
The crop behavior problem is structural. A master asset designed at 1200×628 pixels won't necessarily display at those exact proportions on every placement type, even within a single platform. Facebook's link preview card shows differently in the desktop feed, the mobile feed, and the right-column ad unit. Each of those has slightly different crop ratios and safe areas. A logo positioned at the edge of the frame in the master file may be entirely within the visible area in one placement and clipped in another.
The UI overlay problem is harder to predict and more variable over time. Platforms update their native interface chrome — the "Sponsored" tags, the call-to-action overlays, the profile chip and follow button on Stories format, the bottom scrim on display ads — without necessarily notifying advertisers. A safe-zone specification you established for a platform in early 2024 may not fully account for the UI changes that platform shipped by late 2025.
The Standard Safe Zone Calculation
Most practitioners in brand-production contexts use a combination of percentage-based and fixed-pixel measurements depending on the format. The reasoning: percentage-based zones scale correctly when a master asset is used as the basis for multiple derived formats; fixed-pixel zones are more reliable when you're working with a format at a specific known resolution.
A working starting point for common formats:
For 9:16 vertical stories (1080×1920): Reserve the top 14% (approximately 268px) for platform UI — this accommodates the profile chip, the username overlay, and the timestamp display across Instagram, Facebook, and TikTok Stories variants. Reserve the bottom 20% (approximately 384px) for interactive elements — the "Swipe up" / "See more" prompt, and the reply field on Instagram Stories. Keep logo and any critical text within the middle 66% of the frame's height.
For 16:9 horizontal banners (1200×628 or 1920×1080): A 5% perimeter safe zone handles most feed display crop variations. Logo placement in any corner should maintain at least 40px from the edge at 1200px width — equivalent to 3.3% of the shorter edge. Facebook's desktop link preview can trim a further 8–10px from all edges when rendering the thumbnail, so designs should not rely on any element placed within 50px of any edge.
For 1:1 square formats (1080×1080): The 5% perimeter rule applies, but the corner-to-center diagonal positioning of logos becomes a significant variable. A logo in the lower-left corner of a square asset may be visible in a feed card crop but get clipped in the same image when displayed as a profile tag attachment. Consider this when deciding logo anchor position.
The Platform-Specific Overlay Problem
We're not saying platform crop zones are the only thing that matters here — the overlay problem is often what causes the visible failure in practice. The crop issue is static and testable in advance. Overlay behavior is dynamic.
The most reliable mitigation is to treat the safe-zone specification for each format as a living document that gets reviewed at the start of each campaign cycle, not just at the start of a brand engagement. Assign ownership: a specific person on the brand team is responsible for checking whether the platform UI specs have changed since the last campaign.
Platforms typically publish media specification guidelines in their advertising help centers. These are the primary source of record for safe zone requirements — not third-party cheat sheets, which often lag platform changes by weeks or months. The overlap between a platform's crop specification and its UI overlay territory is where violations live, and the only current source for that overlap is the platform's own documentation.
A Practical Pre-Export Checklist
Before any multi-format export goes to trafficking or media buying, a minimal safe-zone verification step should answer three questions:
First: are all brand-critical elements — logo, product shot, primary headline — within the conservative safe-zone boundary for this format? Not just the generous boundary, but the boundary that accounts for platform UI overlays in the worst-case placement type this asset will appear in.
Second: has the safe-zone specification for this format been verified against current platform documentation within the past 60 days? Platforms update their specs with less notice than most teams expect.
Third: has the asset been previewed at the actual rendered sizes and contexts where it will appear — not just at full resolution in a design tool, but at the compressed dimensions and within a representative mock of the destination placement? A logo that appears safe at 1080px resolution may become illegible or appear to bleed into a busy background at 300px display size.
Building Safe Zones Into the Source Asset
The most durable approach is to encode safe-zone boundaries into the source file itself, as locked guides or components that travel with the master asset. This way, every designer who touches the file — whether it's the original brand designer or a production contractor hired for a campaign cycle — is working within the same boundaries, and the specification is visible at the moment decisions are made rather than applied after the fact as a verification step.
In Figma, this means using layout grids or frame constraints to mark the safe-zone boundaries per format, and setting those layers as locked so they can't be accidentally moved. The safe zone should be visually distinct — a semi-transparent overlay, not just a guide — so it's impossible to misread as optional.
When assets are exported to formats, the safe-zone layer is turned off. But its presence during the design and production process makes violations visible before they become expensive. The crop happens on the platform's server. The safe-zone violation happens in your design file, and that's where it needs to be caught.
