What the App Store Screenshot Size Checker does
This checker reads your app screenshots in the browser and tells you, for each one, which App Store device slot it fits, whether Google Play will accept it, and what is wrong if not - wrong pixel size, a transparent alpha channel, an unsupported format or an aspect ratio Play rejects. The rules come from a dated copy of Apple's and Google's published specifications, shown on the page.
The two stores work differently. App Store Connect accepts only an exact list of pixel sizes per device class, so a screenshot two pixels off is refused. Google Play accepts a range of sizes and ratios instead, but refuses anything whose long side is more than twice the short side - which rules out most modern iPhone-shaped images.
How to use it
- Drop your PNG or JPEG screenshots onto the page, or choose them. They are read in this tab and never uploaded. You can also type sizes such as 1290x2796 to check dimensions before you export.
- Choose Check. The summary shows how many images each store accepts and whether the count rules are met.
- Read the table: the App Store slot each image fits, and a pass or problem for each store.
- Open the per-image findings for the exact problem - for example the nearest accepted App Store size, or that the PNG carries an alpha channel.
- Download the results as CSV or JSON for your release checklist, or print them.
Reading the results
An App Store slot means the image's pixel size is on Apple's accepted list for that device class. Some sizes fit more than one class: 2048 x 2732 is accepted for both 13-inch and 12.9-inch iPads.
Apple requires screenshots for the 6.9-inch or 6.5-inch iPhone if your app runs on iPhone, and 13-inch iPad if it runs on iPad; smaller devices are optional and scaled from the larger set. The summary warns when the required iPhone size is missing.
For Google Play, a problem means the image breaks a stated requirement. Notes about the 16:9 or 9:16 recommendation are not rejections: they affect whether Play can use the image in its large-format recommendation slots.
Worked example: a mixed set of four
The example draws four screenshots in the page: 1290 x 2796 JPEG, 2064 x 2752 JPEG, 1080 x 1920 PNG and 1284 x 2780 JPEG.
1290 x 2796 is on Apple's 6.9-inch list, and 2064 x 2752 is on the 13-inch iPad list, so both are accepted. 1284 x 2780 is refused by Apple: the nearest accepted size is 1284 x 2778, two pixels shorter. The 1080 x 1920 PNG is not an App Store size at all, and because the browser saves canvas PNGs with an alpha channel, both stores flag it for transparency.
On Google Play, the two tall iPhone-shaped images fail: 2,796 / 1,290 is a ratio of 2.17, over Play's 2:1 limit. The iPad image passes. The 1080 x 1920 image would be the ideal Play phone screenshot - 9:16 at 1080 px - once saved without alpha.
Why transparency is flagged even when the image looks solid
Apple refuses screenshots with an alpha channel, and Google Play asks for 24-bit PNG with no alpha. The check is about how the file is stored, not what it looks like: a PNG saved as RGBA has an alpha channel even if every pixel is fully opaque. Design tools and browsers often save RGBA by default.
Export as JPEG, or as PNG with the transparency option turned off, to fix it. This checker reads the PNG header itself - the colour type and any tRNS transparency chunk - so it reports the file exactly as the stores will see it.
Limitations: what the result does not prove
- The size table is a dated copy of Apple's and Google's help pages, not a live feed. The page shows the review date; check the sources before a release, as new devices add sizes.
- It checks dimensions, format, transparency and counts. It does not judge content rules - such as showing the real app interface, or Apple's and Google's policies on text and device frames - which reviewers decide.
- Google Play's per-file size limit is not stated on its screenshot help page for phones, so it is not checked. Apple's App Preview videos are also out of scope.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- App Store Connect Help - Screenshot specifications - checked 19 Sep 2026
- Play Console Help - Add preview assets to showcase your app - checked 19 Sep 2026
- W3C - PNG specification (IHDR colour types and tRNS)
Frequently asked questions
What screenshot size does the App Store require for iPhone?
If your app runs on iPhone you must provide the 6.9-inch size (1260 x 2736, 1290 x 2796 or 1320 x 2868 in portrait) or, if you do not, the 6.5-inch size (1284 x 2778 or 1242 x 2688). Smaller iPhone sizes are optional and scaled from these. The table on this page lists every accepted size.
Why does Google Play reject my iPhone-sized screenshots?
Google Play requires the longer side to be no more than twice the shorter side. Modern iPhone screenshots are about 2.17 times taller than wide, so they break the rule. Crop or pad them to 9:16, such as 1080 x 1920, for Play.
Can I use the same screenshots for iPad and iPhone?
No. App Store Connect checks the pixel size against each device class, and iPad sizes are close to 3:4 while iPhone sizes are much taller. You need a separate set for each class you provide, and 13-inch iPad screenshots are required if the app runs on iPad.
How many screenshots can I upload?
App Store Connect accepts one to ten per device size and localisation. Google Play shows up to eight per device type and needs at least two across device types to publish; tablets and Chromebooks have a minimum of four.
Is a PNG with an alpha channel really rejected if nothing is transparent?
Apple's specification says alpha channels and transparency are not allowed, and Play asks for PNG with no alpha. The safe reading is that the channel itself is the problem, so the checker flags any RGBA or greyscale-with-alpha PNG, or a tRNS chunk, regardless of the pixel values.
Does this upload my screenshots anywhere?
No. The files are read by JavaScript in this browser tab to get their width, height, format and colour type, and nothing is sent to a server. Closing the tab discards them.
Last reviewed by the A2Z.Tools team against the sources listed above.
