Screenshots
Use screenshots to make the search promise obvious. A good set says what the app does, why it matters, and why this app is worth trying instead of the other apps on the page.
When to work on screenshots
- Low conversion: If taps do not turn into installs, the screenshots are usually the first place to look.
- Weak first impression: If the first screenshot does not explain the app in one glance, rewrite it before changing ten smaller things.
- Better competitors: If ranking apps show the benefit faster than you do, study their first three screenshots before redesigning yours.
Build the first three
Screenshot 1: the main promise
Put the strongest keyword or benefit here. The line should be short enough to read in search results.
Screenshot 2: the proof
Show the real screen where the user gets the result. Avoid pretty layouts that hide the actual product.
Screenshot 3: the reason to believe
Show a specific outcome, comparison, saved time, revenue signal, review, or feature that makes the promise feel real.
Keep the rest useful
Use later screenshots for secondary features, social proof, pricing clarity, integrations, or advanced use cases. Do not use them as decoration.
Use competitors first
- Open Competitors: Search the app that already ranks for your target keyword.
- Compare the first screen: Write down the promise, visual style, and proof they show before the user swipes.
- Find the gap: Your screenshot should make a clearer promise, show a cleaner result, or answer a concern the current winners ignore.
Caption rules
- Use 3 to 7 words: Short captions are easier to read on a phone and easier to translate later.
- Use real keywords: Reinforce the same search intent you are targeting in the name, subtitle, and ads.
- Keep contrast high: If the caption is hard to read in a small preview, users will skip it.
- One idea per screenshot: Do not turn every screenshot into a list. One clear promise beats five tiny claims.
Test in App Store Connect
When you have enough traffic, test screenshots with Product Page Optimization. Change one thing at a time so you know what moved conversion.
- Write down the current baseline: If you are not running Apple Ads, use App Store Connect to check the current product page conversion rate before changing screenshots.
- Start with the first screenshot: It carries the most weight because many users never swipe.
- Wait for signal: Do not call the test after one good day. Let the result settle before applying it.
- Watch paid and organic: If you run Apple Ads, check whether better screenshots improve tap-through and install conversion together.
Measure before and after
Without Apple Ads, App Store Connect is your measurement loop. Note the current product page conversion rate, ship the screenshot change, then compare the same metric after enough traffic comes through.
Common misses
- Too much UI: The user sees a busy app screen but does not understand the benefit.
- Too much copy: The screenshot becomes a poster. Keep the promise short and let the product show the rest.
- No local version: If the store page is localized, the screenshot captions should be localized too.