What makes an app store screenshot "good"
A good app store screenshot isn't one that looks polished in isolation. It's one that gets someone who is scrolling past dozens of other apps to stop, understand what your app does in about a second, and tap through to install it.
That's the only measure that matters: tap-through rate from the store listing. Plenty of screenshot sets look professional and still convert poorly, because they're beautiful without being clear, or clear without being in the right order. This guide covers how to make good app store screenshots that actually do their job — the principles, the order, the copy, and the current technical specs — independent of whatever tool you end up using to build them.
The first screenshot is the only one that matters most
Most people browsing an app store see your first screenshot before they see anything else — often before they read your title or description closely. On a search results page or a category listing, it may be the only visual they see at all.
That means your first screenshot has to do the heaviest lifting:
- State the core benefit in one short line, not a feature list
- Show the app's main value, not a settings screen or an onboarding step
- Avoid clutter — one clear message, one focal point
- Be legible at a thumbnail size, not just full screen
If someone doesn't understand what your app does from the first screenshot alone, they usually won't swipe to the second one to find out.
How many screenshots to show, and in what order
Most store listings allow several screenshots, but attention drops fast after the first few. Treat your set as a short narrative, not a gallery:
- First screenshot — the core benefit, stated plainly
- Second and third — the next most important features or outcomes, each with its own single idea
- Remaining screenshots — secondary features, social proof, or supporting detail for people who are already convinced and want more
Order by importance, not by the order features exist in your app. A feature that's technically impressive but not what users care about most should sit later in the set, not first.
Within each screenshot, keep the same discipline: one idea per screen. A screenshot trying to communicate three things usually communicates none of them clearly.
Design principles for screenshots that convert
A few rules do most of the work:
- Hierarchy. The eye should know where to land first — usually a headline, then the device image, then any smaller supporting text. If everything is the same size and weight, nothing stands out.
- Contrast. Text needs to be readable against its background at a glance. Light text on a busy photo background is a common failure point.
- Caption length. Short wins. A caption someone has to pause and re-read is a caption that loses them before they scroll on.
- Device frame vs. full-bleed. A device mockup (phone or tablet frame around the screenshot) gives context and looks native to an app store listing. A full-bleed image — the screenshot filling the whole canvas with no frame — can feel more immersive but loses the visual cue that this is an app. Framed screenshots tend to read faster; full-bleed can work well for lifestyle or photo-heavy apps where the image itself is the sell.
- Consistency across the set. Same fonts, same color palette, same caption style, same device frame (or deliberately none) across every screenshot. Inconsistency reads as unfinished, even if each individual screenshot looks fine.
Real screenshots or stylized mockups?
You generally choose between two approaches:
- Raw UI screenshots — honest, but can look cluttered, inconsistent, and hard to parse out of context.
- Stylized screenshots — the real UI placed inside a device mockup with a headline, background, and consistent branding layered on top.
Stylized screenshots almost always perform better, because they add the hierarchy and messaging a raw screenshot can't provide on its own. This is the gap a tool like AppShots is built for — taking a raw iOS or Android screenshot and turning it into a store-ready visual with a device mockup, headline, and consistent layout, without needing Photoshop or Figma to do it by hand.
Writing captions that sell, not describe
The most common caption mistake is describing a feature instead of selling the outcome. Compare:
Weak: "Push notifications" Strong: "Never miss what matters"
Weak: "Dark mode available" Strong: "Easy on your eyes, day or night"
Weak: "Cloud sync" Strong: "Your data, everywhere you go"
The pattern: lead with what the user gets, not the mechanism behind it. Save the feature name for the app description, where people are already reading in detail — the screenshot caption is a headline, not a spec sheet.
Current size and format specs for Apple and Google
Both Apple App Store Connect and Google Play Console require screenshots at specific pixel dimensions, and those requirements vary by device type (iPhone, iPad, Android phone, Android tablet) and get updated as new device sizes ship.
Because these specs are set directly by Apple and Google and change over time, the safest approach is to check the current required sizes in App Store Connect and Google Play Console at the time you upload — rather than relying on a number that may be out of date by the time you read it. A screenshot tool that exports pre-sized for current store requirements removes the guesswork, which is one of the reasons most teams don't build these dimensions by hand.
What stays constant across both platforms, regardless of the exact pixel count in a given year:
- Each device type needs its own correctly sized export — a phone screenshot resized to fit a tablet slot usually looks stretched or cropped
- Formats are typically flat image files, not layered design files
- Both stores allow multiple screenshots per device type, with the first one carrying the most weight
Common mistakes that hurt conversion
- Text too small to read at thumbnail size. If you can't read the caption when the image is shrunk down, neither can a browsing user.
- No human or real-world context. A pure UI screenshot with no framing can look abstract. A device mockup, or a glimpse of how the app fits into someone's day, helps people picture using it.
- Inconsistent branding across the set. Mixing fonts, colors, or layouts screenshot to screenshot makes the set look unplanned.
- Ignoring localization. A screenshot set written only in one language misses users browsing the store in another. Captions, and sometimes the UI shown, should be adapted per locale rather than translated as an afterthought.
- Outdated specs. Submitting screenshots sized for an old device lineup can mean rejected uploads or screenshots that display incorrectly. Checking current requirements before each submission avoids this.
How to test and improve your screenshots
Screenshots aren't a one-time task. Both major stores offer native ways to test variations against each other:
- Apple's Product Page Optimization lets you run alternate screenshot sets against your current one and see which drives more installs from your existing traffic.
- Google Play's Store Listing Experiments does the same for Android listings, letting you compare screenshot variants directly.
What to measure: tap-through to your app's page, and conversion from page view to install. Run a test long enough to collect a meaningful amount of traffic before drawing conclusions — a test cut short on too few visits can point you in the wrong direction. When one variant clearly outperforms, make it the default and start testing the next hypothesis — a different first screenshot, a shorter caption, a different device frame.
FAQ
Do I need a professional designer to make good app store screenshots? Not necessarily. The principles above — hierarchy, one idea per screen, benefit-led captions, consistency — matter more than design skill with layout software. A tool built specifically for app store screenshots, like AppShots, applies a lot of this structure for you through templates and layouts, which is why many teams skip hiring a designer for this specific task.
Do screenshots affect my app's search ranking, or just conversion? Screenshots influence whether someone who already sees your listing decides to tap through and install — that's conversion. They don't control how a store's search algorithm ranks your app, and no tool or guide can set that ranking for you. Better screenshots can improve the results you get from the traffic you already have, which is a different thing from improving your position in search.
How often should I update my screenshots? That depends on what's changed — a redesign, a new headline feature, a seasonal promotion, or results from an A/B test that point to a better variant. There's no fixed interval; treat it as ongoing rather than a one-time setup task.
Do I really need localized screenshots for every market? If you're targeting users who browse the store in a language other than your primary one, localized captions (and sometimes localized UI in the screenshots themselves) typically perform better than a single set translated after the fact. Whether it's worth the effort depends on how much of your install volume comes from those markets.