Blog
App Store screenshot best practices: how to design screenshots that convert (2026)
You can nail every dimension the stores ask for and still lose the install. Sizes and specs get your screenshots accepted; design is what gets them tapped. Most people decide whether to download your app after glancing at the first couple of screenshots - before they read a word of your description. This guide covers the App Store and Google Play screenshot best practices that actually move conversion: what to show, what to say, and the small choices that separate a set that sells from one that just fills the slots.
Why screenshots decide installs
Your screenshots are the largest, most prominent asset on your store listing, and they do their work in the search results and browse feed - often before anyone taps through to your product page. A user scrolling the App Store sees your icon, your name, and a thumbnail strip of screenshots. That strip is your pitch. If it lands, they tap; if it doesn't, they scroll past and you never get a second chance.
This is why screenshots reward design effort more than almost anything else in your listing. A better icon helps you get noticed; better screenshots are what turn that attention into a download. And because the stores rank partly on conversion rate, screenshots that convert also help you rank - a compounding return on the time you put in.
The first two screenshots are the whole game
On both the App Store and Google Play, the first two to three screenshots are visible without scrolling or swiping. Treat them as if they are the only ones most people will see, because for most people they are. Put your single strongest reason to install in the first frame, your second-strongest in the second, and don't save your best material for a screen nobody swipes to.
A useful test: if a stranger saw only your first screenshot for one second, would they understand what your app does and why they'd want it? If not, rework it before you touch anything else.
App Store screenshot best practices
1. Lead with the outcome, not your home screen
The most common mistake is opening with a raw screen capture of the app's landing view. It's honest, but it's not persuasive - it shows the tool, not the payoff. Lead instead with the outcome your app delivers: the completed workout, the organized inbox, the finished design, the money saved. Show people the result they want and the app becomes the obvious way to get it.
2. Write captions that sell benefits, not features
Every strong screenshot set pairs each screen with a short marketing caption, and the best captions describe a benefit rather than name a feature. "Track every workout automatically" beats "Activity dashboard." Keep captions to a few words - they're read in a glance, at thumbnail size, often one-handed on a train. Lead with a verb, cut adjectives, and make sure each caption could stand alone as a reason to install.
3. Give every screen a clear visual hierarchy
Caption first, then the app UI. The caption is usually the headline, so it should be the first thing the eye lands on - large, high-contrast, comfortably away from the device. Below or beside it, the device frame carries the actual screenshot. When the caption and the UI fight for attention, both lose. A consistent layout - caption band on top, framed device below - reads instantly and lets people move down the set quickly.
4. Keep the whole set visually consistent
Screenshots are viewed as a strip, not in isolation, so consistency is what makes the set feel like a designed product rather than a pile of exports. Use the same background treatment, the same caption typography and position, the same device frame and the same amount of tilt across every screen. Vary the content; keep the container fixed. A consistent set also signals a polished app - people read production quality on the store page as a proxy for quality inside.
5. Show real UI inside a device frame
Framing your captures in a real device puts the UI in context and makes the app feel tangible - it reads as "this is what you'll actually be holding" rather than a floating rectangle. Match the frame to the platform (a Pixel-style frame on Google Play, an iPhone frame on the App Store) and keep the frame consistent across the set. Real UI beats mockup filler, too: show your actual screens with real-looking content, not lorem ipsum and grey placeholder blocks.
6. Design for the thumbnail, then check it small
Your screenshots will be seen small far more often than large. A caption that's perfectly legible in your editor can turn to mush in the search results. Before you ship, shrink the set to thumbnail size and squint: is the caption still readable, is the hero element still obvious, does the first frame still land in one second? Big type, high contrast, and one idea per screen are what survive the shrink.
7. Localize the set for your key markets
A screenshot in the user's own language, showing localized UI, converts markedly better than an English default - and localizing is far less work than it sounds once you treat each language as a small override rather than a rebuild. If you sell in more than one market, this is among the highest-leverage moves available. We wrote a full walkthrough in how to localize App Store screenshots.
Portrait or landscape?
For the vast majority of apps, portrait screenshots are the right default: they match how the store displays phone listings and how people hold their phones. Reach for landscape only when your app genuinely lives sideways - games, video editors, some drawing tools - where a landscape hero shot shows the experience honestly. The stores accept both, but a landscape screenshot in a portrait listing shows smaller in the strip, so don't choose it for style alone.
Stop guessing - A/B test your screenshots
Even seasoned designers are wrong about which screenshot converts best more often than they'd like to admit. Both stores give you the tools to find out for real: Google Play's Store Listing Experiments and Apple's Product Page Optimization let you run live tests against real traffic. Test one variable at a time - a different first screen, a rewritten lead caption, a new background - so you learn why a version won, not just that it did. Then feed the winner back into the rest of the set. Your first design is a hypothesis, not a conclusion.
Common mistakes to avoid
- Burying the lead. Saving your best screen for slot four, where most people never swipe. Front-load your strongest material.
- Naming features instead of selling benefits. "Settings screen" tells a user nothing. "Set it once, forget it forever" tells them why to care.
- Captions too long to read at a glance. If it doesn't fit in a quick look at thumbnail size, it's too long.
- An inconsistent set. A different font, background, or frame on every screen reads as unfinished, not varied.
- Low contrast. Pale caption text on a busy background disappears the moment the image is scaled down.
- Placeholder content. Empty states and dummy data make the app look empty. Show it full and in use.
- Ignoring the platform. An iPhone frame on a Google Play listing looks careless. Match the device to the store.
Frequently asked questions
How many screenshots should I upload?
Upload the maximum the store allows (up to ten on both the App Store and Google Play) so you fill the strip, but put your effort into the first two or three - those carry almost all of the conversion. Later screens support the sale; they rarely make it on their own.
Should I put captions on my App Store screenshots?
For most apps, yes. A short benefit-led caption on each screen consistently outperforms a bare UI capture, because it tells the user what they're looking at and why it matters before they have to work it out themselves. The main exception is apps whose value is purely visual - some games and photo tools - where the imagery speaks for itself.
Do App Store and Google Play screenshots need different designs?
The design principles are identical, but keep two things platform-appropriate: use the matching device frame (iPhone vs. Pixel-style), and produce each store's required sizes. You can share one base design across both and export the right dimensions for each - see our guide to App Store and Google Play screenshot sizes and specs for the exact numbers.
What makes an App Store screenshot convert?
One clear idea per screen, a benefit-led caption people can read in a glance, your strongest material in the first frame, a consistent look across the set, and real UI shown in a device frame - all of it still legible at thumbnail size. Then A/B test to confirm what actually wins with your audience.
Put it together
Great App Store screenshots aren't an art project - they're a short, ordered argument for why someone should install your app. Lead with the outcome, sell benefits in a few words, keep the set consistent, show real UI in a frame, design for the thumbnail, localize your key markets, and let A/B tests settle the rest. Get the first two screens right and you've done most of the work.