Google Play is far looser than the App Store about screenshot dimensions, and that flexibility is what trips people up: uploads succeed at almost any size, so nothing tells you the listing is under-specified. The tables below were read off Google's own Play Console Help on 9 September 2026 and each links back to it.
Screenshots, by device type
| Device type | Dimensions | Aspect ratio | Quantity |
|---|---|---|---|
| Phone | 320–3840 px per side | Free | 2 minimum across the listing; 4+ at 1080 px recommended |
| 7" tablet | 1080–7680 px per side | 16:9 or 9:16 | 4 minimum |
| 10" tablet | 1080–7680 px per side | 16:9 or 9:16 | 4 minimum |
| Wear OS | 384 × 384 minimum | 1:1 | 1 minimum |
| Android TV | No published size | — | 1 minimum |
| Android XR | 3840 × 2400 recommended, 1920 × 1200 minimum | 8:5 | 4 to 8, up to 8 MB each |
| Android Automotive | 800 × 1280 portrait, 1024 × 768 landscape | — | 2 minimum per orientation |
Every screenshot is JPEG or 24-bit PNG with no alpha channel. Note the asymmetry: a phone screenshot has no ratio rule at all, while a tablet screenshot must be exactly 16:9 or 9:16 — so the tablet set is the one that actually needs designing to a grid.
The other listing assets
| Asset | Dimensions | Format | Quantity |
|---|---|---|---|
| App icon | 512 × 512 | 32-bit PNG with alpha, ≤ 1024 KB | 1, required |
| Feature graphic | 1024 × 500 | JPEG or 24-bit PNG, no alpha | 1, required |
| TV banner | 1280 × 720 | JPEG or 24-bit PNG, no alpha | 1, for Android TV apps |
| Preview video | YouTube URL | — | 1; games in some sections require it |
The app icon is the one asset that wants an alpha channel — Play applies its own mask and shadow, so a pre-baked rounded square with a drawn shadow comes out wrong. Everything else refuses transparency.
Why 1080 px is the number that matters
Google's own recommendation for phone listings is at least four screenshots of 1080 pixels or more, even though the hard floor is 320. Below that recommendation a listing still publishes, but it is working against the surfaces that show large-format cards. Since those placements cost nothing, there is no reason to submit less.
The mockup workflow that fits the spec
- 01Export your app screens at 2x from Figma — a 360 × 800 Android frame becomes 720 × 1600, enough to fill a 3D device screen without upscaling.
- 02Drop each screen into a phone mockup and add a short headline above the device — the first two screenshots carry the install decision here as much as on the App Store.
- 03Set the export canvas to 9:16. MochiMockup's free tier renders at 2K, comfortably past the 1080 px recommendation.
- 04Export PNG for crisp UI, and convert to JPEG only to shave upload size — Play re-compresses either way.
- 05Reuse the composition at 1024 × 500 for the feature graphic, cropping the device to the right so the left half stays free for a tagline.
Google Play vs App Store: the differences that matter
| Rule | Google Play | Apple App Store |
|---|---|---|
| Screenshot count | 2 minimum across the listing, 4 per tablet type | 1 to 10 per app |
| Fixed resolutions | No — ranges, plus a 1080 px recommendation | Yes — 1320 × 2868 for the required 6.9" iPhone slot |
| Phone aspect ratio | None | Fixed by the slot |
| Feature graphic | 1024 × 500, required | Not used |
| Alpha channel | Screenshots no, app icon yes | Never |
Source: Google Play Console Help and Apple App Store Connect Help
Shipping on both stores: design once at 9:16 with generous margins, export the Apple set at 1320 × 2868 for the 6.9" slot and the Play set at 1080 × 1920 or larger. One mockup scene, two exports — the layout survives both.