Google Play screenshot workflow
Google Play Screenshot Generator for Android Apps
StoreLocale helps Android teams design and localize Google Play screenshots in the browser. You frame real app screens in Pixel or Galaxy devices, add short taglines, and translate both the taglines and the in-app text into 32 languages. Exports are scaled from a tall iPhone-shaped base, so treat Play PNGs as localized drafts for now.
Last updated:
- Pixel 9 Pro and Galaxy S24 Ultra frames
- Localized taglines and in-app text
- Localized PNG drafts sorted by locale
How the workflow works
- 01
Upload the Android screens that show your core features. Each file becomes a slide, and duplicates are skipped.
- 02
Frame each screen, add a short tagline and choose a background.
- 03
Add target languages, detect and translate the text, and review each locale next to the source.
- 04
Export PNGs to review every locale, then produce the final Play-size files separately, because current Play presets come out stretched or over the 2:1 limit.
What are Google Play's screenshot requirements?
Google Play sets limits rather than fixed sizes. The rules below come from Play Console Help: Add preview assets to showcase your app (opens in a new tab).
| Rule | Google Play requirement |
|---|---|
| Minimum to publish | Two screenshots across different device types |
| Maximum per device type | Eight |
| File format | JPEG or 24-bit PNG with no alpha |
| Dimensions | 320 px minimum, 3840 px maximum; Google's large-screen section lists 1,080 to 7,680 px for tablets and Chromebooks |
| Aspect ratio | The long side can't be more than twice the short side |
| Recommendation eligibility (apps) | At least four screenshots at 1080 px or more: 9:16 portrait (1080 × 1920 minimum) or 16:9 landscape (1920 × 1080 minimum) |
| Taglines | Add only if needed, and keep them to no more than 20% of the image |
Wear OS, Android TV, Android Automotive OS and Android XR have their own rules. Wear OS screenshots, for example, must be 1:1 and can't sit inside device frames. For the full list, see the screenshot sizes reference.
Where do Google Play screenshots appear?
Google says screenshots may be displayed throughout Google Play (opens in a new tab), for instance in search or on the homepage, as well as on your store listing. That means your first images have to make sense at small sizes, outside the context of your listing.
- Lead with the screen that best explains what the app does, not a splash or login screen.
- Keep each tagline to a few words so it stays readable in search results and well under the 20% guidance.
- Use the same frame, font and background across the set so it reads as one sequence.
How should you localize Google Play graphic assets?
Play Console lets you add localized graphic assets (opens in a new tab) for each store listing language. If you don't, your listing shows the graphic assets from your default language. Google's asset guidance also asks you to localize graphic and branding text (opens in a new tab) for each market.
Google says in-game UI does not need to be localized per market, but taglines and text overlays should be. StoreLocale handles both layers:
- Taglines are editable text layers with a separate string per locale. A four-word English tagline can run much longer in German or Finnish, so read the text expansion guide before you fix the layout.
- In-app text is detected and translated for free, then repainted by an image model at 1, 2 or 4 credits per image (1K, 2K or 4K output).
- Protected content: media areas the model detects, such as video frames, posters and artwork, are masked and restored after the repaint. Rating and format badges are kept untranslated. Protection depends on detection, so check each result.
Play Console uses its own locale codes, such as iw-IL for Hebrew and es-419 for Latin American Spanish. StoreLocale folders use short codes such as he and es, so match them with the locale code guide.
Which Android device frames can you use?
| Frame | Style | Good for |
|---|---|---|
| Google Pixel 9 Pro | Detailed artwork | Stock Android look |
| Samsung Galaxy S24 Ultra | Detailed artwork | Galaxy-heavy markets |
| Clay Minimal Phone (9:16) | Drawn, neutral bezel | Brand-first sets that don't show a specific phone |
| Clay Tablet (landscape) | Drawn, neutral bezel | Editor mockups only; landscape layouts export stretched |
StoreLocale suggests a frame from each image's aspect ratio, and you can remove it at any time. Choose whichever frame makes the UI easiest to read at small sizes.
Do StoreLocale's export sizes work for Google Play?
Not without extra work yet. Every export is scaled from one 1320 × 2868 portrait design, with width and height scaled independently, and there are no per-size layouts. As a result, none of the current Play presets exports an undistorted file that is also within Play's limits.
| StoreLocale preset | Pixels | Dimensions within Play limits? | Export proportions |
|---|---|---|---|
| Original (base) | 1320 × 2868 | No; about 2.17:1, over the 2:1 limit | Undistorted |
| Modern Phone | 1080 × 2400 | No; about 2.22:1, over the 2:1 limit | Close to the base |
| Standard Phone | 1080 × 1920 | Yes (9:16) | Squeezed vertically by about 18% relative to width |
| 7-inch Tablet | 1200 × 1920 | Yes | Squeezed vertically by about 26% relative to width |
| 10-inch Tablet | 1600 × 2560 | Yes | Squeezed vertically by about 26% relative to width |
Frequently asked questions
How many screenshots does Google Play require?
At least two across different device types to publish, and up to eight per device type. Google recommends at least four 1080 px or larger screenshots to be eligible for recommendations, according to Play Console Help (opens in a new tab).
What aspect ratio should Google Play phone screenshots use?
9:16 portrait (at least 1080 × 1920) or 16:9 landscape (at least 1920 × 1080). In any case the long side can't be more than twice the short side.
Do I have to localize the app UI in my screenshots?
Google says in-game UI doesn't need to be localized per market, but taglines and text overlays should be. Translating the UI as well usually makes the listing easier to follow for local users, and StoreLocale can do both.
What happens if I don't upload localized screenshots?
Google Play shows the graphic assets from your default language on every listing that lacks its own.
Does StoreLocale upload to Play Console or run store listing experiments?
No. StoreLocale exports PNG files. Uploading and A/B testing both happen in Play Console. See the ASO screenshot tool page for how experiments fit into the workflow.
Why do StoreLocale's Play-size exports look squeezed?
Every export is scaled from a 1320 × 2868 base. Play's 9:16 phone and 16:10 tablet sizes are shorter than that base, so content is compressed vertically, while the taller presets exceed Play's 2:1 aspect limit. Produce final Play files separately for now.
Can I use my own AI key?
Yes. Add an OpenRouter or Gemini key and generations use 0 platform credits. The key is stored in your browser, so you'll need to add it again on other devices.
Sources
Explore related workflows
Store screenshot sizes
Every Google Play and Apple screenshot requirement in one reference.
App Store vs Google Play locale codes
Match language folders to the exact codes each console expects.
App screenshot translator
Detect, translate and repaint the text inside app screenshots.
Text expansion by language
Plan tagline length for languages that run longer than English.
Supported languages
The 32 target languages StoreLocale can localize into.
All localization guides
Locale codes, text expansion, RTL layouts and pre-upload checks.
Translate your next screenshot set with StoreLocale
Upload your screenshots, pick target languages, and review every localized version before you export.