App Store Screenshot Best Practices

What Apple actually says

Apple's product page guidance is short, and four sentences of it decide most screenshot decisions. Quoted rather than paraphrased, because the wording matters:

The first three carry the page

Apple's own sentence draws the line: the first one to three images are what appear in search results. Everything from slide four onward is seen only by someone who already tapped through to your product page and then swiped.

That changes the budget. If you have limited time, spend it on slides one to three and accept that the rest are supporting material. The common failure is the reverse — a beautiful slide six that nobody ever reaches, and a slide one that says "Welcome".

There is a second clause worth noticing: "when no app preview is available". If you ship an app preview video, it takes the search-results slot and your screenshots stop appearing there at all. That is a reason to decide between the two deliberately rather than doing both badly.

Readable at thumbnail size

A screenshot in search results renders at a fraction of its 2868-pixel height. Headline text that reads comfortably in your design tool frequently disappears there. The test is mechanical, not aesthetic:

1. Export the slide at full resolution.
2. Scale it down to roughly 150 pixels wide — about what a search result shows.
3. Look at it at arm's length. If you cannot read the headline, it is too long or too small.
4. Cut words rather than shrinking type. Four or five words survive this test; twelve do not.
5. Repeat for your darkest and lightest slides — contrast that works on white often fails on a coloured background.

A six-slide structure

This next part is ShotQuill's framework, not Apple guidance — worth saying plainly, since the section above was quoting Apple. It is the structure the product generates against, and it exists because "focus each screenshot on a main benefit" does not tell you which benefits or in what order.

The ordering logic: hook and result go first because Apple tells you the first images appear in search. Pain goes fourth rather than first — leading with the problem works in long-form copy where the reader has committed, but a search result has no such commitment. Trust and CTA sit last because they only matter to someone already considering the download.

Common mistakes

• A first slide that says "Welcome" or shows your onboarding screen. It occupies the only slot most people ever see.
• Headlines written at design-tool scale that vanish at search-result scale.
• Six slides that each restate the same benefit in different words — Apple asks for a main benefit per screenshot precisely to avoid this.
• Abstract backgrounds with no app UI. Apple asks for images captured from your app's interface.
• Shipping an app preview and assuming screenshots still show in search. They do not.
• Uploading the same set to every localization with untranslated headline text. The screenshot is localizable; use it.
• Building all ten because ten is allowed. Slides seven through ten are almost never reached.

Measure it rather than trusting a benchmark

You will find a lot of numbers online claiming a specific conversion lift from better screenshots. This guide does not quote any of them, because none traced back to a verifiable primary source when checked.

You do not need an industry average anyway. Apple's Product Page Optimization runs A/B tests on your own product page, against your own traffic, and reports the result. One test on your app is worth more than any benchmark from someone else's.

Practical approach: ship the six-slide set, then use Product Page Optimization to test the first slide alone. It is the one with the most traffic and the clearest attribution.

Questions