Adding Device Frames to Store Screenshots Without Breaking the Rules: Apple vs Google Play vs Chinese Android Stores

In product page thumbnails, an interface wrapped in a phone frame often looks more like the real thing than a "bare screen". The problem: once the frame doesn't match the device tier of the upload slot, or hits a channel that explicitly bans device imagery, review sends it back for "inaccurate metadata" or "non-compliant assets". A common case in forums is an iPhone frame uploaded to an iPad slot, with the reply citing Guideline 2.3.3.

This article covers only "whether to add a frame, where, and which kind"; it doesn't repeat size tables. For iPhone 6.9-inch pixels, see the 1320×2868 tutorial; for pixel sizes across Chinese app stores, see China app store screenshot sizes.

First, separate store slot images from off-store promo images

Store slot images are the ones uploaded per device type in App Store Connect, Play Console, and the Huawei / Xiaomi / OPPO / vivo consoles. Review and the store UI interpret them as "the app's interface on a certain kind of device".

Off-store promo images are website heroes, social posts, press materials and landing pages. Viewers don't check the frame against Connect's "iPad 13-inch slot"; aesthetics and brand come first.

The same framed PNG can be perfect for your website yet wrong for a particular store slot. Before you design, ask: which slot in which console will this file end up in? If it's off-store, go ahead with thick frames, desk scenes and multiple devices side by side; if it's a store slot, read that slot's device constraints first.

This site's device frame preview is good for quickly producing off-store mockups, or for checking for yourself "is it still sharp inside a real device frame?". The main flow for portrait store images is still laying out at target pixels in the screenshot editor at /preview; a frame is optional, not something to add by default.

For overseas developers: in mainland China, Android apps are distributed mainly through phone makers' own app stores (Huawei, Xiaomi, OPPO, vivo and others), each with its own asset rules.

Apple: decoration is allowed, but not "the wrong device"

App Review Guideline 2.3.3 requires screenshots to show the app in use, and allows text and image overlays (for example, to demonstrate touch input). It doesn't say "no phone frames at all". What really trips people up is a frame implying a device that doesn't match the size tier being uploaded.

A typical rejection says: an iPhone device frame appears in iPad screenshots. The reviewer sees "you claim this is the tablet experience, but the image shows a phone body". Conversely, using an outdated thick-notch frame in the slot for current Dynamic Island models also tends to look unrealistic.

What to do:

1. Whatever size slot you've opened in Connect (e.g. 6.9-inch iPhone, 13-inch iPad), use only the matching form factor for the frame: phones in phone slots, tablets in tablet slots.
2. The interface must come from real UI (simulator or device screenshots); don't pass off a launch screen or a pure title card as "in use".
3. Overlaid copy is fine, but don't let the frame + big headline squeeze the actual interface until it's unreadable. Apple also requires metadata to suit a 4+ audience, so gory or inappropriate imagery can't appear in screenshots even if the app has a higher rating.
4. The spec page states screenshots can't contain alpha / transparency; when exporting with a frame, check whether the surroundings are cut out and fill a solid background if needed. See Apple's Screenshot specifications.

If you're short on time and unsure whether a frame will cause trouble, use a "no frame + brand-color background + short headline" layout for store slots and keep frames for your website. For a roundup of rejection reasons, see common reasons App Store screenshots get rejected.

Google Play: phone slots are relatively flexible; Wear OS and the Feature Graphic are stricter

Phone / tablet screenshots: Google stresses showing the real in-app experience and advises against compositions like "a hand pressing on the device" that are unrelated to the core experience (unless the interaction itself happens off the device). For phone slots, "must be frameless" isn't stated as an absolute the way it is for Wear; but device imagery is listed as something to avoid in the recommendations for both the Feature Graphic and screenshots, since device designs date quickly and may alienate some users.

Wear OS is explicit: screenshots should show only the app's interface on the watch, without embedding it in a device frame, and without extra backgrounds or decorative text. The watch face category likewise requires showing only the watch face itself. Framed images you made for phone slots can't go straight into Wear slots.

Feature Graphic (1024×500): Google advises avoiding device imagery. A whole phone on the banner eats into the safe area and conflicts with the featuring guidance. For how to make one, see the Feature Graphic guide.

Phone screenshots must still be JPEG or 24-bit PNG without transparency. If a framed export has transparent edges, you'll hit the same problem as transparency rejections.

Chinese Android stores: brand of the device often matters more than how it looks

Xiaomi's developer documentation has clear rules for screenshots, splash screens and onboarding pages: if a phone's exterior appears, it must be a Xiaomi phone; iPhones and other brands' designs are prohibited, and the status bar shouldn't show third-party icons unrelated to the app. Using Apple frames for Xiaomi store assets is a high-probability rejection.

Review notes for OPPO, vivo and other channels commonly include: no duplicate, blurry or stretched screenshots, no other brands' marks, and in some cases a single orientation. Go by the console prompts for exact pixels and counts; you can check China app store screenshot sizes first.

A safe strategy:

• By default, don't add competitor or iPhone frames to Chinese store images; if you want a frame, use a device design the channel accepts, or go frameless.
• Clear notifications and unrelated icons from the status bar, with normal battery and signal.
• Keep your "iPhone-framed set" for the App Store or your website; don't take the shortcut of uploading it to Xiaomi / vivo too.

Recommended workflow: one interface, two export lines

1. Capture portrait interface PNGs on a simulator or device at close to the target store's resolution (e.g. 1080×1920 commonly for Play, 1320×2868 for the App Store 6.9-inch).
2. Store slots: open /preview, pick the matching preset, fill a solid background and add short copy; if you need a frame, confirm its device type matches the upload slot and check for transparent edges.
3. Off-store: drag the same interface into device frame preview, pick a showcase device, and export for your website or social media. Name files separately, e.g. store_play_1.png and web_mockup_1.png, so you don't upload the wrong one.
4. Before publishing to multiple stores, scan the checklist: do Apple slot devices match, are Play Wear images frameless, does Xiaomi show any non-Xiaomi devices, has a whole-device image slipped into the Feature Graphic?

Frames aren't a conversion cure-all; first-screenshot clarity and the information structure of the first three screenshots usually matter more. For more, see screenshot copywriting and the first screenshot. A frame is just a shell that makes it "look like a real device"; when the shell doesn't match the shelf label, review will stop you first.