App Store Optimization

Screenshots

Also known asApp Store ScreenshotsPlay Store Screenshots

The images shown on your product page on the App Store and Google Play — the single biggest driver of browse-to-install conversion rate.

MWM data

State of April 2026

Median screenshot count

7

Half of apps have fewer, half more

Apps with 5+ screenshots

83.6%

Most apps use at least 5 — half of the available 10 slots

Apps with all 10 screenshots

31.1%

Apps that fully use both stores' 10-slot capacity

Apps with fewer than 3 screenshots

1.08%

Under-investing in product page conversion

Key takeaways

  1. 01Screenshots are the most important conversion surface — a user spends 7-10 seconds deciding, mostly on the first two visible screenshots.
  2. 02Real catalog data: median app ships 7 screenshots; 83% of apps use 5+; 31% use all 10 slots.
  3. 03Captioned benefit-focused screenshots outperform raw UI by 15-30% on install conversion.
  4. 04A/B testable: Google Play Store Experiments (native) and iOS Product Page Optimization (launched iOS 15).

Screenshots are the most important conversion surface in mobile app marketing. A user who clicks into your product page typically spends 7-10 seconds deciding whether to install. Most of that decision happens on the first two screenshots visible above the fold. Get those right and you lift CVR substantially; get them wrong and even great app-icon / great-reviews can't fully compensate.

Platform constraints

  • iOS: up to 10 screenshots, portrait OR landscape (one orientation per app), optionally with framed device shots, marketing copy overlaid, multiple per-locale variants.
  • Google Play: 2-8 screenshots required (8 maximum), portrait or landscape, no orientation restriction beyond per-asset choice.

Both stores support localized screenshots — different visuals + text per market.

Captioned screenshots dominate — overlay short benefit-focused headlines (5-7 words: "Track every workout", "Convert any document", "Find your match") on stylized backgrounds with the app UI inside a device frame. This pattern beats raw "here's what the app looks like" screenshots by 15-30% on install conversion consistently across categories. The screenshot becomes mini-marketing inventory, not just product photos.

A/B testing: Google Play Store Experiments tests screenshot sets natively — set up two variants, route traffic, measure install rate. iOS has Product Page Optimization (launched iOS 15) which lets you test up to 3 alternate "Treatments" against your default — same A/B testing capability, slightly different UI.

How to sequence your screenshots

Because most of the decision happens on the first two frames above the fold, screenshot order is a design problem, not an afterthought. The sequence strong apps converge on:

  1. Screenshot 1 — the hook. Your single strongest value proposition: one benefit headline, one clear visual. If a user reads only this frame, they should understand why the app matters. It does more conversion work than the other nine combined.
  2. Screenshot 2 — the second pillar. The other above-the-fold slot. Frames 1 and 2 together must tell the whole core story, because a large share of users never scroll past them.
  3. Screenshots 3-5 — differentiators. One specific benefit per frame (not feature dumps) — the things that set you apart from the category. Lead with benefit language, not UI tours.
  4. Screenshots 6+ — proof and depth. Social proof (ratings, awards, press), edge-case features, or a connected "panorama" payoff. Marginal conversion value drops sharply here — which is exactly why the catalog median sits at 7, not 10.

Common mistakes: leading with a raw UI shot instead of a benefit hook; cramming more than ~7 words of copy onto a frame; burying the value proposition past slot 2; and shipping ten near-identical frames. Localize the set for your top markets (localized screenshots lift conversion 20-40% in non-English markets) and A/B test the first two frames before touching anything else.

How many screenshots apps actually ship

Across the MWM catalog the median app ships 7 screenshots — not the full 10-slot maximum most ASO advice assumes. The distribution below, and the by-download-tier breakdown, show how screenshot count actually scales.

Screenshot count distribution across the catalogBoth iOS and Google Play allow up to 10 screenshots per app. Real-world usage clusters tightly: most apps use 5-10 screenshots, with full-10 being the modal cluster among high-volume apps.025K50K75K100K0: 11: 3352: 1,9943: 10,0014: 23,1995: 33,8756: 27,2987: 19,2738: 26,0309: 7,20910: 9,01511+: 58,441Full slate01234567891011+Number of screenshots
Screenshot count distribution across the catalog — Apps with ≥1,000 downloads in last 30 days, MWM catalog, State of April 2026.

Screenshot count by app download-volume tier

Download tier (30d)Median screenshotsMean screenshots
1K-10K downloads79.0
10K-100K downloads810.3
100K-1M downloads812.7
1M+ downloads1214.4

Higher-download tiers ship more screenshots on average — the biggest apps use the full slate — but even at scale the median sits below the maximum, leaving unused store real estate for most of the catalog.

Quick answers

How many screenshots should my app have?

Real catalog data: median app ships 7 screenshots, 83% of apps use 5+, 31% use all 10 slots, 1% have under 3. Both iOS and Google Play allow up to 10 (iOS) / 8 (Google Play). The marginal value of screenshots 6-10 is much lower than 1-5; most install conversion happens on the first two visible above the fold. Most apps converge on 5-8 high-quality screenshots.

Are captioned screenshots better than raw UI screenshots?

Yes — captioned benefit-focused screenshots beat raw UI by 15-30% on install conversion, consistently across categories. The pattern: stylized background + short benefit headline (5-7 words) + app UI in device frame. The screenshot becomes mini-marketing inventory, not just product photos. The premium A/B-tested layouts in 2026 are almost all captioned.

Can I A/B test my app store screenshots?

Yes on both platforms. **Google Play Store Experiments** tests screenshot sets natively — set up variants, route traffic, measure install rate. **iOS Product Page Optimization** (launched iOS 15) lets you test up to 3 alternate "Treatments" against your default product page. Both support per-locale targeting.

Should I localize my screenshots?

For markets where you've already localized the app text, yes — localized screenshots typically lift install conversion 20-40% over English-only screenshots in non-English markets. For markets you've only machine-translated, the marginal benefit is smaller. Best practice: localize screenshots for your top 3-5 markets, use translated-text overlay for the next tier, English-only for long-tail markets.

Back to glossary