Quick answer
The Apple App Store requires 6.9-inch iPhone screenshots (1320×2868 or 2868×1320) and accepts up to 10 per device, while Google Play wants 1080×1920 phone screenshots, a 2:1 max ratio, and 2 to 8 per listing. Apple is stricter about exact device sizes; Google is looser but caps the aspect ratio. The smart move is to design one screenshot set on a shared canvas and export both sizes from it.
What's the difference between App Store and Play Store screenshots?
If you're shipping the same app on both iOS and Android, you've probably hit this wall: the two stores want different things, and what passes on one fails on the other. Here's the side-by-side.
| | Apple App Store | Google Play | |---|---|---| | Phone size | 1320×2868 or 1290×2796 (6.9"/6.7" iPhone) | 1080×1920 (recommended) | | Min / max count | 1–10 per device size | 2–8 per listing | | Aspect ratio rule | Must match a supported device | No wider than 2:1 | | Orientation | Portrait or landscape | Portrait or landscape | | Format | PNG or JPEG | PNG or JPEG | | Required? | At least 1 for the largest iPhone | At least 2 phone shots |
The headline difference: Apple is strict about exact device dimensions, Google is loose but caps the aspect ratio. Apple wants screenshots that match specific iPhone display sizes to the pixel. Google mostly cares that your shortest side is at least 320px, your longest is at most 3840px, and you're not wider than 2:1.
The other big difference is count. Apple gives you up to 10 screenshot slots per device size; Google gives you 8. And Apple's are organized per device class, which means if you only upload screenshots for the largest iPhone, Apple scales them down for smaller phones automatically — but you lose pixel-perfect control on those smaller screens.
For the authoritative specs, check Apple's screenshot specifications and Google's Play Console asset guidelines directly, since both update their numbers periodically.
| | Apple App Store | Google Play | |---|---|---| | Phone size | 1320×2868 or 1290×2796 (6.9"/6.7" iPhone) | 1080×1920 (recommended) | | Min / max count | 1–10 per device size | 2–8 per listing | | Aspect ratio rule | Must match a supported device | No wider than 2:1 | | Orientation | Portrait or landscape | Portrait or landscape | | Format | PNG or JPEG | PNG or JPEG | | Required? | At least 1 for the largest iPhone | At least 2 phone shots |
The headline difference: Apple is strict about exact device dimensions, Google is loose but caps the aspect ratio. Apple wants screenshots that match specific iPhone display sizes to the pixel. Google mostly cares that your shortest side is at least 320px, your longest is at most 3840px, and you're not wider than 2:1.
The other big difference is count. Apple gives you up to 10 screenshot slots per device size; Google gives you 8. And Apple's are organized per device class, which means if you only upload screenshots for the largest iPhone, Apple scales them down for smaller phones automatically — but you lose pixel-perfect control on those smaller screens.
For the authoritative specs, check Apple's screenshot specifications and Google's Play Console asset guidelines directly, since both update their numbers periodically.
How many screenshots does each store want?
Apple gives you up to 10 screenshots per device size. Google gives you up to 8 per form factor with a minimum of 2.
In practice, you don't need to design 10 versus 8 separate ideas. You design one ordered set of your strongest 6–8 frames, and then you decide how many slots to fill on each store. I usually fill 8 on both — Apple's extra two slots get supporting screens that don't make the Android cut.
The ordering logic is identical across both stores: lead with your strongest benefit, because both Apple and Google show only the first couple of screenshots in search results before someone taps into the full listing. So your two best frames carry the search-results glance on both platforms. The frames behind them get swiped through only by people who already tapped in.
One nuance: Apple shows the first three screenshots in some search-results layouts (especially on larger screens and with the newer App Store presentation), while Google typically shows about two. It's not worth obsessing over, but if you're optimizing hard, make sure your first three frames are all strong rather than just your first two.
In practice, you don't need to design 10 versus 8 separate ideas. You design one ordered set of your strongest 6–8 frames, and then you decide how many slots to fill on each store. I usually fill 8 on both — Apple's extra two slots get supporting screens that don't make the Android cut.
The ordering logic is identical across both stores: lead with your strongest benefit, because both Apple and Google show only the first couple of screenshots in search results before someone taps into the full listing. So your two best frames carry the search-results glance on both platforms. The frames behind them get swiped through only by people who already tapped in.
One nuance: Apple shows the first three screenshots in some search-results layouts (especially on larger screens and with the newer App Store presentation), while Google typically shows about two. It's not worth obsessing over, but if you're optimizing hard, make sure your first three frames are all strong rather than just your first two.
Which screenshot specs are stricter — and why it matters?
Apple is stricter, and the reason matters for how you build your screenshots.
Apple validates that each screenshot matches a real iPhone display size. If you upload a 1080×1920 Android-sized image to the App Store, it gets rejected — the dimensions don't correspond to any iPhone. You have to hit the actual device resolutions, like 1320×2868 for the 6.9-inch iPhone or 1290×2796 for the 6.7-inch. That precision is annoying but predictable: there's exactly one right answer per device.
Google is more forgiving on exact size but enforces the 2:1 aspect ratio ceiling hard. A tall 1080×2400 screenshot (that's 20:9, common on modern Androids) is fine. But if you tried something wider than 2:1 — say a panoramic 2400×1000 — Google rejects it. Most people never hit this because phone screenshots are naturally portrait and tall.
Why this matters for your workflow: because the two stores disagree on exact dimensions, the trap is designing your screenshots once at one store's size and then stretching them to fit the other. Stretching is what produces those slightly-off, squished-looking screenshots you've definitely seen on cross-platform apps. A 16:9 design jammed into a 19.5:9 frame looks wrong, and people feel it even if they can't name it.
The fix isn't to design twice. It's to design on a frame-based canvas where the device frame defines the export size, so the same layout renders correctly to each platform's dimensions instead of being stretched between them. That's exactly the problem the PlayMockUp frame library is built around — pick the iPhone frame for the App Store export, pick the Pixel or Galaxy frame for Play, same screenshot, two correct sizes.
Apple validates that each screenshot matches a real iPhone display size. If you upload a 1080×1920 Android-sized image to the App Store, it gets rejected — the dimensions don't correspond to any iPhone. You have to hit the actual device resolutions, like 1320×2868 for the 6.9-inch iPhone or 1290×2796 for the 6.7-inch. That precision is annoying but predictable: there's exactly one right answer per device.
Google is more forgiving on exact size but enforces the 2:1 aspect ratio ceiling hard. A tall 1080×2400 screenshot (that's 20:9, common on modern Androids) is fine. But if you tried something wider than 2:1 — say a panoramic 2400×1000 — Google rejects it. Most people never hit this because phone screenshots are naturally portrait and tall.
Why this matters for your workflow: because the two stores disagree on exact dimensions, the trap is designing your screenshots once at one store's size and then stretching them to fit the other. Stretching is what produces those slightly-off, squished-looking screenshots you've definitely seen on cross-platform apps. A 16:9 design jammed into a 19.5:9 frame looks wrong, and people feel it even if they can't name it.
The fix isn't to design twice. It's to design on a frame-based canvas where the device frame defines the export size, so the same layout renders correctly to each platform's dimensions instead of being stretched between them. That's exactly the problem the PlayMockUp frame library is built around — pick the iPhone frame for the App Store export, pick the Pixel or Galaxy frame for Play, same screenshot, two correct sizes.
How do you design one screenshot set for both stores?
Here's the workflow I use to ship to both stores without doing the work twice.
1. Capture your raw screens once. Grab the actual in-app screenshots from a device or emulator at native resolution. These are your source images — you'll reuse the same ones for both stores.
2. Decide your set and order once. Write your 6–8 headlines and decide the order, strongest first. This thinking is platform-independent — the message that sells your app is the same on iOS and Android.
3. Frame and export per platform. This is the only step that branches. Drop each raw screenshot into the right device frame for each store — an iPhone frame for the App Store export, a Pixel or Galaxy frame for Play — keep the same headline and background, and export. Because the frame defines the canvas, each export comes out at that platform's correct dimensions with nothing stretched. You can do all of this for free in the PlayMockUp studio: same screenshot, swap the frame, export again.
4. Keep the design language identical. Same headline font, same background palette, same caption position across both stores. Someone who sees your app on the App Store and later on Google Play should recognize it instantly. Consistency across platforms is a small trust signal that compounds.
The whole point is to separate the *thinking* (which is shared) from the *sizing* (which differs). Do the thinking once, let a framing tool handle the sizing per platform, and shipping to both stores stops being double the work. If you want the full Android-side numbers in one place, I broke them all down in the Play Store screenshot sizes guide, and the conversion principles in how to make app screenshots that get downloads apply identically on both platforms.
1. Capture your raw screens once. Grab the actual in-app screenshots from a device or emulator at native resolution. These are your source images — you'll reuse the same ones for both stores.
2. Decide your set and order once. Write your 6–8 headlines and decide the order, strongest first. This thinking is platform-independent — the message that sells your app is the same on iOS and Android.
3. Frame and export per platform. This is the only step that branches. Drop each raw screenshot into the right device frame for each store — an iPhone frame for the App Store export, a Pixel or Galaxy frame for Play — keep the same headline and background, and export. Because the frame defines the canvas, each export comes out at that platform's correct dimensions with nothing stretched. You can do all of this for free in the PlayMockUp studio: same screenshot, swap the frame, export again.
4. Keep the design language identical. Same headline font, same background palette, same caption position across both stores. Someone who sees your app on the App Store and later on Google Play should recognize it instantly. Consistency across platforms is a small trust signal that compounds.
The whole point is to separate the *thinking* (which is shared) from the *sizing* (which differs). Do the thinking once, let a framing tool handle the sizing per platform, and shipping to both stores stops being double the work. If you want the full Android-side numbers in one place, I broke them all down in the Play Store screenshot sizes guide, and the conversion principles in how to make app screenshots that get downloads apply identically on both platforms.
What cross-platform screenshot mistakes should you avoid?
When you're shipping to two stores at once, a handful of mistakes show up over and over. I've made most of them.
Stretching one size to fit the other. This is the big one. You design beautiful 1080×1920 Android screenshots, then squash them into the iPhone's taller ratio to save time. The result looks subtly wrong — fonts slightly too wide, the device frame distorted — and users feel it even if they can't articulate why. Always export from a frame at the target size instead of resizing a finished image.
Forgetting Apple's exact device requirement. Google's looseness lulls you into thinking any reasonable size works. Then the App Store rejects your upload because 1080×1920 isn't a real iPhone resolution. Keep a note of the current required iPhone size and frame to it specifically.
Letting the two listings drift apart. It's easy to update your Play Store screenshots during a release and forget the App Store, or vice versa. A month later your two listings show different headlines and different feature emphasis for the same app. Update them together, from the same source set, every time.
Ignoring the localized text crop. If you ship to multiple languages, a headline that fits in English may overflow in German or Russian. Leave margin in your caption area so translated text doesn't collide with the device frame.
Designing for the full size, not the thumbnail. This applies on both stores equally — the screenshot is seen small first. Big headline, high contrast, one focal point. If it doesn't read at thumbnail scale, it doesn't matter how good it looks full size.
None of these are hard to avoid once you know they exist. The single habit that prevents most of them is keeping one source set and one design system, then exporting each platform's size from a real device frame rather than reshaping a finished image. Pick the right frame from the device library, keep your headlines and palette fixed, and the two listings stay in sync by default.
Stretching one size to fit the other. This is the big one. You design beautiful 1080×1920 Android screenshots, then squash them into the iPhone's taller ratio to save time. The result looks subtly wrong — fonts slightly too wide, the device frame distorted — and users feel it even if they can't articulate why. Always export from a frame at the target size instead of resizing a finished image.
Forgetting Apple's exact device requirement. Google's looseness lulls you into thinking any reasonable size works. Then the App Store rejects your upload because 1080×1920 isn't a real iPhone resolution. Keep a note of the current required iPhone size and frame to it specifically.
Letting the two listings drift apart. It's easy to update your Play Store screenshots during a release and forget the App Store, or vice versa. A month later your two listings show different headlines and different feature emphasis for the same app. Update them together, from the same source set, every time.
Ignoring the localized text crop. If you ship to multiple languages, a headline that fits in English may overflow in German or Russian. Leave margin in your caption area so translated text doesn't collide with the device frame.
Designing for the full size, not the thumbnail. This applies on both stores equally — the screenshot is seen small first. Big headline, high contrast, one focal point. If it doesn't read at thumbnail scale, it doesn't matter how good it looks full size.
None of these are hard to avoid once you know they exist. The single habit that prevents most of them is keeping one source set and one design system, then exporting each platform's size from a real device frame rather than reshaping a finished image. Pick the right frame from the device library, keep your headlines and palette fixed, and the two listings stay in sync by default.
Frequently asked questions
Are App Store and Play Store screenshot sizes the same?
No. The App Store wants exact iPhone display sizes like 1320×2868 for the 6.9-inch iPhone, while Google Play recommends 1080×1920 and only requires you stay under a 2:1 aspect ratio. Apple is strict about matching real device dimensions; Google is looser but caps the ratio.
How many screenshots can you upload to the App Store vs Play Store?
Apple allows up to 10 screenshots per device size, and Google Play allows up to 8 per form factor with a minimum of 2. In practice you design one ordered set of your strongest frames and decide how many slots to fill on each store.
Can I use the same screenshots for both iOS and Android?
You can reuse the same raw screen captures and the same headlines and order, but you should export them at each platform's correct dimensions rather than stretching one size to fit both. The cleanest way is to drop the screenshot into an iPhone frame for the App Store and a Pixel or Galaxy frame for Play, which exports each at the right size.
Which store is stricter about screenshot dimensions?
Apple is stricter. It rejects screenshots that don't match a real iPhone display size, so you have to hit exact resolutions. Google is more forgiving on size but firmly rejects any screenshot with an aspect ratio wider than 2:1.
What's the easiest way to make screenshots for both stores?
Design your set and headlines once, then use a frame-based tool to export each platform's size from the same screenshot. The [PlayMockUp studio](/create) lets you swap between iPhone, Pixel, and Galaxy frames so one design produces correctly sized exports for both the App Store and Google Play, free and in your browser.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.