Play Store vs App Store screenshots differ in size, count, and ratio rules: Apple's 6.9-inch iPhone slot accepts 1290×2796 and up to 10 screenshots, while Google Play takes 2–8 phone screenshots with a long side no more than 2.3 times the short side, and recommends 9:16 portrait at 1080×1920 or larger. Share the story and headlines; split frames, captures, and export sizes.
Most cross-platform teams lose time in one of two ways. Either they maintain two completely separate design files that drift apart every release, or they upload one set everywhere and end up with cropped headlines, an iPhone frame on Google Play, or a rejected upload. This guide shows where the stores genuinely differ, where they do not, and a workflow that keeps one narrative with two native exports.
Play Store vs App Store screenshot specs side by side
Start with the hard constraints, because they decide what you can reuse at all. The numbers below come from Apple's screenshot specifications and Google Play Console Help. Both stores update requirements, so confirm in App Store Connect and Play Console before a release. For a deeper single-store breakdown see the App Store screenshot size guide and the Google Play screenshot size & requirements guide.
- Screenshot count — App Store: up to 10 per device size per localization. Google Play: 2–8 phone screenshots.
- Main phone size — App Store: the 6.9-inch iPhone slot accepts 1320×2868, 1290×2796 or 1260×2736 portrait. Google Play: 1080×1920 portrait (9:16) is the common recommendation.
- Older iPhone slot — App Store: the 6.5-inch slot accepts 1284×2778 and 1242×2688.
- Ratio rule — Google Play: each side between 320 px and 3840 px, and the long side no more than 2.3× the short side; 9:16 portrait (minimum 1080×1920) is recommended. App Store: fixed pixel dimensions per slot rather than a ratio range.
- Formats — App Store: PNG or JPEG, no transparency. Google Play: JPEG or 24-bit PNG, no alpha.
- Tablet — App Store: if your app runs on iPad, a 13-inch iPad set (2064×2752 or 2048×2732) is required. Google Play: tablet screenshots are separate, optional-but-recommended assets.
- Header asset — Google Play: a 1024×500 feature graphic is required. App Store: no equivalent banner.
- Video — App Store: app preview videos uploaded per device size, which can appear before screenshots. Google Play: a promo video added as a YouTube URL.
Why you cannot upload the same file to both stores
The quiet trap is the ratio. A 1290×2796 image has a long side about 2.17× its short side. That is inside Google Play's 2.3× limit, so Play will accept the file, but it is not the 9:16 portrait format Google recommends (minimum 1080×1920) for its recommendation surfaces, and it still shows iPhone UI on an Android listing. Going the other way, a 1080×1920 image is not one of the pixel sizes Apple accepts for the iPhone slots, so App Store Connect will not take it.
Even if you squeeze one into the other's dimensions, the composition breaks. The iOS frame is taller and narrower, so a layout tuned for it either gets letterboxed or loses vertical space for the headline when converted to 9:16. Stretching pixels makes UI text soft, which shows up immediately next to sharp competitor listings. Export native masters for each store instead; if you are already fighting upload errors, the store screenshot checklist covers the common rejections.

