App Store and Google Play screenshot sizes: the working checklist

June 30, 2026 · 6 min read

Store consoles are strict about pixels. Upload a screenshot at the wrong size and App Store Connect or the Play Console will refuse it, usually at 11pm on launch night. This is the checklist we keep taped above the desk.

Pixel dimensions are only one part of approval. The companion App Store screenshot guidelines and requirements cover truthful UI, text overlays, ordering, localization, and promotion eligibility.

Apple App Store

Apple scales your 6.9″ set down for smaller devices, so one iPhone size and one iPad size covers the listing for most apps. Apple accepts additional current 6.9-inch iPhone and 13-inch iPad resolutions, so check its complete screenshot specification matrix when you are exporting outside Storeboard.

Google Play

The Play rules that trip people up:

• Screenshots must be exactly 16:9 or 9:16. Not roughly. Exactly.
• Every side must be between 320px and 3,840px, and files must stay under 8MB.
• Each slot takes between 2 and 8 screenshots.
• To be eligible for promotion placements, Google wants at least 4 screenshots with each side at 1080px or more.

The feature graphic has enough rules of its own that we gave it its own guide.

The AI-generation wrinkle

If you generate screenshots with an image model, note that most store sizes are not valid model output sizes. Image models typically want dimensions in multiples of 16 within certain pixel bounds, and 1290 × 2796 satisfies neither cleanly. The reliable pipeline is to generate at the nearest valid size (for example 1296 × 2800), then resize and center-crop to the exact store target in code. That is exactly what Storeboard does under the hood, so every file that comes out is console-ready without a resize step in Figma.

Shipping in more than one language? Every size above applies per locale; the localized screenshots note covers how to keep ten sets in sync, and the submission checklist is the full pre-upload rundown.