Do App Store screenshots need a device frame?
Published
Short answer
No. Apple’s screenshot specification asks for pixel dimensions, file format and a missing alpha channel — it says nothing about a bezel or mockup1 (source 1). The App Review Guidelines require only that a screenshot show the app in use2 (source 2). Whether to frame the screen is a design choice with a real trade-off: a frame eats vertical space that could otherwise show more of the product. No reliable public data settles which performs better, so treat any conversion-rate claim you read about frames with suspicion.
Key points
- Apple’s screenshot specification regulates pixel dimensions, file format and the alpha channel — never the presence or absence of a frame1 (source 1).
- Guideline 2.3.3 asks a screenshot to “show the app in use, and not merely the title art”2 (source 2) — a rule about the content inside the frame, not what surrounds it. A frame is compatible with that rule either way.
- Guideline 2.3.10 bars apps and their metadata from carrying “names, icons, or imagery of other mobile platforms”2 (source 2). That is the rule a mismatched frame actually risks — an Android-shaped outline or foreign system chrome in an App Store screenshot.
- Apple’s own guidelines for using its product imagery require an actual photograph of genuine Apple hardware, not an artist’s rendering, when a third party depicts an Apple product3 (source 3). Whether that reaches a generic illustrated phone outline drawn around your own screenshot is not addressed anywhere Apple publishes — treat it as an open question, not a settled one.
- No public, sourced data compares install or conversion rates between framed and full-bleed screenshots. A specific percentage quoted for this claim should be treated as unverified until it names its source.
Does Apple require a device frame?
No. Nothing in Apple’s screenshot specification asks for a frame, a bezel or a device mockup. The specification is entirely about the file itself — which pixel dimensions are accepted (see the accepted size table), which formats are allowed, and the rule against an alpha channel1 (source 1). It never addresses what happens visually inside that rectangle.
The App Review Guidelines add a content rule, not a framing rule. Apple asks that a screenshot “show the app in use, and not merely the title art”2 (source 2) — a requirement about what fills the frame, not whether a bezel sits around it. A frame is permitted, never required, and what App Review actually checks is the product view underneath it.
What the rules do restrict
Guideline 2.3.3 permits text and image overlays — labelling a gesture, calling out a feature — as long as the screenshot underneath is the app itself, not a title card or a login screen2 (source 2). A frame is a kind of overlay in that sense: it sits around the capture rather than replacing it, which is why framing on its own does not violate the rule.
Guideline 2.3.10 is the rule that actually bears on frame choice. Apps and their metadata may not carry “names, icons, or imagery of other mobile platforms”2 (source 2). A screenshot wrapped in an Android-shaped outline, or one showing foreign system chrome such as a different status bar or navigation gesture, is the kind of image this guideline targets — not because a frame is banned, but because the wrong frame reads as another platform.
None of this reaches the file-level mistakes that cause a rejection on their own — wrong pixel dimensions, an alpha channel left in a PNG export, more than ten images in one localisation. Those sit in App Store Connect’s mechanical checks rather than App Review’s content rules; see why an upload gets rejected for the causes that have nothing to do with framing.
The trade-off: frame versus full bleed
A frame costs space. Draw a phone outline around a screenshot and the actual UI — the part a shopper is trying to evaluate — has to shrink to fit inside it, leaving a visible margin of bezel and background around the edges. A full-bleed screenshot, cropped to the exact accepted pixel size, shows more of the product in the same rectangle.
That is the entire trade, and it runs in both directions. A frame adds context — this is a phone, held a certain way — and can make a set of screenshots read as one coherent story rather than several disconnected crops. A full-bleed screen reads faster and gives text and UI more room to stay legible at App Store thumbnail size.
Consistency matters more than which one you pick
The bigger risk is not choosing wrong — it is choosing inconsistently. A set where the first three screenshots sit inside a phone frame and the last two are full-bleed crops reads as unfinished, as if two people worked on it without checking each other’s output. Shoppers scan a screenshot set in a few seconds; a break in that rhythm is the kind of thing they notice without being able to say why.
Pick one approach for the whole set — frame every screen or frame none of them — before designing the first one. The same discipline applies across localisations and across the required 6.9-inch size and any secondary size you export; a frame that looks right at one size but crops oddly at another undermines the consistency it was meant to add.
If you use a frame, make it a real one
A frame that misrepresents the platform is the one real failure mode. Wrapping an iOS screenshot in a frame shaped like an Android device, or one with generic rounded corners that match neither, works against what Guideline 2.3.10 is aimed at even when no automated check catches it2 (source 2) — it makes the listing look like it was not built for this platform.
The safer bar is a frame that resembles a plausible current iPhone — the right corner radius, a notch or Dynamic Island where the real device has one, no home button on a design that has not shipped one in years. It does not need to be a photograph of a specific model; App Review’s own screenshot rule is about the content of the screen, not the accuracy of an illustrated bezel around it.
Shotluma renders perspective device mockups and keeps the frame as an editable layer rather than baking it into a flattened image, so switching between framed and full-bleed — or changing the frame’s angle — stays a reversible decision late in the process. It is free, MIT-licensed and browser-based, and exports at 1290 × 2796 and 1242 × 2688. It does not currently produce iPad sizes or Google Play–compatible dimensions.
Perspective frames versus flat frames
A flat frame — the phone drawn straight-on, screen parallel to the viewer — keeps the UI undistorted and easiest to read at thumbnail size, since every pixel of the captured screen maps directly to the same rectangle in the frame. It reads as literal: this is exactly what the app looks like.
A perspective or angled frame — the phone tilted, sometimes set against a shadow or a hand — reads more like a product photograph and can make a static screenshot feel less flat. The cost is legibility: text and small UI elements near the far edge of the tilt compress, and at thumbnail size in search results that compression can make a dense screen harder to parse at a glance.
Neither is prohibited, and Apple does not distinguish between them anywhere in its rules. The choice sits closer to a brand decision than a compliance one: a flat frame suits an app that sells on information density, a perspective frame suits one that sells on feel.
Frequently asked questions
Does the frame count toward the required pixel dimensions?
Yes. Whatever you export — framed or not — has to match one of the accepted sizes exactly1 (source 1). If a frame graphic pushes your canvas past 1290 × 2796, you resize the whole composition, not just the screen inside it; see the accepted size table for every accepted value.
Can I use a frame with the Apple logo visible on it?
Be cautious. Apple’s own guidelines for using its product imagery require an actual photograph of genuine Apple hardware for that kind of use, not an illustrated rendering3 (source 3), and a drawn frame with a rendered Apple logo is neither. The simpler choice is a generic phone outline with no logo at all — nothing in App Review requires one, and leaving it off avoids the question entirely.
Do App Store preview videos need a frame the same way screenshots do?
No, and the underlying rule is different in kind. Previews must be video screen captures of the app itself2 (source 2), so a frame around that capture is a compositing choice, not a requirement — the same reasoning as screenshots, applied to video.
If I frame my iPhone screenshots, should my iPad screenshots match?
Yes, for the same consistency reason as within one device’s set — a shopper moving between your iPhone and iPad listings should not see one framed and the other full-bleed. Match the frame style, not necessarily the exact device model, since an iPad frame and an iPhone frame are shaped differently by definition.
Will a full-bleed screenshot look empty next to competitors who use frames?
That depends on how much of the screen is genuinely showing UI, not on the presence of a frame. A full-bleed crop of a screen that is mostly whitespace can look sparse regardless of framing; the fix in that case is the layout of the screenshot itself. There is no evidence that adding a frame compensates for a screen that does not have much to show.
Sources
- 1Screenshot specifications — App Store Connect Help — Apple Developer, Screenshot format, dimensions and alpha-channel requirements. Read .
- 2App Review Guidelines — Apple Developer, Guideline 2.3.3 (Screenshots) and 2.3.10 (Platform imagery). Read .
- 3Guidelines for Using Apple Trademarks and Copyrights — Apple, Depictions of Apple Products, under Compatibility. Read .