Device Frames on App Store Screenshots

A device frame on an App Store screenshot is a drawing of a phone or tablet around the real interface. It is allowed. It is not a ranking trick, and it is not a way to avoid the pixel size. The uploaded file still has to match the slot exactly. The UI inside the frame still has to be something a shopper can read.

The pixel tables live in App Store screenshot sizes. The required iPhone 6.9-inch slot is 1260×2736. If the app supports iPad, the 13-inch slot is 2064×2752. A frame has to sit inside those pixels. Capture technique is in how to make App Store screenshots, and the visual system is in screenshot best practices.

The frame does not change the canvas

Designers sometimes export a tall marketing image, drop a phone render on it, and upload the result. If that file is not the required width and height, App Store Connect rejects it. Scaling the whole composition to fit stretches the UI. Cropping it cuts off the caption or the home indicator. Measure the exported file, not the artboard you started from.

The frame is part of the image, not a layer the store adds. Apple’s product page does not wrap your screenshot in hardware for you. If you want the outline, you draw it inside the required rectangle. If you do not want it, a full-bleed capture of the UI is a valid screenshot. Both have to be honest pictures of the app.

Legible means the control still looks like itself

Guideline 2.3.3 says screenshots should show the app in use, not only title art, a login wall, or a splash. A frame that reduces the app to a stamp fails that spirit even when the pixel size is correct. The shopper should recognize the screen. Buttons, labels, and the main image have to survive thumbnail size, which is smaller than the frame already made them.

Thick bezels, a heavy shadow, a caption, and a background color all compete for the same rectangle. Something has to give. Give up the shadow first, then the bezel thickness, then the caption length. Do not give up the UI. If you cannot point at the primary control after shrinking the file, the frame is too hungry.

Worked example: a camera app

A camera app’s product is the viewfinder. The shutter, the lens switch, and the last photo are the things a shopper uses to judge it. Put a full-bleed capture next to a framed one before you commit. In the framed version, the phone outline plus a top caption often shrinks the shutter until it reads as a dot. That file can still be 1260×2736 and still be a bad screenshot.

For this app, a thin frame or no frame is the better default. If you keep a frame, leave the viewfinder large, put the caption in a short band above the phone, and do not add a second device at an angle. One phone, one screen, the shutter obvious. The gallery frame that shows a photo you just took can use the same outline so the set feels consistent. Do not switch from a framed shot to a full-bleed shot at random unless the change is the point.

On a camera app, keep the viewfinder and shutter large. A thin frame is optional. A thick bezel hides the product.

iPhone and iPad do not share a frame

An iPhone outline on an iPad canvas is a tell. The iPad screenshot has to show the iPad layout, including a sidebar or split view if that is how the app works. Scaling a framed iPhone shot up to 2064×2752 leaves a phone floating in a tablet slot. iPad screenshot layout is the layout problem. The sizes post is the pixel problem. Solve both.

Use a frame that matches the device you captured. An old bezel on a current screen looks like a template. You do not need the newest render to be honest, but you should not imply hardware the UI was not designed for. Status bar, corner radius, and safe areas should agree with the screenshot inside.

Dark UI makes a bad frame worse

A black camera UI inside a black bezel on a black background is a hole. Separate the layers with a quiet background that is not pure black, or drop the frame. Dark mode screenshots covers the one-slot rule: you still upload one set per device size and localization. The frame does not create a second slot for a light version.

Do not put price, “#1,” or a star badge on the frame. Those are claims, and guideline 2.3 is about an accurate page. A frame is not a place to sneak in a rank you do not have. It is also not evidence that framed screenshots outrank full-bleed ones. Apple has not said that.

Check the file, then the thumbnail

After export, read the pixel dimensions. Then open the image at a width close to a search result and ask whether you can tell what the app does. For the camera, that means seeing a picture in the viewfinder and a shutter. If you only see a phone-shaped blob, remove the frame and try again. AppGrowthKit is one place to do that comparison on the real capture, with the caption and the outline as separate layers you can turn off.

Keep the same decision across the set. Framing only the first screenshot and leaving the rest full bleed makes the gallery look like two designers. Either the outline is a quiet constant or it is gone. Consistency is for the reader. It is not a rank factor you can bank on.