App Store conversion rate: benchmarks and how to improve yours
What counts as a good App Store conversion rate, where to find yours in App Store Connect, and the levers that actually move it — ranked by effort and impact.
"Is my conversion rate any good?" is the first question every developer asks after connecting analytics — and the answer is genuinely murky, because Apple's numbers are noisy and public benchmarks vary wildly by category. This post explains how to read your own numbers, what "good" roughly looks like, and which levers move the needle.
Where to find your conversion rate
In App Store Connect, open Analytics → Metrics and look at:
- Impressions — how many times your app appeared anywhere (search results, Today tab, charts).
- Product page views — how many people opened your full page.
- Total downloads (first-time downloads is the cleaner metric).
Your headline number is downloads ÷ impressions. But split it in two, because they're different funnels:
- Search results → download (most downloads happen here, straight from the results card)
- Product page view → download (people who tapped through and read more)
What "good" looks like
Apple doesn't publish official benchmarks, and third-party datasets (Appfigures, AppTweak, and Apple's own peer-group percentiles in App Store Connect) disagree on exact numbers. Rough shape of reality:
~2–5%
Typical impressions → download for browse-heavy traffic
20–40%
Common product page view → download range
50%+
Achievable on high-intent branded searches
Treat these as orientation, not targets. The genuinely useful benchmark is in App Store Connect itself: Analytics → Benchmarks compares your conversion against a peer group of similar apps in percentiles. If you're below the 50th percentile there, your product page — not your marketing — is the bottleneck.
The levers, ranked
Not all product-page elements pull equally. In rough order of impact for a typical indie app:
- Screenshots 1–3. The dominant visual element in both search results and the product page. If you change one thing, change these — here's how to design the trio.
- Icon. Decides whether your search result gets looked at, at all. See the icon design guide.
- Title + subtitle. Both keyword relevance and the pitch. "Budget tracker — see where money goes" outperforms "MoneyMaster Pro".
- Ratings. Below ~4.0 stars, everything else fights uphill. Prompt happy users with
SKStoreReviewControllerat moments of success. - Price framing. If you're paid or subscription, screenshots that are honest about pricing ("$4 once, no subscription") convert better and filter out future one-star reviews.
- App preview video. Helps some categories (games, visual tools), hurts others by replacing your first two screenshot slots. Test before committing — our preview video guide covers when they're worth it.
The improvement loop
- Read your split. Low search-results conversion but decent page conversion → your first three screenshots and icon are weak. Good search conversion but page visitors bounce → screenshots 4–10, description, and reviews are letting you down.
- Fix the obvious first. The ten most common screenshot mistakes are all visible from outside; you don't need data to find them, you need honesty.
- Then A/B test refinements. Apple's Product Page Optimization tests screenshot variants against each other on live traffic — the full guide is here. You need traffic for significance, which is why the obvious fixes come first.
A realistic expectation
Doubling a 15% page conversion to 30% is a common outcome of fixing genuinely weak screenshots. Going from 30% to 33% takes disciplined A/B testing. The further you are from good, the cheaper the wins — which is great news if you've never seriously worked on your screenshots.
If you want the honest outside read on where you stand: Screenshot Roast gives your current screenshots a conversion score out of 10 with named problems and prioritised fixes, and generates redesigned versions you can put straight into a PPO test. Free credits cover the first roasts.