What Should Go in Your First Three App Store Screenshots?

Most app teams build ten screenshots and spend the same care on each one. The store then shows three of them, and almost nobody scrolls, so the other seven are a rounding error on the install rate.

Getting this right is cheap compared with everything else in user acquisition, which is what makes it worth doing before the next media budget goes out the door.

What should go in your first three app store screenshots?

The first three screenshots should carry the value proposition, the best-looking moment of the product in use, and the one difference between you and the obvious alternative. Keep them in that order, because a visitor deciding in seconds reads left to right and stops as soon as they are convinced or bored.

The ordering is not a style preference. Per AppFollow’s 2026 screenshot guidance, App Store search results display up to three portrait screenshots without any tap, so those three frames are doing the work of a whole landing page before the visitor has committed to anything.

What goes wrong is usually sequence rather than craft. Teams lead with onboarding screens, settings or a sign-in page, because that is the order a user meets the app in, and a browsing visitor has no reason to care about any of them.

Lead with the outcome and show the mechanism second. A frame that says what the user gets, followed by a frame showing the screen where they get it, answers the two questions in the order a stranger asks them.

Frame	Job	What goes in it	Common mistake
1	the value proposition	one benefit line over a real screen	an onboarding or sign-in screen
2	the product doing the work	the screen a happy user spends most time in	the densest screen in the app
3	the differentiator	the one claim a competitor cannot make	a repeat of frame one’s benefit
4 to 10	support for the already-interested	social proof, secondary features, awards	treating these as equal in weight

Our guide to optimising an App Store and Google Play listing covers where screenshots sit against the rest of the listing’s conversion levers.

How many screenshots does the App Store actually show before a tap?

The App Store actually shows three screenshots on a portrait set, and one if your first asset is landscape, which is the point AppAgent’s study makes bluntly: with landscape images you get one shot. For any game or landscape-first app that detail costs more than any creative decision, because it cuts the visible space by two thirds before a designer opens a file.

Scroll behaviour past that point is the part that changes planning. In AppAgent’s 2017 study of five apps, covering more than 25,000 store-listing visitors and about 10,000 installs, the average visit lasted roughly seven seconds, 13% of visitors scrolled through the screenshots and 3% enlarged one.

Two caveats belong with those numbers. The study is a vendor publication of five apps rather than a platform disclosure, and Phiture published it in August 2017, so read the levels as directional. The ranking it produces, that scroll rates sit in single digits to low teens, is consistent with every practitioner account since.

The planning consequence holds either way. Build three screenshots as if they were the whole set, then add the rest for the minority already leaning toward installing. Our piece on why an app gets no downloads covers the case where the problem is upstream of the listing entirely.

What should the first screenshot say?

The first screenshot should state the outcome in under seven words and show a real screen behind it. A visitor who reads only that one frame should be able to say what the app does and who it is for, which is a higher bar than most first frames clear.

Write the caption as a benefit, not a feature name. “Track every subscription in one place” works where “Subscription dashboard” does not, because the first describes a result and the second describes a noun the visitor has no context for.

Keep the text large enough to read at thumbnail size. Search results render these images small, and a caption sized for a design review is often unreadable at the size the decision is actually made. Test it by shrinking the export to the width of a search result and reading it at arm’s length.

Avoid two common first-frame mistakes. A pure marketing panel with no product visible reads as an advert and gives the visitor nothing to evaluate, and a bare unannotated screen asks them to infer the value themselves. The device frame with one short caption above it is the convention because it does both jobs at once.

What belongs in screenshots two and three?

Screenshot two should show the product doing the main job, and screenshot three should show the one thing a competitor cannot claim. The second frame answers “how does it work”, the third answers “why this one”.

For the second frame, pick the screen a happy user spends the most time on, not the most visually complex one. A dense dashboard looks impressive to the team that built it and looks like work to a stranger. Choose the screen that is easiest to understand at a glance and populate it with realistic content rather than placeholder text.

For the third frame, name the actual differentiator. Faster setup, works offline, no account needed, a data source nobody else has, a price structure that differs from the category: whatever the honest answer is when a user asks why not the market leader.

