By Mehdi HassanHow do you design app store screenshots that increase downloads?
You design app store screenshots that increase downloads by writing them like a landing page: a clear promise in the first frame, proof in the next few, and nothing that needs explaining. Most people decide from the search result or the top of the product page, so the first frames have to work as a complete pitch at thumbnail size.
That's why we start with the words. A screenshot set is a headline, a sequence of benefits and a visual for each one, which is the same structure as a good landing page compressed into a horizontal strip. Teams that start with a template and a stack of interface screens end up with a tour of the app. Teams that start with the captions end up with a reason to download. For the rest of the store listing and launch, see our mobile app design guide.
What should the first app store screenshot say?
The first screenshot should say what the user gets, in one short line they'd use themselves, next to the screen that delivers it. It plays the role of a landing page headline: if someone reads only that frame, they should know what the app does for them and why it's different.
Weak caption | Stronger caption | Why it works |
|---|---|---|
AI-powered budgeting | See where your money went this month | Outcome, not technology |
Advanced scheduling features | Book a class in two taps | Specific action and effort |
The all-in-one fitness app | Workouts that fit 20 free minutes | A concrete situation the reader recognizes |
Welcome to Acme | Turn receipts into expense reports automatically | Says the job; the app name is already on the listing |
Keep captions to a few words per line, large enough to read on a phone in search results. If you need a sentence to explain the frame, the frame is doing too much. The same rules that make a homepage redesign work apply here: lead with the outcome and let the screen supply the proof.
How should you sequence app store screenshots?
Sequence app store screenshots in the order a skeptical user's questions arrive: what is it, does it do the thing I need, how hard is it, and can I trust it. Put the strongest benefit first, the core screen second, and save settings, integrations and secondary features for the end, where only interested readers swipe.
Frame 1: the promise
The headline benefit plus the screen that delivers it. This frame should work alone in search results.
Frame 2: the core moment
The value event: the plan generated, the booking confirmed, the report done. Show the result, not the menu.
Frames 3 to 5: one benefit each
Each frame answers one objection or adds one reason, in the order most users care about them.
Frame 6: proof or trust
Security, privacy, integrations or a well-known partner, if you can say it honestly. Avoid unverifiable claims.
Remaining frames: depth for the curious
Widgets, customization, dark mode, accessibility. Useful for people already convinced, invisible to the rest.
Both stores cap how many screenshots a listing can show, and the limits change, so check each store's current requirements. You don't have to fill every slot. A tight set of five that each earn their place reads better than ten that repeat themselves.
What makes good app store screenshot design, frame by frame?
Design each frame around one focal point: the part of the real interface that proves the caption. Crop in, zoom on the key element, or place the screen inside a simple device outline with the caption above it. Everything must be readable when the screenshot is a small thumbnail in a list.
- Use real screens with realistic content. Fill them with believable data, not lorem ipsum or obvious placeholders.
- Keep one visual system across all frames: same caption position, type, background and device framing, so the set reads as one story.
- Use your brand color for backgrounds, and make sure it contrasts with your app icon and the store's light and dark modes.
- Highlight, don't decorate. A zoomed element or a subtle callout beats arrows, badges and stickers.
- Make the strip continuous if you like, with backgrounds that flow across frames, but each frame must still stand alone.
Your app icon sits right next to these frames in search results, so design them together. Our guide to app icon design covers turning a logo into an icon that holds up at small sizes.
How do iOS and Google Play screenshots differ?
The App Store and Google Play use screenshots in similar ways, but Google Play adds a feature graphic shown in some placements and handles promotional video through a YouTube link, while the App Store uses app previews: short videos that autoplay at the start of your screenshot set. Check Apple's current limit on how many previews each localization can include.
Design one caption system and adapt it to both stores rather than making two unrelated sets. Show iOS screens on the App Store and Android screens on Google Play, because users notice when a listing shows the other platform's controls. Our comparison of iOS vs Android design lists which components should look different. Always check each store's current size and format requirements in its developer documentation before exporting, since they change with new devices.
For example, suppose you're writing screenshots for a receipt-scanning expense app
For example, suppose a small team has an expense app that scans receipts and builds reports. Their current set shows the camera, a list, a settings screen and a chart, captioned Scan, Expenses, Settings and Insights.
A copy-first rewrite might be: Frame 1, "Snap a receipt. The report writes itself," over a scan turning into a line item. Frame 2, "Expense reports ready in one tap," over a finished report. Frame 3, "Every card and currency in one list." Frame 4, "Approvals your finance team will actually like." Frame 5, "Your data stays private," with a plain statement of what they do and don't share. Settings disappears entirely.
This is a hypothetical rewrite, not a measured result, but it shows the shift: from naming screens to stating outcomes.
Should you use an app preview video?
Use an app preview video when your app's value is easier to show in motion than in still frames: a gesture-led interaction, a transformation such as a photo edit, or a game. If your app is mostly forms and lists, strong static screenshots usually communicate faster.
If you make one, open with the core moment in the first seconds, since many viewers won't watch to the end, and make it understandable with sound off. Use real app footage; both stores' guidelines expect previews to show the actual app experience. Keep captions consistent with the static frames so the listing reads as one message.
How do you test app store screenshots?
Test app store screenshots with each store's built-in tools: product page optimization in App Store Connect and store listing experiments in the Google Play Console. Both split traffic between your current set and one or more variants and report which one converts more visitors to installs.
Test one big idea at a time, such as a different first caption or a result-first versus a screen-first opening frame, rather than small color tweaks. Give tests enough traffic to be meaningful, and remember that what wins for paid traffic may differ from organic search. Then carry the winning message to your website, so the app's landing page and listing say the same thing. If users download but drop off on the first screens, the problem is no longer the listing; look at mobile onboarding design.
