SnapFrame STUDIO

Padding, radius, shadow, tilt: the numbers behind a clean mockup

Guide 03 · composition · Updated 16 November 2026

Most mockups that look wrong are not badly designed; they are badly proportioned. The padding is too tight, the shadow is too heavy, or the tilt is large enough to suggest a broken layout rather than motion. The fix is usually not taste but a small set of ratios that scale.

Think in percentages, not pixels

A padding of 60px is generous on a 1080-wide image and cramped on a 3200-wide one. Express the space around the subject as a share of the image's shorter side, and the same composition survives every export size.

ElementRangeSweet spot
Padding (all sides)5% – 14% of the short side8% – 10%
Corner radius1% – 3% of the short side1.8% – 2.4%
Shadow blur4% – 12% of the short side7%
Shadow opacity8% – 25%14%
Shadow offset1% – 4% of the short side2%
Tilt (X and Y)0° – 16°4° – 8°

At 1080px wide, an 8% padding is 86px, a 2% radius is 22px and a 7% shadow blur is 76px. Those are the numbers the studio's sliders map to when you leave everything at its default.

Why 8% padding works

Below about 5% the subject touches the edge and the image reads as a crop rather than a composition. Above about 14% the subject becomes a thumbnail floating in a colour field, and the detail you wanted to show is lost.

Asymmetric padding is also legitimate: a wider bottom margin makes the subject feel grounded, and is the whole idea behind a Polaroid frame. What must not happen is padding that differs by one or two percent between images — the eye notices that immediately and reads it as a mistake.

Corner radius has a ceiling

A radius that is too large makes a dense UI screenshot look like a toy: the corners eat the toolbar. A useful test is to look at the top-left corner of the screenshot itself. If your frame radius is much larger than the radius already used inside the product, the frame starts to look like a different design system.

Shadow: one soft light, not five

A single large, low-opacity shadow reads as depth. Multiple stacked shadows with visible edges read as a drop-shadow filter from 2010. Two settings cover almost everything:

On a very dark background, a black shadow does nothing. Either raise the background's brightness slightly behind the subject, or switch to a light rim (a 1px inner stroke at 8–12% white) to separate the card from the page.

How much tilt

Tilt is a rhythm tool, not a default. Four to eight degrees reads as "someone placed this here". Past twelve degrees the perspective starts to distort the interface itself — vertical edges converge, text becomes unevenly spaced, and a screenshot that was supposed to show a clean product starts to look skewed.

Two rules that keep tilt from looking accidental:

Matching the frame to the context

Where it goesFrameWhy
Documentation, help centremacOS windowSignals "this is an application" without adding a brand colour.
Landing page heroBrowser frame or clean shadowA URL bar answers "where does this live" in one glance.
Slide deckMinimal glassTranslucency sits well on top of a coloured template.
Social postClean shadow or editorialLess chrome leaves more room for a headline at feed size.
Changelog, release notesBrowser frameReads as a shipped artefact rather than a mockup.

Background: contrast decides legibility

The subject and the background need a value difference of roughly 15% to feel separated. White UI on white needs the shadow and the frame to carry it; dark UI on a dark gradient needs a rim light. A mid-saturation gradient behind a mid-tone interface is the combination that most often turns to mush.

Two reliable patterns: a near-neutral background (paper, graphite) with a strong shadow, or a saturated gradient with a dark or light frame and almost no shadow. Mixing both strong colour and strong shadow usually looks busy.

Consistency checklist

Keep reading

Try it on your own screenshot

Free, no sign-up, and the image never leaves your browser.

Open the studio