Google Play screenshot sizes: phone, tablet, feature graphic
Google Play accepts ranges, not exact sizes. A screenshot is fine if each side is between 320 px and 3840 px and the image is not more than twice as long as it is wide. The one exception is the feature graphic, which is exactly 1024 × 500.
That flexibility is why Play uploads rarely fail and Play listings often look untidy: the store accepts a mixed bag, then shows it in one carousel.
Play's slots and their constraints
| Slot | API image type | Canonical size | Accepted range |
|---|---|---|---|
| Phone | phoneScreenshots |
1080 × 1920 | min side 320, max side 3840, aspect ≤ 2:1 |
| 7" tablet | sevenInchScreenshots |
1200 × 1920 | min side 320, max side 3840, aspect ≤ 2:1 |
| 10" tablet | tenInchScreenshots |
1600 × 2560 | min side 320, max side 3840, aspect ≤ 2:1 |
| Feature graphic | featureGraphic |
1024 × 500 | exact, landscape only |
The canonical sizes are not Play requirements. They are the sizes AppSubmit renders to, chosen so that one listing's screenshots are the same size as each other. Any in-range image passes; a consistent set looks like it was made on purpose.
Phone, 7" and 10" slots all take either orientation. The feature graphic is landscape-only: 1024 wide by 500 tall, never rotated.
The aspect ratio catch
Max aspect 2:1 sounds generous until you screenshot a modern phone. A 1290 × 2796 iPhone capture is 2.17:1. A 1170 × 2532 capture is 2.16:1. Both are out of range for a Play phone slot even though every pixel dimension is comfortably inside 320 to 3840.
That is the single most common surprise when reusing iOS screenshots on Play: the file is not too big or too small, it is too tall. It needs padding to a wider canvas, not resizing.
The feature graphic
1024 × 500, landscape, and required before Play will let you publish. It is the banner at the top of your store listing and the image Play uses in promotional placements, so it is the one asset that gets seen without anyone tapping your app.
Two practical constraints that are not in the spec:
- The centre is the safe area. Play crops the graphic differently in different placements, so anything critical near an edge can vanish. Keep the logo and any words in the middle.
- No screenshots-of-screenshots. A feature graphic made of shrunken phone screenshots is unreadable at the size it actually renders.
Icon, and the other form factors
| Asset | Size | Notes |
|---|---|---|
| App icon | 512 × 512 | 32-bit PNG, alpha allowed, max 1 MB |
| Feature graphic | 1024 × 500 | PNG or JPEG, max 15 MB |
| Chromebook screenshots | Own slot in Play Console | Landscape 16:9 preferred; same 320 to 3840 side limits |
| Wear OS screenshots | 384 × 384 | Square (1:1) |
| Android TV screenshots | 1920 × 1080 | Landscape 16:9 |
| Android TV banner | 1280 × 720 | Required for TV apps |
AppSubmit does not generate Chromebook, Wear OS or Android TV sets, if you ship to those form factors you are uploading them by hand in the Play Console.
Play also gates some store treatment on having tablet screenshots at all: an app with phone screenshots only can be flagged as not tablet-optimised.
Counts and file limits
| Constraint | Value |
|---|---|
| Formats | JPEG or 24-bit PNG (no alpha) |
| Per file | Up to 8 MB |
| Per slot | 2 to 8 screenshots |
| Minimum to publish | 2 phone screenshots |
"24-bit PNG, no alpha" is the row that catches people. Export a PNG with transparency and Play may accept it while rendering it against a background you did not choose. Flatten first, AppSubmit's own pipeline flattens alpha on every Play variant for exactly this reason.
Reusing your App Store screenshots
You can, with one transformation. The iPhone sizes are all taller than 2:1, so they cannot go straight into a phone slot:
| Source | Play phone verdict |
|---|---|
| 1080 × 1920 | Ready, exact canonical size |
| 1290 × 2796 | Out of range (2.17:1), needs padding to 1080 × 1920 |
| 1179 × 2556 | Out of range (2.17:1), needs padding |
| 1320 × 2868 | Out of range (2.17:1), needs padding |
| 2048 × 2732 (iPad) | In range (1.33:1), accepted as-is, but sized for a tablet slot |
Padding means fitting the whole image inside the target canvas and filling the leftover strips with a background colour, not cropping the top and bottom off your headline. Cropping a 2.17:1 image down to 1.78:1 removes roughly 18% of its height, and on a marketing screenshot that height is usually where the text lives.
What "accepted" does not mean
Play will take a 320 × 480 screenshot. It will render it upscaled and blurry next to a competitor's crisp one, and no policy check will ever tell you.
The range exists for compatibility, not quality. Pick one canonical size per slot, render everything to it, and treat Play's tolerance as a safety net rather than a target.
AppSubmit checks each source image against every slot before anything is uploaded and tells you which ones pass untouched, which need a resize and which need padding, the same three verdicts described here, which you can work out yourself from the table at the top.