Blog · August 25, 2026

How to make App Store screenshots that convert

One of my apps launched to complete silence. Good app, real problem, nothing wrong with it. It sat at a handful of downloads a day for weeks. Then I changed one thing, the first screenshot, and the same app started converting the same traffic two to three times better. Nothing about the product changed. The listing just finally said what the app was for.

App Store screenshots are the part of marketing most builders treat as an afterthought, and they are the one thing that decides whether your product page turns a visitor into a user. Here is what actually moves the needle, learned the slow way across four apps that Apple featured and plenty that it did not.

Most people decide from the first three screens

People do not scroll. In search results and at the top of your product page, the store shows two or three screenshots, on a phone, for a second or two. That first glance is the whole pitch. So treat the first three screenshots as your ad and everything after as the fine print for the few who keep going. If those three do not land, nothing else on the page gets a chance.

Sell the outcome, not the interface

The most common mistake is showing your UI. A tidy settings screen means nothing to someone who does not use the app yet. Show what the app gets them instead. Lead each screen with the result: the run tracked, the invoice sent, the streak kept. Then cut the caption until only the benefit is left. “Powerful analytics dashboard” is a feature. “See exactly where your day went” is a reason to download.

One message per screen, readable at thumbnail size

Each screenshot should make exactly one point. Put it in a short, bold caption above the app, five to seven words, two lines at most. Then check it small. Not on your 27 inch monitor, on your phone, in the actual store, at the size a stranger sees it. If the headline is not legible there, it does not exist. Big type and high contrast beat clever every time, and clutter is the fastest way to lose someone.

Show the real app, in a device frame

Apple expects real in-app UI in your screenshots, not invented marketing art, so use your actual screens. But do not paste raw captures flat on a background. Wrap them in a device frame. A phone frame anchors the eye and quietly tells the viewer “this is what it looks like on my phone”. That is the difference between a slide and a product.

Make the whole set look like one app

Five screenshots in five different styles read as five different apps. Pick one background, one type treatment, one caption position, and hold it across the set. Consistency is what makes a listing feel finished and worth trusting. It is also what lets you swap one screen later without redesigning the rest.

Order by priority, then test

Your clearest, strongest screen goes first, because it is the only one guaranteed to be seen. Then the second reason, then the third. Once the set is live, change one screenshot at a time and watch what happens. App Store Connect and Google Play both let you test variations. A small caption change routinely moves installs more than a whole new feature does.

A word on all those sizes

You do not ship one screenshot, you ship the same idea in a stack of sizes: the 6.9 and 6.5 inch iPhone, the 13 inch iPad if you support it, the Play Store phone and tablet sizes for Android. That is a lot of exports of the same layout, and it is exactly where sets fall apart. Set the layout up once so every size comes out matching, or you will quietly publish an inconsistent set just to be done with it.

Where this fits Monocards

This is the boring, repeated work Monocards is built for. The Device Mockup card wraps your screenshot in a phone, tablet, browser or laptop frame, in the App Store and Play Store sizes, with your caption and your look already set. You design the frame and the type once, save it as a template, and every screen after that comes out matching in every size you need. If you build with an agent, you can hand it the screens and the captions and get the whole set back through a local MCP server, on your Mac, with no image model in the loop.

The app is optional. The rules are not. Lead with the outcome, keep it readable small, show the real app in a frame, and make the first three screens carry the pitch. Do that and the same traffic you already have starts converting better, which is the cheapest growth there is, the same idea behind promoting an app without a marketing budget.