Running a competitor analysis across the top listings in your category is how you find out what everybody else is already claiming, so you do not spend your third frame repeating it.

Both frames should be legible without the first. A visitor arriving from a deep link or a paid campaign may see them in a different context, and a frame that only makes sense as part of a sequence loses its meaning.

If your acquisition and conversion path need to be built as one piece rather than handed to two separate teams, that is the work we take on in app launches end to end.

Do captions on screenshots help or get ignored?

Captions help conversion and do nothing for search ranking, and the distinction matters because teams keyword-stuff them hoping for both. Neither store indexes text inside an image, so a caption packed with search terms costs you clarity and buys no ranking.

What captions do is remove the inference step. A screen on its own requires the visitor to work out what they are looking at, and seven seconds is not enough time for that across three frames. One short line of text per frame does the interpreting for them.

Keep each caption to a single idea and a single line. Two-line captions at search-result size become texture rather than text, and a frame carrying two ideas usually communicates neither.

Localise the captions rather than translating them. Apple allows a separate screenshot set per localisation, which means the caption can be rewritten for the market rather than rendered word for word, and the phrasing a market actually uses converts better than a faithful translation of yours. Our comparison of ASO on the App Store and Google Play covers what each store indexes and what it does not.

How do you test a screenshot set rather than guess?

Test with the stores’ own tools, because both run the experiment on live store traffic rather than a simulation. Per Apple’s App Store Connect documentation, product page optimization runs up to three treatments against your default page for up to 90 days, lets you set what share of traffic the test receives, and can vary the app icon, screenshots and app previews.

Two limits on Apple’s tool are worth knowing before you plan around it. Treatments are alternate versions of your default page and you can change only those three asset types, and the test runs on the default product page rather than on custom product pages.

Per the same Apple documentation, a test set to 30% traffic with three treatments gives each treatment 10% of total traffic, so a low-traffic app will need the full 90 days.

On Android, Google Play store listing experiments work the same way with up to three variants against the control. Both platforms test the screenshot set as a unit rather than individual frames, so design treatments as whole alternative arguments rather than as one-frame swaps.

Test a bold change first. A new first frame with a different claim will produce a readable result where a font-weight change will not, because a small lift needs far more traffic to confirm than a large one. Our guide to how many ad creatives to test per month applies the same logic to paid social, where the volume maths is more forgiving.

How is the screenshot set different on Google Play?

Google Play accepts fewer screenshots and shows fewer of them, so the first frame carries even more weight there. Per ASOMobile’s 2026 requirements guide, Google Play takes up to eight screenshots per device type against Apple’s ten per localisation.

The export sizes differ enough that one file will not serve both. The two stores specify different dimensions, so the same creative needs two renders. Plan that into the design brief rather than discovering it at upload.

Play also puts a feature graphic and an optional promo video above the screenshot row, which changes what the first frame is competing with. On a listing with a video, many visitors watch rather than scroll, so the video’s opening seconds become the first screenshot in practice.

Keep the concept shared and the assets separate. One creative argument, two export sets, two upload workflows, and separate test cycles because the two stores’ experiment tools report differently. Our piece on ASO for a new app with no reviews covers what to prioritise on both stores before you have social proof to work with.

The short version

Three frames do the work. App Store search results show up to three portrait screenshots without a tap and one if your first asset is landscape, per AppFollow’s 2026 guidance, so the value proposition, the product in use and your single differentiator all have to land inside them.

Assume nobody scrolls. Per AppAgent’s 2017 study of five apps and more than 25,000 store-listing visitors, the average visit lasted about seven seconds, 13% of visitors scrolled through the screenshots and 3% enlarged one.

Then test rather than argue. Apple’s product page optimization runs up to three treatments against your default page for up to 90 days on icon, screenshots and previews, and Google Play store listing experiments run up to three variants against the control, with both testing the set as a whole.

One limit on the numbers above: the scroll and dwell figures come from a single vendor study published in 2017, so treat them as directional, and measure your own listing’s conversion rate before and after any change.