App Store vs Google Play Screenshot Sizes
Apple and Google both accept portrait and landscape screenshots, but their systems are organized differently. Apple validates exact pixel pairs for named display classes. Google Play allows a broad dimension range, then recommends high-resolution 9:16 or 16:9 assets for discovery placements. This comparison helps you prepare both without treating one store as a resized copy of the other.
The short comparison
For a modern iPhone listing, a 6.9-inch set is the practical Apple starting point; App Asset Kit defaults to 1320 × 2868 portrait. When an app supports iPad, prepare a genuine 13-inch iPad set, commonly 2064 × 2752 portrait. Apple also lists alternate accepted pixel pairs within those classes.
For a regular Android app, 1080 × 1920 portrait is a practical Google Play starting point. It satisfies the high-resolution 9:16 recommendation pattern while remaining easy to produce from current device captures. Google’s hard limits are broader: each dimension must be 320–3840px and the long edge cannot exceed twice the short edge.
| Question | Apple App Store | Google Play |
|---|---|---|
| Sizing model | Exact pixel pairs by device display class | Flexible 320–3840px range with ratio constraint |
| Practical phone default | 1320 × 2868 portrait (6.9-inch) | 1080 × 1920 portrait (9:16) |
| Practical tablet default | 2064 × 2752 portrait (13-inch iPad) | 1080 × 1920 or higher with genuine tablet UI |
| Quantity | 1–10 per supported device context and localization | At least 2 across device types; up to 8 per type |
| Formats | JPEG, JPG, or PNG without transparency | JPEG or opaque 24-bit PNG |
| Promotional companion | Optional app previews and other product-page assets | Required 1024 × 500 feature graphic |
Why Apple uses exact device classes
App Store Connect groups screenshots by supported device display. A file must match one of the accepted portrait or landscape pairs for that class. Supplying a highest-resolution set can let Apple scale consistent UI for smaller phones, but it does not convert phone UI into an iPad layout.
The 6.5-inch iPhone category remains required when 6.9-inch screenshots are not provided. Apps that run on iPad need the 13-inch iPad category. Because the accepted list can change with hardware, treat Apple’s specification page as the source of truth and keep your export presets reviewable.
| Class | Portrait | Landscape | When to prepare it |
|---|---|---|---|
| 6.9-inch iPhone | 1320 × 2868 | 2868 × 1320 | Primary modern iPhone set |
| 6.5-inch iPhone | 1284 × 2778 | 2778 × 1284 | Required when 6.9-inch is not supplied |
| 13-inch iPad | 2064 × 2752 | 2752 × 2064 | Required when the app supports iPad |
Why Google Play uses ranges and recommendation ratios
Google Play accepts multiple device types and a wider range of screenshot shapes. The hard rules permit flexibility, while recommendation surfaces have stricter quality guidance. For regular apps, prepare at least four screenshots at 1080px or higher using 9:16 portrait or 16:9 landscape when those discovery formats matter.
Games have a separate recommendation pattern and should show genuine gameplay. Tablet, Chromebook, Wear OS, TV, Automotive, and XR categories add their own presentation considerations. A phone screenshot that technically fits the pixel range is not a meaningful tablet asset.
| Output | Portrait | Landscape | Use |
|---|---|---|---|
| Recommended baseline | 1080 × 1920 | 1920 × 1080 | Regular phone or tablet listing |
| Higher resolution | 1440 × 2560 | 2560 × 1440 | High-density source and export |
| Maximum-edge 9:16 | 2160 × 3840 | 3840 × 2160 | Optional large output within general limit |
| Feature graphic | — | 1024 × 500 | Separate required listing graphic |
Do not reuse one platform screenshot unchanged
A shared visual system can save design time, but the captured interface, hardware frame, wording, and export dimensions should match the target store. An iOS capture inside an Android-looking device weakens trust. A phone layout enlarged into a tablet frame hides the real large-screen experience.
Reuse the story architecture and brand system instead: the same five benefits can be supported by platform-specific screens, device treatments, and dimensions. This keeps the campaign coherent while giving each storefront accurate product evidence.
- Keep the same strategic panel order when it works for both stores
- Capture native UI for each platform
- Prepare tablet assets from genuine tablet layouts
- Export each store from its own validated presets
A two-store production checklist
Create a small matrix before exporting so no platform, form factor, orientation, or localization is silently reused in the wrong place. Open the final files and verify their actual dimensions rather than relying on folder names alone.
- Choose primary device categories for each store
- Capture real iOS and Android states
- Select portrait or landscape based on the product
- Create separate phone and tablet sets when supported
- Match caption language to the listing localization
- Verify opaque output and exact pixels
- Upload in the intended story order
Frequently asked questions
Can the same screenshot file be uploaded to both stores?
Sometimes it may fit both stores technically, but platform-specific UI, device framing, and export requirements usually make separate assets clearer and more accurate.
What is a practical App Store iPhone size?
1320 × 2868 portrait is a useful 6.9-inch starting preset; Apple also accepts other exact pairs in that class.
What is a practical Google Play screenshot size?
1080 × 1920 portrait or 1920 × 1080 landscape is a strong recommendation-ready starting point for regular apps.
Does Google Play need a feature graphic?
Yes. It is a separate 1024 × 500 JPEG or opaque 24-bit PNG listing asset.
Create the screenshot set while the plan is fresh.
Upload real captures, write one focused message per screen, and export exact App Store or Google Play dimensions in your browser.
Open App Asset Kit