App Store Screenshot Best Practices: 12 Rules That Lift Downloads
Twelve rules that separate screenshots people scroll past from screenshots that get the download.
Updated:
Most people never read your description. They look at your icon, your name and your first few screenshots, then decide. That makes screenshots the highest-leverage asset on your product page. These twelve rules come from what top-ranked apps have in common and from what the stores themselves require.
The first three screenshots
1. Treat the first three as an ad
In App Store search results, people see your first three portrait screenshots next to your icon. On Google Play the first few show in the listing and in some search layouts. These slots decide whether anyone opens your page, so they must explain the app on their own, even without the rest.
2. Lead with the outcome, not the feature
"Save 3 hours a week" sells; "Smart automation" doesn't. Start with what changes for the user, then show the feature that makes it happen.
3. One idea per screenshot
A screenshot that tries to show four features shows none. Pick one benefit, one headline and one screen. If a feature needs explaining, it probably belongs further down the set.
Headlines and design
4. Keep headlines under six words
Screenshots are often seen as small thumbnails. Short headlines in a large, heavy font stay readable at that size. If you need a second line, make it smaller and lighter so the hierarchy is clear.
5. High contrast, few colours
Pick a background that makes both the headline and the device stand out. Two or three colours from your brand are enough. Check your set in dark mode on a phone: the App Store follows the system theme, and a pale background can look very different next to dark UI.
6. Show the real app
Apple's App Review Guidelines ask that screenshots show the app in use, not only title art, a splash screen or a login page. Real screens also build trust: people want to see what they will actually get.
7. Be consistent across the set
Same font, same headline position, same device frame, same spacing. Consistency reads as quality. A template is the simplest way to keep it, because the layout is fixed and you only change the content.
Persuasion
8. Add proof, honestly
Ratings, number of users, awards or press quotes reduce risk for a new user. Use them only if they are true and current. Outdated or invented claims can get your app rejected and hurt trust.
9. Use your keywords in captions
Captions don't replace the keyword field, but they confirm to the visitor that your app matches what they searched for. Some ASO practitioners also believe Apple reads text in screenshots; Apple hasn't confirmed this, so treat it as a bonus, not a strategy. Our keywords guide covers the fields that do count.
10. Avoid things that date quickly
Prices, "new" badges, holiday themes and version numbers age fast and force you to redo the set. If you run a seasonal campaign, plan to switch back when it ends.
Reach and testing
11. Localise for your biggest markets
Translating headlines is one of the cheapest ways to grow downloads outside English-speaking countries. Start with the languages where you already see traffic. Read the localisation guide for a step-by-step approach.
12. Test one change at a time
Apple's Product Page Optimization and Google Play's store listing experiments let you split traffic between versions of your screenshots. Change one variable, such as the first screenshot or the background colour, run the test until it has enough data, and keep the winner.
A checklist before you upload
- The first screenshot explains the app on its own.
- Every headline is six words or fewer and readable as a thumbnail.
- Every screenshot shows a real screen of the app.
- Sizes and formats match the store requirements.
- No transparent PNGs, no mixed orientations.
- Claims and numbers are true today.
- Headlines are translated for your main markets.
StoreAppScreens is built around these rules: templates with large readable headlines, real device frames, one design exported to every size, and headlines you can translate into 39 languages in a click.