Play crops less, but shows fewer
Play surfaces the first three screenshots in most listing layouts and, unlike the App Store, will happily show a landscape set. Your first frame still carries almost all of the weight.
Drop in your Android screens — Pixel, Samsung, or straight out of the emulator. Get a phone gallery at 1080 × 1920, a tablet gallery at 1600 × 2560, and a ZIP already split into the folders you upload from, in as many store languages as you ship. Free to try, no card.
A Play Store screenshot generator turns raw captures from your Android app into the marketing images Google Play shows in your listing. It frames each screen in a device shell, sets a headline above it, and exports at dimensions and ratios Play Console will accept — plus, ideally, the feature graphic and icon that a listing cannot publish without.
Google ships a free Device Art Generator that does the first of those jobs. It wraps a capture in device artwork and stops there: no headline, no store sizing, no tablet set, no second language. That gap is the reason this category exists.
Android also makes the framing question harder than iOS does. There is no single current handset, so a Pixel shell and a Samsung shell both read as “an Android phone” while looking noticeably different. Here the device shell is chosen for you to sit neutral enough that the screen inside it stays the thing people look at.
Screenshots are one row of five. A listing missing its feature graphic simply will not publish.
| Asset | Size | Rule | Here |
|---|---|---|---|
| Phone screenshots | 1080 × 1920 recommended | 2 to 8 images. 16:9 or 9:16. Minimum 320 px and maximum 3840 px on any side. | Generated |
| 7" tablet screenshots | 1080–7680 px per side | Minimum 4, up to 8. 16:9 landscape or 9:16 portrait. Skipping these costs you tablet-surface visibility, not just polish. | Generated |
| 10" tablet screenshots | 1080–7680 px per side | Minimum 4, up to 8. Exported at 1600 × 2560 for a crisp portrait tablet listing. | Generated |
| Chromebook screenshots | 1080–7680 px per side | Minimum 4 if you target ChromeOS. Same rules as the tablet sets. | Generated |
| Feature graphic | 1024 × 500 | Mandatory. Shown at the top of your listing and in some Play surfaces. No transparency. | Guide |
| App icon | 512 × 512 | 32-bit PNG with alpha. Play applies its own masking and shadow. | Guide |
The two marked Guide are static brand assets rather than screen mockups — sizes and layout rules are on feature graphic and app icon sizes.
Upload two to eight Android screens as PNG or JPG, up to 10 MB each.
Select Google Play Store as the target — the canvas locks to 9:16.
Add up to five store languages; headline copy is written natively per language, not translated word for word.
Optionally request up to four art directions of the same screen and keep the one that fits.
Export with the Google Play preset. The ZIP contains PlayStore/Phone at 1080 × 1920 and PlayStore/Tablet at 1600 × 2560, split by language.
Play surfaces the first three screenshots in most listing layouts and, unlike the App Store, will happily show a landscape set. Your first frame still carries almost all of the weight.
A 1024 × 500 banner appears before your screenshots on the listing page. If it contradicts the gallery below it, the listing reads as unfinished. Match the palette and the headline voice.
Play validates aspect ratio and edge length rather than an exact pixel size. That is more forgiving than App Store Connect — but it also means a badly proportioned image passes validation and looks wrong in the store.
Play lets you run gallery experiments against real traffic at no cost. It is the cheapest conversion work available to an Android app, and most teams never switch it on.
Capture your app on a Pixel, a Samsung device or the Android emulator and export as PNG or JPG. Upload two to eight of them, pick Google Play as the target, and render. Each screen is framed in an Android shell, given a headline, and exported at 1080 × 1920 for phone plus the tablet sizes if you need them. The download is a ZIP already foldered the way Play Console expects, so there is no renaming step.
This one has a free tier — three credits on signup, one credit per rendered screenshot, no card. That covers three finished frames, which is enough to see how the output looks on your own screens. Google also ships a free Device Art Generator, but it only wraps a capture in a device frame: no headlines, no store sizes, no localisation.
1080 × 1920 px is the practical answer for phones. Play formally accepts anything from 320 px to 3840 px on each side, in a 16:9 or 9:16 ratio, with no side more than twice the length of the other. Each file must be under 8 MB, PNG or JPEG, with no transparency.
A minimum of two and a maximum of eight per device type. Play will not publish a listing with fewer than two phone screenshots.
Only if your app declares tablet support — but if it does, Play now wants a minimum of four screenshots per tablet size rather than treating them as optional extras. Falling short reduces how your listing is surfaced on tablet and Chromebook, so it is worth generating the 10" set even when phone is your focus.
Technically yes if the ratio fits, but you should not show an iPhone bezel on a Play listing — it reads as a port and Play discourages referencing other platforms. Generate the Android set with an Android device shell instead; select "Both Platforms" and one batch produces both.
The feature graphic is a single 1024 × 500 banner at the top of the listing and is required. Screenshots are the scrollable gallery beneath it. They serve different jobs: the banner sets the brand, the gallery sells the features.
Three free credits, one credit per screenshot. Enough to see your own app framed before you decide anything.
Create a free account