Google Play Screenshot Sizes & Requirements (2026)
At least 2 phone screenshots (JPEG/PNG, 320–3,840px per side), a 512×512 icon, and a 1024×500 feature graphic. Compliance gets you submitted; one-idea-per-shot composition with thumbnail-readable headlines gets you installed.
The requirement table
Phone: 2–8 screenshots, JPEG or 24-bit PNG, 320–3,840px. Icon: 512×512, 32-bit PNG. Feature graphic: 1024×500 JPG/PNG. 7-inch and 10-inch tablets need their own sets if you list tablet support. Produce the phone set in one pass with our screenshot generator — 1080×1920 exports that validate on upload.
Composition that converts
Reviewers check dimensions; users check meaning. Lead with the core value proposition, keep headline text legible at list-thumbnail size, keep key copy inside safe zones, and never show UI your binary doesn't ship — mismatched screenshots are a policy finding, not just bad marketing. Pair visuals with copy from the store listing generator.
Text size is the silent killer
Anything below ~30sp equivalent turns to noise on a phone screen in the Play app. If a caption needs squinting in preview, reframe: fewer words, bigger type, or split one busy shot into two focused ones.
Frequently asked questions
How many screenshots does Google Play require?
Minimum 2 phone screenshots (up to 8), plus a 512×512 high-res icon and a 1024×500 feature graphic. Tablets, wearables, TV, and ChromeOS have their own screenshot slots if you target those form factors.
What dimensions and formats are accepted?
Phone screenshots: JPEG or 24-bit PNG (no alpha), each side between 320 and 3,840 pixels. 1080×1920 portrait is the standard working size our templates export.
What makes a screenshot convert instead of just comply?
One idea per screenshot, headline-readable at thumbnail size, first screenshot showing the core value, and real UI — not splash screens. Order tells a story: value, proof, depth.
Can I use the same screenshots for all locales?
You can, but localized captions convert better where your audience isn't English-first. Keep text in editable template fields so re-exporting per locale is minutes, not a redesign.
Keep going
Make screenshots that convert
Templates, safe zones, validated exports.