Preparing iPhone or iPad assets? Read the App Store screenshot sizes and export guide for portrait and landscape pairs, required sets and a direct dimension check.
Exporting the app icon? Read the Google Play app icon size and PNG guide for the 512 × 512 listing asset. Choose the listing app icon target above; its alpha rules differ from screenshots.
Checking a Play banner? Read the Google Play feature graphic size and export guide for the 1024 × 500 target and common PNG mistakes.
App Store and Google Play screenshot sizes
These are the targets covered by this checker, not a complete device catalogue. Apple rows list portrait dimensions; their landscape equivalents also match. Use the official console reference for other device classes and submission requirements.
| Target | Pixels / ratio |
|---|---|
| App Store · iPhone 6.9-inch | 1260 × 2736; 1290 × 2796; 1320 × 2868 |
| App Store · iPhone 6.5-inch | 1284 × 2778; 1242 × 2688 |
| App Store · iPhone 6.3-inch | 1179 × 2556; 1206 × 2622 |
| App Store · iPhone 6.1-inch | 1170 × 2532; 1125 × 2436; 1080 × 2340 |
| App Store · iPad 13-inch | 2064 × 2752; 2048 × 2732 |
| Google Play · phone screenshot | Sides 320–3840; longest side ≤ 2 × shortest |
| Google Play · tablet / Chromebook guidance | Sides 1080–7680; 9:16 or 16:9 |
| Google Play · feature graphic | 1024 × 500 |
| Google Play · listing app icon | 512 × 512 |
For Apple, the iPhone 6.5-inch set is required when a 6.9-inch set is absent, and a 13-inch set is required for iPad support. Google Play's basic screenshot bounds differ from its recommendation-format guidance: the latter calls for 9:16 or 16:9 at a minimum 1080-pixel short side, plus the applicable screenshot quantity. A size match alone does not establish eligibility.
Why a screenshot can fit one store and fail another
A 1290 × 2796 export matches the listed iPhone 6.9-inch target. Its long side is more than twice its short side, so it fails the basic Google Play phone ratio check. A 1080 × 1920 export fits the Play phone bounds, but it is not one of the listed iPhone slot sizes. This is an export decision, rather than evidence that one image is better designed.
Keep separate source canvases when the app's layout or destination differs. Stretching the same pixels to a new ratio can make text and controls look distorted. Rebuild the composition around a genuine capture from the relevant supported interface, then inspect the final exported file. Preserve the original capture so you can trace which build and locale the presentation represents.
What the PNG and JPEG file check covers
The local check reads the file's encoded size and PNG color/transparency metadata. It detects an alpha channel even when the image looks opaque. Apple excludes alpha channels or transparency in screenshots; Google's screenshot and feature graphic formats are JPEG or 24-bit PNG without alpha. The separate Play listing icon requires 32-bit PNG with alpha, and its encoded byte count is checked against the listed 1024 KB limit. Changing a filename from .webp to .png does not change the encoded format.
The checker does not decode or repair the image data, verify color profiles, or evaluate legibility. JPEG orientation metadata is not applied; the reported dimensions are the encoded pixels. Open the export in your image editor and confirm its actual orientation, readability and appearance. A file that matches these header checks can still be damaged or unsuitable for submission.
A short export review for an indie app
- Record the store, device slot, locale, app build and screenshot position before exporting.
- Check the final file against its target. Resolve size and alpha warnings in the source editor, then export again.
- View the image at a small presentation size. Ask a fresh reader what task it promises, without explaining the headline.
- Confirm that the current build delivers that task, including any account, payment or setup requirement.
- Keep the previous set and the reason for each change. Review the store's actual upload validation before submitting.
For example, a fictional recipe organizer might show a saved-recipe screen as its first image. A correctly sized export still fails the team's review if a tester thinks it promises meal delivery. The next edit should clarify the task using the app's real interface. That observation supports a comprehension decision; it does not establish a conversion gain or ranking change.