GOOGLE PLAY REFERENCE
Google Play screenshot requirements and capture checklist.
A practical reference for preparing Android store screenshots across languages, app states, sample data, device classes, and Play Console output.
Last reviewed: May 14, 2026. This page summarizes the Google Play preview asset requirements most teams need during screenshot production. For final submission decisions, verify against Google's official preview asset documentation.
Google Play screenshot requirements
| Requirement | Current rule | Production note |
|---|---|---|
| Image format | JPEG or 24-bit PNG | Avoid alpha channels and keep the exported file ready for Play Console upload. |
| Screenshots per device type | Up to 8 screenshots | Prepare separate sets for phone, tablet, Chromebook, and other supported form factors when relevant. |
| Minimum dimension | At least 320 px | Both width and height should be large enough to pass Play Console validation. |
| Maximum dimension | Up to 3840 px | The longest side cannot be more than twice the shortest side. |
| Large-screen quality target | Use 1080 px to 7680 px for tablets and larger devices | Higher-resolution assets help Play feature screenshots clearly across surfaces. |
| Store listing sequence | First images matter most | Put the clearest value proposition and most stable UI screens at the beginning of the set. |
01
Plan form factors
Decide whether the release needs phone only, phone plus tablet, or additional large-screen assets.
02
Define capture targets
Save the language, screen, state, sample data, and device setup each screenshot needs.
03
Capture real screens
Use stable app states and repeatable deep links so the same product screens can be regenerated later.
04
Localize copy
Keep titles and subtitles in a table so every locale can be reviewed before export.
05
Export folders
Generate final folders by platform, locale, device class, and screen order.
Capture Android store assets without repeating setup work
Store Screenshot Studio lets you capture Android screens in the right language, page, state, and sample data setup, then finish localized copy, templates, and final Google Play export folders in one macOS project.