Screenshots are the highest-leverage assets in a Play listing. They appear in search results before anyone taps, and they are the last thing someone looks at before deciding. Most apps waste them on raw UI captures.
The dimensions Play accepts
Phone screenshots
- Minimum 2, maximum 8.
- Each side between 320 px and 3840 px.
- The longest side may be at most twice the shortest — so no ultra-tall strips.
- PNG or JPEG, no alpha channel.
1080 × 1920 is the safe default: it satisfies every constraint and matches the most common phone aspect ratio.
Tablet screenshots
- 7-inch and 10-inch sets, up to 8 each, same ratio constraints.
- Required if you declare tablet support. Play now surfaces warnings and can rank you lower on large-screen devices without them.
Other form factors — Wear OS, Android TV, Chromebook and Android Auto each have their own sets if you declare support.
The first two do almost all the work
In Play search results, users see your icon, title and the first couple of screenshots without opening the listing. Whatever is in slots one and two is your advert.
So do not lead with a login screen, a settings page, or an empty state. Lead with the screen that shows the thing your app is for, already full of plausible data.
Captions: write outcomes, not features
A caption above or below the device frame gives context a raw screenshot cannot.
- Weak: "Analytics dashboard" → Strong: "See where your money went"
- Weak: "Offline mode" → Strong: "Works with no signal"
- Weak: "Export feature" → Strong: "Send your accountant a clean PDF"
Keep each under about eight words — they are read at thumbnail size.
Order them as an argument
- The core value. The one thing the app does, shown working.
- The differentiator. Why you and not the other twelve apps.
- A trust or proof point. Privacy, offline, no ads, speed.
- Supporting features, most wanted first.
Four to six well-ordered screenshots beat eight arbitrary ones.
What gets screenshots rejected or demoted
- Misleading content — showing functionality the app does not have.
- Fake ratings, awards or store badges drawn into the image.
- Calls to action referencing other stores or off-Play purchases.
- Alpha channels — an upload-time rejection.
- Placeholder or lorem ipsum data, which reads as unfinished.
Practical production notes
- Capture on a device or emulator at a clean resolution, with a full battery and no notifications in the status bar.
- Use realistic data, not "Test User 1".
- Localise the screenshots for your top markets — Play lets you upload a set per language, and screenshots in the user's language convert noticeably better.
- Keep a source file so you can regenerate the whole set when your UI changes.
The screenshot generator frames raw captures, adds captions and exports the whole set at 1080 × 1920 as a ZIP. Check your listing text against Play's limits at the same time with the listing preview.