Quick answer
App screenshots convert when the first two frames carry a clear headline, the strongest benefit comes first, every shot uses a consistent device frame and background, and the text is readable at thumbnail size. Bare, uncaptioned phone screens are the most common mistake — they make the user decode what they're seeing instead of telling them. The nine rules below cover ordering, headlines, framing, and contrast.
Why do most app screenshots fail to convert?
Here's the uncomfortable truth: most people decide whether to install your app in about three seconds, and they make that call mostly on your icon and your first two screenshots. They don't read your description. They glance at the carousel and either tap "Install" or keep scrolling.
So the question isn't "do my screenshots show the app?" It's "does someone glancing at the first two frames instantly understand why this app is worth their thumb-tap?"
Most screenshots fail that test because they're raw exports straight off the device — a bare phone screen with no headline, no context, no framing. The developer knows what the screen does. The stranger scrolling the store doesn't. A bare screenshot makes that stranger do the work of figuring it out, and most won't bother.
I learned this the slow way. My first app had five clean, honest screenshots of the actual UI and a conversion rate that embarrassed me. I added a one-line headline to each and reordered them so the best benefit came first. Same app, same screens, just framed and captioned — and the install rate moved enough that I now treat screenshots as the highest-leverage marketing asset an indie developer has. The nine rules below are what I wish someone had handed me then.
So the question isn't "do my screenshots show the app?" It's "does someone glancing at the first two frames instantly understand why this app is worth their thumb-tap?"
Most screenshots fail that test because they're raw exports straight off the device — a bare phone screen with no headline, no context, no framing. The developer knows what the screen does. The stranger scrolling the store doesn't. A bare screenshot makes that stranger do the work of figuring it out, and most won't bother.
I learned this the slow way. My first app had five clean, honest screenshots of the actual UI and a conversion rate that embarrassed me. I added a one-line headline to each and reordered them so the best benefit came first. Same app, same screens, just framed and captioned — and the install rate moved enough that I now treat screenshots as the highest-leverage marketing asset an indie developer has. The nine rules below are what I wish someone had handed me then.
Rule 1–3: Lead with a headline, order by strength, caption everything
Rule 1: Put a headline on every screenshot. Three to five words, large, in the top third of the frame. "Track every workout." "Split bills in seconds." "Your notes, finally organized." The headline does the selling; the screenshot proves it's real. Without the headline, the screenshot is just evidence with no claim attached.
Rule 2: Order by strength, not by app flow. Your screenshots are not a tutorial. Don't show the onboarding screen first just because it comes first in the app. Lead with your single most compelling benefit, then your second, then your third. The first two frames are the only ones most people see in search results, so your two best ideas go there — never your splash screen or login.
Rule 3: Caption all of them, not just the first. Once someone taps into the full listing, they swipe through the whole carousel. Every frame is a chance to land another reason to install. A captioned screenshot keeps making the case; a bare one makes them stop and decode. Keep the caption style identical across all frames — same font, same position, same size — so the set reads as one designed thing instead of eight random screens.
Rule 2: Order by strength, not by app flow. Your screenshots are not a tutorial. Don't show the onboarding screen first just because it comes first in the app. Lead with your single most compelling benefit, then your second, then your third. The first two frames are the only ones most people see in search results, so your two best ideas go there — never your splash screen or login.
Rule 3: Caption all of them, not just the first. Once someone taps into the full listing, they swipe through the whole carousel. Every frame is a chance to land another reason to install. A captioned screenshot keeps making the case; a bare one makes them stop and decode. Keep the caption style identical across all frames — same font, same position, same size — so the set reads as one designed thing instead of eight random screens.
Rule 4–6: Frame the device, stay consistent, mind the thumbnail
Rule 4: Put the screen inside a device frame. A screenshot floating on a colored background looks fine. A screenshot inside a real device frame — correct bezel, correct corners, a believable phone — looks like a product. The frame signals "this is a real, shipping app," and it gives the screenshot a consistent shape so a tall screen and a short screen still line up in the carousel. You can drop any screenshot into a real frame in the PlayMockUp studio and the bezel and corner radius are exact rather than faked.
Rule 5: One background, one frame, one type style — across all 8. Consistency is what separates a listing that looks designed from one that looks thrown together. Pick a background palette that matches your brand, pick one device frame, pick one caption style, and apply them to every screenshot. The eye reads a consistent set as trustworthy. A set where every frame has a different background reads as amateur, even when each individual shot is fine.
Rule 6: Design for the thumbnail, not the full size. Your screenshot will most often be seen small — in search results, in a category list, at maybe a third of full size. Open your design at thumbnail scale and check: can you still read the headline? Is the key UI element still visible? If the text turns to mush when shrunk, it's too small or too low-contrast. Big headline, high contrast, one focal point per frame.
Rule 5: One background, one frame, one type style — across all 8. Consistency is what separates a listing that looks designed from one that looks thrown together. Pick a background palette that matches your brand, pick one device frame, pick one caption style, and apply them to every screenshot. The eye reads a consistent set as trustworthy. A set where every frame has a different background reads as amateur, even when each individual shot is fine.
Rule 6: Design for the thumbnail, not the full size. Your screenshot will most often be seen small — in search results, in a category list, at maybe a third of full size. Open your design at thumbnail scale and check: can you still read the headline? Is the key UI element still visible? If the text turns to mush when shrunk, it's too small or too low-contrast. Big headline, high contrast, one focal point per frame.
Rule 7–9: Show results, localize the look, test and iterate
Rule 7: Show outcomes, not just features. "Has a calendar" is a feature. "Never miss a deadline again" is an outcome. People install apps to get a result, not to acquire features. Where you can, frame a screenshot around the after-state — the organized inbox, the finished workout streak, the saved money — instead of the tool that produces it.
Rule 8: Match the look to your audience. A meditation app and a developer tool should not have the same screenshot energy. Calm app → soft gradients, lots of breathing room, gentle type. Power tool → dense, dark, confident, information-rich. The background, frame color, and type you choose tell the viewer who this app is for before they read a single word. Pick frames and backgrounds that match the feeling, not just the platform.
Rule 9: Treat screenshots as testable, not finished. Your first screenshot set is a hypothesis, not a monument. Ship it, watch your store conversion rate, then change one thing — the lead frame, the headline wording, the background — and watch again. The biggest wins usually come from the first frame, because that's the one doing the search-results selling. The whole point of using a fast framing tool is that re-exporting a new variant takes minutes, so iterating costs you almost nothing. Browse the full device frame library to test how the same screenshot reads in a phone versus a tablet versus a laptop — sometimes the form factor itself is the variable worth testing.
Nine rules, but they collapse to one idea: stop shipping evidence with no argument. Every screenshot should make a claim, prove it, and look like it belongs to the same product as the seven beside it. For the broader picture of how screenshots fit alongside your icon and listing copy, Apple's own product page guidance is a surprisingly good read even if you're shipping on Android.
Rule 8: Match the look to your audience. A meditation app and a developer tool should not have the same screenshot energy. Calm app → soft gradients, lots of breathing room, gentle type. Power tool → dense, dark, confident, information-rich. The background, frame color, and type you choose tell the viewer who this app is for before they read a single word. Pick frames and backgrounds that match the feeling, not just the platform.
Rule 9: Treat screenshots as testable, not finished. Your first screenshot set is a hypothesis, not a monument. Ship it, watch your store conversion rate, then change one thing — the lead frame, the headline wording, the background — and watch again. The biggest wins usually come from the first frame, because that's the one doing the search-results selling. The whole point of using a fast framing tool is that re-exporting a new variant takes minutes, so iterating costs you almost nothing. Browse the full device frame library to test how the same screenshot reads in a phone versus a tablet versus a laptop — sometimes the form factor itself is the variable worth testing.
Nine rules, but they collapse to one idea: stop shipping evidence with no argument. Every screenshot should make a claim, prove it, and look like it belongs to the same product as the seven beside it. For the broader picture of how screenshots fit alongside your icon and listing copy, Apple's own product page guidance is a surprisingly good read even if you're shipping on Android.
What backgrounds and colors actually work?
Once you've got the structure right, the background is what separates a screenshot set that looks designed from one that looks decorated. A few things I've learned the hard way.
Use your brand color, but dial it down. A screenshot background screaming at full saturation fights with the UI inside the device frame and tires the eye across eight frames. I usually take the brand color and pull it toward a softer gradient or a darker, desaturated version so the actual app screen stays the hero. The device and its content should be the brightest, sharpest thing in the frame.
Contrast is non-negotiable for the headline. Dark headline on a light background, or light headline on a dark background — never mid-tone text on a mid-tone field. The fastest way to check: squint at the thumbnail. If the words blur into the background when you squint, a stranger glancing at search results won't read them either.
Pick a direction and commit to all eight. A light, airy set or a dark, premium set — both work, but pick one. Switching between light and dark frames mid-carousel reads as indecision. Dark backgrounds tend to make colorful app UI pop and feel premium; light backgrounds feel friendly and approachable. Match the mood to your audience from Rule 8.
Leave breathing room around the device. Crammed screenshots feel cheap. Give the framed device margin on all sides so it sits in the canvas rather than bursting out of it. The empty space is doing work — it's what makes the whole thing read as intentional. In the PlayMockUp studio you can nudge the device scale and background until that margin feels right, then lock the same settings across every frame so the set stays consistent.
Use your brand color, but dial it down. A screenshot background screaming at full saturation fights with the UI inside the device frame and tires the eye across eight frames. I usually take the brand color and pull it toward a softer gradient or a darker, desaturated version so the actual app screen stays the hero. The device and its content should be the brightest, sharpest thing in the frame.
Contrast is non-negotiable for the headline. Dark headline on a light background, or light headline on a dark background — never mid-tone text on a mid-tone field. The fastest way to check: squint at the thumbnail. If the words blur into the background when you squint, a stranger glancing at search results won't read them either.
Pick a direction and commit to all eight. A light, airy set or a dark, premium set — both work, but pick one. Switching between light and dark frames mid-carousel reads as indecision. Dark backgrounds tend to make colorful app UI pop and feel premium; light backgrounds feel friendly and approachable. Match the mood to your audience from Rule 8.
Leave breathing room around the device. Crammed screenshots feel cheap. Give the framed device margin on all sides so it sits in the canvas rather than bursting out of it. The empty space is doing work — it's what makes the whole thing read as intentional. In the PlayMockUp studio you can nudge the device scale and background until that margin feels right, then lock the same settings across every frame so the set stays consistent.
Frequently asked questions
How many app screenshots should I have?
Use all the slots the store gives you if you can fill them with value — up to 8 on Google Play. Each screenshot is free search real estate, and fuller, captioned sets convert better. The minimum is 2, but two bare screens rarely sell an app well.
Should app screenshots have text on them?
Yes. A short headline of three to five words on each screenshot is the single highest-impact change you can make. It tells the viewer what they're looking at instead of forcing them to decode a bare UI screen, and it's what survives the search-results thumbnail crop.
Do framed screenshots convert better than raw ones?
In most cases, yes. A device frame signals a real, shipping product and gives every screenshot a consistent shape so the carousel looks designed. You can frame any screenshot for free in the [PlayMockUp studio](/create) with exact bezels and corners, or browse the full [device frame library](/frames) first.
What order should I put my app screenshots in?
Order by strength, not by app flow. Lead with your single biggest benefit, then your second-best, because the first two frames are all most users see in search results. Save onboarding and settings screens for the back of the set.
What's the most common app screenshot mistake?
Shipping bare, uncaptioned phone screens with no headline and no device frame. The developer knows what each screen does, but the stranger scrolling the store doesn't — so they keep scrolling. Add a headline and a consistent frame and that problem mostly disappears.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.