How each store displays screenshots in search and on the product page
On the App Store, search results for an app without an app preview typically show the first few portrait screenshots right under the name and icon. That makes your first three frames a search-results asset, not just product-page decoration. Treat them as a mini-pitch that reads at thumbnail size, and see App Store screenshot order that converts for sequencing.
On Google Play, the layout varies more by device, query, and listing. Search results often lean on the icon, title, and rating, with screenshots or video surfacing in some placements. On the product page, the promo video or feature graphic can occupy the top of the listing, with the screenshot carousel beneath. The practical consequence: on Play, the feature graphic and the first two screenshots share the job of the first impression, so they need to agree visually.
Both stores show screenshots in a horizontal carousel that many visitors only partly scroll. Front-load the outcome on both, regardless of how many total frames you upload.
Audience and UI conventions: Android vs iOS
Android and iOS users recognise their own platform at a glance: navigation patterns, status bars, system sheets, back behaviour, and device silhouettes. A Google Play listing that shows an iPhone frame, a Dynamic Island, or iOS-style share sheets reads as a port at best and careless at worst. Use Android captures and a neutral or Android-style device frame on Play, and iPhone captures and frames on the App Store.
Policy points the same direction. Google Play's metadata policy prohibits misleading store listing content, and its preview asset guidance asks that screenshots represent the actual in-app experience. Showing another platform's UI, or features that only exist on iOS, risks confusing users and inviting a review issue. Apple's guidelines likewise expect screenshots to show the app in use. Never capture a screen on one platform and present it as the other.
Audience mix can differ too. If your Android users skew toward different regions or price sensitivity, the same headline can land differently. That is a messaging test, not a reason to rebuild the whole set.
What to keep shared across both stores
The expensive part of screenshots is thinking: which outcome leads, which proof follows, what each headline says. That work is platform-neutral, so do it once. Most of the time you can reuse screenshots for both stores at the story level while still exporting different files.
- The narrative order: hero outcome, then proof, then depth features, then trust or social proof
- Headline and subtext copy (adjust only where a platform-specific feature differs)
- Brand colours, typography, and background treatment
- Localization plan and translated strings
- The underlying feature list each frame demonstrates
What to split per store
Split anything that is physically tied to a platform or a store's format. This list is where most of the per-store effort belongs.
- Device frames: iPhone frames on the App Store; Android or frameless on Google Play
- UI captures: real screens from the iOS build and the Android build respectively
- Aspect ratio and export size: 1290×2796 (or another accepted 6.9-inch size) vs 1080×1920
- Feature graphic: Google Play only, 1024×500, designed as its own banner
- Video: app preview on iOS vs a YouTube promo video on Play
- Screenshot count: up to 10 on iOS vs 2–8 on Play, so trim the weakest frames for Play
- Platform-only features: widgets, watch apps, or integrations that exist on one OS
Decision table: reuse or split?
Use this as a quick reference when planning a release. Each line reads: asset — decision — reason.
- Story and slide order — Share — the user's job does not change between platforms
- Headlines and subtext — Share, with edits for platform-only features — copy is the costliest part to rewrite
- Background and brand style — Share — keeps the brand recognisable across stores
- Device frame — Split — an iPhone frame on Google Play misrepresents the app
- In-app captures — Split — each store should show its own platform's real UI
- Export size and ratio — Split — 1290×2796 passes Play's 2.3:1 limit but is not the recommended 9:16; 1080×1920 is not an accepted iPhone size
- Feature graphic — Play only — required 1024×500 banner with no iOS equivalent
- Video — Split — app previews and Play promo videos have different formats and hosting
- Screenshot count — Split — trim to 8 or fewer for Play
Testing screenshots on each store
Both stores let you test creative natively, but the tools differ. On the App Store, Product Page Optimization lets you test up to three treatments against your original product page, varying icons, screenshots, and app previews, with tests running for up to 90 days. On Google Play, store listing experiments can test the icon, feature graphic, screenshots, and short or full description, with up to three variants against the current listing, and localized experiments for specific languages.
Because the stores are tested separately, a winner on one is a hypothesis for the other, not a proven result. A headline that wins on Google Play is worth trying in a PPO treatment, but audience and layout differences mean it may not transfer. The App Store screenshot A/B testing guide covers test design and how long to wait before calling a result.
A one-project workflow for both stores with StoreShots
The goal is one creative direction and two native outputs without maintaining two design files. In StoreShots AI, the uploaded captures stay the source of truth; the AI plans purposes, headlines, and themes around them rather than redrawing your UI.
Generate App Store and Play Store sets1290×2796 and 1080×1920 PNG exports from real app captures, as a ZIP.- Capture 3–10 real screens from the iOS build and, separately, from the Android build
- Write down the shared story: hero outcome, two or three proof frames, then depth
- Create a project with the iOS captures and preview the hero frame before generating
- Generate the App Store pack and export PNGs at 1290×2796 as a ZIP
- Repeat with the Android captures and export the Google Play pack at 1080×1920
- Align headlines across both packs, using chat revisions on individual slides where they drifted
- Design the 1024×500 feature graphic separately; StoreShots does not generate feature graphics, iPad sets, Android tablet sizes, or app preview videos
- Upload, then plan PPO and store listing experiments from the same headline hypotheses
Quick reference: Play Store vs App Store screenshots
If you only remember a handful of facts, make them these. For cost planning, credits are one-time packs that never expire; see pricing.
- App Store: up to 10 screenshots per device size per localization; Google Play: 2–8 phone screenshots
- 1290×2796 is accepted in Apple's 6.9-inch slot; 1080×1920 is the common Play phone size
- Google Play accepts a long side up to 2.3× the short side but recommends 9:16, so tall iPhone masters are not the best fit
- Neither store accepts transparency in screenshots
- Google Play requires a 1024×500 feature graphic; the App Store has no equivalent
- Do not show iPhone frames or iOS UI on Google Play
- Share story and copy; split frames, captures, sizes, and the feature graphic
- Test with PPO on iOS and store listing experiments on Play, separately
FAQ
Questions about this topic
Can I use the same screenshots for the App Store and Google Play?
You can reuse the story and headlines, but you should not reuse the same files. A 1290×2796 iPhone screenshot fits within Google Play's 2.3:1 limit but misses the recommended 9:16 format and shows iOS UI, and 1080×1920 is not an accepted iPhone size. Export native sets per store and swap in each platform's own UI captures and device frames.
What size should Android vs iOS screenshots be?
Use 1080×1920 portrait for Google Play phones and 1290×2796 (or another accepted 6.9-inch size) for the App Store. Google Play allows any size between 320 and 3840 pixels per side with the long side at most 2.3 times the short side, while Apple specifies exact pixel sizes per device slot. Check App Store Connect before each release, since Apple updates its specifications.
How many screenshots does each store allow?
The App Store allows up to 10 screenshots per device size per localization, and Google Play allows 2–8 phone screenshots. If your iOS set has ten frames, cut the two weakest for Google Play rather than cramming two features into one frame. Front-load the strongest outcome on both, because many visitors never scroll the full carousel.
Is it a problem to show an iPhone in Google Play screenshots?
Yes, avoid it. An iPhone frame or iOS interface on Google Play misrepresents what Android users will get, and Google Play's metadata policy prohibits misleading listing content. Use real Android captures with a neutral or Android-style frame. The same applies in reverse: show iOS screens and iPhone frames on the App Store.
Does the App Store have a feature graphic like Google Play?
No, the 1024×500 feature graphic is a Google Play requirement with no App Store equivalent. On the App Store, the first screenshots or an app preview video carry the first impression instead. Design the feature graphic as its own banner that matches your first two Play screenshots, rather than cropping a screenshot to fit.
Should I A/B test screenshots on both stores?
Yes, but treat each store's result separately. Apple's Product Page Optimization tests up to three treatments for up to 90 days, and Google Play store listing experiments test up to three variants against the current listing. A winner on one store is a strong hypothesis for the other, not a guaranteed result, because audiences and layouts differ.
Sources
Official references used
- Screenshot specifications (Apple App Store Connect Help)
- Product page optimization (Apple Developer)
- Add preview assets: screenshots and graphics (Google Play Console Help)
- Store listing experiments (Google Play Console Help)
Continue
Choose the next step
Related