App Store and Google Play screenshot sizes: the working checklist
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.
Apple App Store
| Slot | Size (portrait) | Notes |
|---|---|---|
| iPhone 6.9″ | 1290 × 2796 | The current required iPhone size. Up to 10 screenshots. |
| iPad 13″ | 2048 × 2732 | Required if your app runs on iPad. |
Apple scales your 6.9″ set down for smaller devices, so one iPhone size and one iPad size covers the listing for most apps.
Google Play
| Slot | Size | Notes |
|---|---|---|
| Phone | 1080 × 1920 | Any exact 16:9 or 9:16 works; this is the standard choice. |
| 7″ tablet | 1440 × 2560 | Same aspect rules as phone. |
| 10″ tablet | 1620 × 2880 | Same aspect rules as phone. |
| Feature graphic | 1024 × 500 | Required to be eligible for featuring. |
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 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.
Skip the artboards entirely.
A description, a screenshot, or your URL in; the full store-ready set out. Start free with a draft project.
Build my listing →