How much whitespace does a screenshot actually need?

There's no universal correct margin — a 6% inset and a 12% inset can both look intentional. What can't both look intentional is a set where the margin changes from frame to frame, because that's not a design choice, it's an accident that happens to be visible in a carousel. The number matters less than the discipline of picking one.

Two ways to get it wrong

Cramped screenshots push the headline to the very edge of the canvas, wedge the phone mockup against the type, and leave no air between elements. It reads as amateur — not because any single choice is wrong, but because nothing had room to breathe, and a viewer's eye associates that with a rushed export rather than a designed asset.

The opposite failure is less obvious and just as common: a headline centered in a sea of background with the phone shrunk down to compensate. That reads as unfinished, like a placeholder waiting for content that never arrived. Generous whitespace only works when something in the frame is confident enough to earn it — a bold headline, a striking color, a phone mockup large enough to matter. Empty space around nothing still reads as empty.

Pick one number and use it everywhere

The fix for both failure modes is the same fix: set a margin as a percentage of the canvas, not a fixed pixel count, and hold it constant across every frame in the set. Something in the 6–10% range from each edge is a reasonable starting point for most templates — tight enough that the content still dominates, loose enough that nothing touches the frame.

Percentage matters more than pixels because your canvas isn't one size. An App Store set spans at least three device classes (6.9" iPhone, 6.5" fallback, 13" iPad), and Google Play adds its own. A 96px margin that looks right on a 2868px-tall canvas looks like a rounding error on a 2732px one and cramped on anything smaller. A percentage scales itself; a fixed pixel value has to be re-tuned by hand for every export size, and the frame someone forgets to re-tune is the one that looks off.

Worked example: an 8% margin on a 1320×2868 iPhone 6.9" canvas is about 106px on each side and 230px top and bottom — enough that a headline can sit comfortably inset without feeling like it's floating. Apply that same 8% to a 2048×2732 iPad canvas and you get roughly 164px sides and 219px top and bottom — different pixel counts, same visual relationship, because the percentage is what a viewer's eye actually reads. Nobody looks at a screenshot and clocks "106 pixels"; they clock "the same amount of breathing room as the frame next to it."

Let the background bleed. Don't let the message bleed.

Margin discipline has one legitimate exception, and it trips people up because it looks like a contradiction: decorative elements — a gradient, a background photo, a color field — are allowed to run to the very edge of the canvas. Full-bleed color reads as intentional, even expensive; it's why full-page magazine ads use it and half-page classifieds don't.

What can't bleed is anything the viewer has to read or parse: the headline, the phone mockup, a badge or price callout. Those stay inside the margin every time. The distinction is simple once it's named — background can touch the edge, message can't — but it's easy to break by accident when a device mockup is scaled up "for impact" until its corner clips the frame. That's not confidence, it's a layout that ran out of room.

The gap that does more work than the margin

Outer margin gets the attention, but the gap between the headline and the phone mockup underneath it is doing more of the actual work. That's the space a viewer's eye crosses first — from the words that make the promise to the interface that proves it — and if that gap is inconsistent, the set feels like it was assembled by five different people even when the margins are perfect.

Treat it the same way: one proportion of the canvas height, applied identically whether the headline is one line or two. The instinct when a headline wraps to two lines is to shrink the gap below it so the phone doesn't get pushed down — resist that. A shrinking gap is exactly the kind of inconsistency a viewer can't name but can feel, scrolling past five frames where the fourth one sits slightly differently than the rest.

Whitespace is proportional to confidence, not screen size

The apps that get away with the most whitespace — a huge headline, a small centered mockup, acres of flat color — are usually the ones with the simplest, most singular pitch. A habit tracker can say "Build the streak" and let that sentence own the frame. A project management tool with six features to communicate in six frames doesn't have that luxury; it needs the mockup larger and the margin tighter just to fit enough evidence on screen.

That's the actual answer to "how much whitespace does a screenshot need": as much as the message can support without help. A single confident headline can carry an almost-empty frame. A feature that needs the UI to do the explaining needs the UI to be big enough to read, which means the margin has to give up the room.

Consistency, without measuring it by hand

This is the kind of discipline that's easy to state and tedious to actually hold across eight frames and three device sizes by eye. ShotCanvas templates compute margins and headline-to-mockup spacing as proportions of the canvas, so every export in a set — every device size, every locale — inherits the same spacing automatically instead of drifting frame to frame.