App Store Screenshots That Convert: A Practical Guide

Ranking gets you seen. Screenshots decide whether being seen becomes an install, and because conversion feeds back into ranking, a better first screenshot raises your position as well as your download count.

Last updated 20 August 2026 · by the ASOWeb team

Why only the first three matter

On a search results page, both stores show a preview of your first two or three screenshots without anyone opening your listing. Most people decide there. Scrolling your gallery is a minority behaviour, and the people who do it were already interested.

The practical consequence: design as if you get three images and nothing else. Anything essential that lives in screenshot seven is, for most viewers, not on your listing at all.

What belongs in each of the three

1. The first states what the app is. Not your cleverest feature, the category-defining thing. A stranger should be able to say what your app does after one second.
2. The second states why yours. The differentiator: the thing you have that the four apps beside you do not.
3. The third removes the main objection. Usually "is this hard to set up", "does it cost anything", or "does it work with what I already use".

Everything after that is for the minority who scroll: depth, secondary features, social proof.

Writing captions that do work

A screenshot without a caption asks the viewer to work out what they are looking at from a small image of a user interface. Very few will.

• State a benefit, not a feature. "Share one album with everyone at the wedding" beats "Album management".
• Keep it to about five words. These are read at thumbnail size while scrolling.
• Put the caption at the top. On a phone-shaped image, the bottom third is frequently cropped in previews.
• Use sentence case and high contrast. All-caps at small sizes reads slower.
• Do not repeat your app name. It is already directly above the gallery.

Captions are not indexed for search on either store. They earn their place purely through conversion, which, since conversion feeds ranking, is still ranking work.

Testing alternatives for free

Both stores give you a free experiment framework, and most developers never use either.

• Apple: Custom Product Pages. Up to 35 variants with different screenshots and previews, each with its own URL. Combined with Product Page Optimization you can run a genuine split test against your default page.
• Google Play: store listing experiments. Native A/B testing on icon, screenshots, short description and full description, with statistical significance reported for you.

Test one variable at a time, and start with the first screenshot, it carries more of the decision than the rest combined. Run until the tool reports significance rather than until the numbers look encouraging.

Seven mistakes worth avoiding

• A bare UI screenshot with no caption. The commonest and most costly mistake.
• Marketing copy nobody can parse at thumbnail size. If it needs reading twice, it is not working.
• Looking exactly like the four apps beside you. Open the shelf you compete on and look at the row. If everyone uses the same purple gradient, be the one that does not.
• Burying the differentiator at position five. Almost nobody reaches it.
• Text in the bottom third. Frequently cropped in search previews.
• Never updating them. Screenshots age with your UI, and a stale one signals an abandoned app.
• Ignoring the localised versions. Screenshots are per-localisation, and English captions in a non-English storefront convert badly.

Frequently asked questions