App Store Screenshots: Sizes, Order, and the First Three
A practical guide to app store screenshots: current size checks, the first-three rule, caption hierarchy, localization, and how to test a new set.
**App store screenshots** are the part of ASO most teams treat as decoration. They are not. In a search result, the icon and first screenshot are often the only visual proof a user sees before deciding whether to tap.
The technical requirements matter, but the bigger decision is the story the first three screenshots tell. This guide covers both, without pretending the store specs never change.
Key takeaways
- Check the current Apple and Google specs before exporting; sizes change with new devices.
- The first three screenshots should form one argument, not list three features.
- Captions must be readable at thumbnail size on a phone.
- Show real UI; generic device frames with no product are weak proof.
- Change one screenshot at a time when testing.
Technical requirements: what to verify
| Store | What to check | Practical note |
|---|---|---|
| Apple | Required iPhone display size and iPad set if supported | Apple updates the required size with new devices; export from the current template |
| Apple | Up to 10 screenshots per device size | The first three are the ones most people see |
| Google Play | Phone, tablet, and other device sets | Each set can have its own order and captions |
| Google Play | Aspect ratio and min/max dimensions | Check Play Console help for the current range |
| Both | Format, colour space, and transparency rules | Use sRGB and avoid transparent corners |
Do not copy pixel dimensions from an old blog post. Open the current Apple and Google documentation, or use the templates in the store consoles, and export against those. This page is about strategy, not a frozen spec sheet.
The first-three rule
Screenshot one answers the query. Screenshot two shows the core workflow. Screenshot three proves the outcome or the differentiator. Everything after that supports a secondary use case or answers an objection.
- One: the promise, with the main screen and a short caption.
- Two: how the product delivers it, with a real interaction.
- Three: the proof: a result, a comparison, a privacy detail, or a before/after.
- Four onward: secondary features, edge cases, and trust signals.
If the first screenshot is a login screen or an empty state, the set is starting a paragraph with 'Once upon a time.' Show the product doing the job.
Caption hierarchy
A caption has about three seconds to land. Use a short benefit line, not a feature label. `See the whole month at a glance` is better than `Dashboard view`. Keep the type large enough to read at thumbnail size, and do not put critical text in the bottom third where store UI may overlay it.
- One idea per screenshot.
- Six words or fewer per caption where possible.
- High contrast; test on a bright screen.
- Consistent framing and type scale across the set.
- No fake ratings, awards, or device chrome that implies an endorsement.
Localisation
Screenshots are localised separately from the app binary. If you translate the listing but leave the screenshots in English, the page looks unfinished. Translate captions and, where possible, use screenshots of the localised UI. Right-to-left locales need mirrored reading order and checked text alignment.
Testing a new set
Change one variable per test: the first caption, the first screenshot image, or the order of the first three. Keep the rest stable. Give the test enough impressions to produce a readable signal, and record the start and end dates. If you change the icon, screenshots, and title together, you have a redesign, not an experiment.
What to avoid
- A wall of text explaining features.
- Screenshots that do not match the current app.
- Generic stock photos with no product UI.
- Borrowed competitor layouts that misrepresent the app.
- Ten screenshots when three would be clearer.
Where NewASO fits
Screenshot Studio is coming soon. Today, NewASO's Listing Studio helps you decide the promise the screenshots need to support, and the App Icon Studio compares your icon with competitor icons in store mockups. The screenshot set itself still needs a designer or a careful template pass.
For the metadata that sits above the screenshots, read app title optimization. For the icon, read app icon design.
Frequently asked questions
How many screenshots should an app store listing have?
Both stores allow up to 10 per device size. Most apps do not need 10. Three to six well-designed screenshots that tell one story are usually stronger than a crowded set.
Do screenshots affect App Store ranking?
They are primarily a conversion surface. Better screenshots can improve install rate, which can indirectly support store signals, but screenshots are not a direct keyword-ranking field.
What sizes should I use?
Use the current templates in App Store Connect and Play Console. Required device sizes change with new hardware, so verify before exporting rather than relying on an old spec list.