App Store Screenshots: The Conversion Guide
Quick answer: App store screenshots are the single biggest conversion lever on a listing — most users decide whether to install from the first two or three. Lead each one with a clear benefit caption over a focused visual, design for the portrait gallery, A/B test them, and localize them. On iOS, screenshot caption text is now also indexed via OCR (since 2025), so strong captions help both conversion and keyword relevance.
Last updated: June 2026.
You can rank #1 and still lose the install. Once a user reaches your product page, your screenshots do most of the convincing — and unlike keywords, their impact is immediate and measurable. This guide covers what makes screenshots convert, how many you actually need, why captions now matter twice on iOS, and how to test them without guessing. It pairs with the broader App Store Optimization guide.
Why screenshots are the #1 conversion lever
Keywords decide whether you're seen; screenshots decide whether you're chosen. Improving conversion is a multiplier on every install source you have — a listing that converts at 3% instead of 2% gets 50% more installs from the same traffic and the same ad spend. No other single asset moves conversion as much as the screenshot gallery.
The first two or three screenshots are (almost) everything
In search results and on the product page, most users only see the first two or three screenshots before deciding or scrolling on. So:
- Front-load your strongest value. Your single best benefit goes on screenshot one. Don't save it for slide five.
- Make each of the first three a complete argument. Assume the user sees nothing else.
- Order by priority, not by app flow. This isn't a tutorial; it's a pitch.
Anatomy of a high-converting screenshot
Most effective store screenshots are not raw UI captures. They're designed panels with three parts:
- A short benefit caption — the headline. Outcome-focused ("Track every habit in one tap"), not feature-focused ("Habit list view").
- A focused visual — a clean, often-framed slice of the UI that supports the caption. One idea per screenshot.
- Visual consistency — shared colors, type, and rhythm across the set so the gallery reads as one designed story.
Raw, caption-less screenshots almost always underperform designed ones, because they make the user do the work of figuring out why they should care.
Preview how your listing — screenshots included — looks before you ship.
Format, count, and order
- Portrait dominates. Most apps should ship portrait screenshots; they show more of the gallery in results. Use landscape only if your app is genuinely landscape-first (some games).
- Quality over count. Both stores allow up to ~10 (iOS up to 10 per localization; Google Play 8). You rarely need all of them — three to six excellent ones beat ten mediocre ones.
- Order = priority. Best benefit first, then descending. Revisit the order as you learn what converts.
On iOS, captions now do double duty
A 2025 change made screenshots matter for rankings, not just conversion: Apple appears to have begun indexing the visible caption text on screenshots via OCR (widely reported through ranking-anomaly data — see what changed in ASO for 2026). Practically:
- Put real, relevant keywords into your captions — naturally, as part of a benefit line.
- Keep them readable first. You're writing for a human deciding whether to install; the keyword value is a bonus, not a license to stuff text.
This makes the screenshot the rare asset that drives conversion and (now, on iOS) keyword relevance — so it deserves more attention than the once-and-forget treatment most teams give it.
Don't guess — A/B test
Screenshots are the highest-value thing to test, and both stores support it:
- Apple Product Page Optimization — test up to three screenshot/icon/preview variants against your default.
- Google Play Store Listing Experiments — test screenshots (and other creative) on your main or custom store listings.
Change one variable at a time and let each test reach statistical significance before you call it. Full mechanics are in app store A/B testing.
Localize your screenshots
Screenshots are part of localization, not separate from it. A market with translated text but English screenshots is half-localized — and on iOS you'd be missing the now-indexed local caption keywords. Translate the captions natively for each market you target (see app localization).
A note on the preview video
Both stores autoplay a preview video when present. A strong one lifts conversion; a weak or slow one can hurt it (users bounce before it lands). If you ship one, lead with the payoff in the first few seconds and make sure the still frame works on its own.
Common screenshot mistakes
- Burying the best benefit past the first two or three slides.
- Raw UI captures with no captions — they make the user do the convincing.
- Inconsistent design across the set, so it reads as a random pile.
- Landscape for a portrait-first app, shrinking what shows in results.
- English screenshots in localized markets — half-localized, and missing indexed local captions on iOS.
- Never testing. Screenshots are the highest-leverage thing to A/B test; guessing is the expensive option.
Frequently asked questions
How many screenshots should an app have?
Quality over count: three to six excellent, benefit-led screenshots typically beat the maximum of mediocre ones. iOS allows up to 10 per localization and Google Play up to 8, but the first two or three do most of the work, so invest there first.
Do screenshots affect App Store rankings?
Indirectly and — new on iOS — directly. Indirectly, better screenshots lift conversion and install velocity, which feed rankings. Directly, since 2025 Apple appears to index screenshot caption text via OCR, so relevant captions can influence which keywords you rank for. Keep captions benefit-led and readable, with real keywords woven in naturally.
Should screenshots be portrait or landscape?
Portrait for most apps — it shows more of the gallery in search results and on the product page. Use landscape only if your app is genuinely landscape-first, such as some games. Match the orientation to how people actually hold the device while using your app.
How do I A/B test app screenshots?
Use Apple's Product Page Optimization (up to three variants) or Google Play's Store Listing Experiments. Test one variable at a time — a single new first screenshot, not a whole new set — and let the experiment reach statistical significance before deciding. See app store A/B testing for the full process.
What should the first screenshot say?
Your single strongest benefit, as a short outcome-focused caption over a clean supporting visual. Assume it's the only screenshot the user sees. Lead with the result they want ("Plan your week in 2 minutes"), not a feature label ("Calendar view").
