The short answer
Make one iPhone set at 1320 × 2868(portrait, 6.9"). Apple scales it down for every smaller iPhone. If your app supports iPad, add a second set at 2064 × 2752. For Google Play, re-export the same layouts at 1080 × 1920 and add a 1024 × 500 feature graphic.
That is four exports total. Everything below is the detail behind those numbers — and the caveat that matters: Apple retires required sizes every year or two, so glance at the upload screen in App Store Connect before you spend an evening in Figma.
iOS screenshot dimensions
| Display | Example device | Portrait (px) | Landscape (px) | Do you need it? |
|---|---|---|---|---|
| iPhone 6.9" | iPhone 16 Pro Max | 1320 × 2868 | 2868 × 1320 | Yes — this is the set to make |
| iPhone 6.7" | iPhone 15 Pro Max, 14 Pro Max | 1290 × 2796 | 2796 × 1290 | Accepted alternative |
| iPhone 6.5" | iPhone 11 Pro Max, XS Max | 1242 × 2688 | 2688 × 1242 | Accepted alternative |
| iPhone 6.3" | iPhone 16 Pro | 1206 × 2622 | 2622 × 1206 | Optional |
| iPad 13" | iPad Pro (M4) | 2064 × 2752 | 2752 × 2064 | Yes, if you support iPad |
| iPad 12.9" | iPad Pro (older) | 2048 × 2732 | 2732 × 2048 | Accepted alternative |
Rules the uploader enforces silently:
- PNG or JPEG, RGB, flattened. No alpha channel. A transparent PNG is the single most common upload failure.
- No rounded corners, no status-bar edits. Ship the full rectangle; the store rounds it in the UI.
- Exact pixel dimensions. 1320 × 2868 means exactly that — a 1319-wide export is rejected, not resized.
- Up to 10 per size per localization, plus up to 3 app preview videos.
Google Play graphic assets
Play is friendlier: it specifies a range instead of exact sizes, so one well-chosen export covers everything.
| Asset | Spec | Count | Note |
|---|---|---|---|
| Phone screenshots | 320–3840 px per side, 16:9 to 9:16 | 2–8 | 1080 × 1920 is the safe default |
| Feature graphic | 1024 × 500, PNG or JPEG | 1 (required) | Shown at the top of your listing |
| App icon | 512 × 512, 32-bit PNG | 1 (required) | No transparency, no rounded corners |
| Tablet screenshots | Same range as phone | 0–8 | Needed to be surfaced well on tablets |
| Promo video | YouTube URL | Optional | Autoplays in place of the feature graphic |
The feature graphic catches people out because it is the one asset with no equivalent on iOS. It is a wide 1024 × 500 banner, it is required before you can publish, and text near the edges gets cropped on small screens — keep the wordmark centered.
The five-minute export workflow
- Capture on the biggest device. Run your app in an iPhone 16 Pro Max simulator and screenshot the five screens that sell it — usually the main view, the moment of value, one detail screen, one settings/personalization screen, and the paywall.
- Caption each one. One short benefit line per image, top third of the frame. The search results page shows the first two screenshots at thumbnail size, so anything below the halfway mark is decoration.
- Export iOS at 1320 × 2868. Flatten to RGB, no transparency.
- Resize the frame to 1080 × 1920 and re-export for Play. Same layouts, different canvas. Then make the 1024 × 500 feature graphic from the same background and wordmark.
- Check the preview, not the file. Both consoles show you how the set looks in search. That view — small, cropped, scrolling — is the only one that decides installs.
Sizes are the easy part
Getting the pixel count right takes an afternoon. Having screens worth screenshotting is the actual work — and it is where most first apps stall, because the app is still half-built when the founder starts designing the listing.
If you are at that stage, build the app first and let the screenshots fall out of it. ShipNative generates a real React Native app from a description, runs it on your phone, and exports the full Expo project — so the screens you capture are the screens you ship. When you get to the upload form, the EAS submission checklist covers the rest of what review looks at, and the Google Play publishing guide walks the Android side end to end.