What to put on App Store screenshot 1
the short version
- Screenshot 1 is a poster. One screen of the real app, the moment that makes it worth having, and a caption of two to six words.
- Not the login screen, not the logo, not a collage of features. People decide from the first frames in search, often without opening your page.
- The caption says what the person gets, not the feature’s internal name. It has to be readable when the image is tiny.
- Check it on a phone, next to three apps in your category, before you design frames two to ten.
In this post6 sections
Put the hero moment on screenshot 1. One screen of the real app, filled with believable content, and a caption of two to six words that says what the person gets. Not the login screen. Not a logo on a colour. Not eleven features in a collage. If a stranger can tell what the app does from that single frame at thumbnail size, the frame is done.
In App Store search, people see your icon, your name, your subtitle and the first few screenshots. Plenty of them never open the product page. Frame 1 is the one they cannot miss. The other nine checks (caption size, status bar, the set read as a sentence, the icon agreeing with the frame) are in the screenshot checklist. This post is only the first frame, because that’s the one that does the selling.
We haven’t shipped a client’s screenshot set. We’re a new studio. What follows is the check we’d make in a teardown, and the one you can make this afternoon.
Screenshot 1 is a poster
A poster has one idea, big enough to read from across the room. A screenshot set is a short story. Frame 1 is the poster they see before they agree to hear the story.
The idea is the hero moment: the screen where a new person goes “oh, nice”. Not the screen that took the longest to build, and not the settings page you’re proud of. If you haven’t picked that moment yet, picking it is the job. The four-week plan is where it gets chosen. The frame just shows it.
Write the outcome in a sentence before you open a design file. “You can see which flatmate owes you £37.” The frame has to prove that sentence. If the picture needs a paragraph underneath it, the picture is of the wrong thing.
If frame 1 only makes sense after frame 4, frame 1 isn’t finished. It’s a preface.
The words beside the picture have a job too. Your subtitle and this caption should agree. The listing-copy post is those words. Read the subtitle and the caption out loud, one after the other. If they sound like two different apps, one of them is wrong.
The caption does one job
Two to six words. What the person gets, not what the feature is called internally.
| Instead of | The caption |
|---|---|
| “Smart expense engine” | “See who owes you” |
| “Inventory management” | “Cook what’s in the fridge” |
| “AI-powered planning” | “Your week, in one tap” |
| “Seamless collaboration” | “The tab, kept up to date” |
“Seamless” and “smart” don’t survive thumbnail size. They don’t survive a person either. Say the verb. See, cook, split, keep, send.
Put the caption where it won’t fight the UI. High contrast, heavy enough that it still reads when the App Store shrinks the image to a slice of a search result. Nothing important in the bottom quarter, where thumbs and the next screenshot’s edge compete with it. The checklist post has the full thumbnail test. For frame 1, do it before you design anything else: if this caption fails, the set doesn’t have a beginning.
A question can be the caption, if the picture answers it. “Forgot who paid?” only works if the screen shows the answer. A question on its own is a poster for a product you forgot to include.
What to leave off
The failures are boring, which is why they keep shipping.
The login screen. A stranger already knows apps have logins. It tells them nothing they’d tap for.
The logo, large, with a slogan. The icon next to your name is already the logo. Spending frame 1 on it again is spending your best slot twice.
A collage. Four phones, three feature callouts, a badge that says “NEW”. That’s a flyer. Flyers get skimmed. One screen, full size, gets understood.
Empty UI. “John Doe”, lorem ipsum, a grey box where a photo should be. Filled-in content shows what a life with the app looks like. An empty app shows a file that isn’t finished. Use clearly fictional names and meals if you don’t have permission to use real ones. Say they’re fictional. Don’t borrow a stranger’s face.
A number you don’t have. “Join 10,000 people” on the day you launch is a claim, and a claim on a poster is the first thing a careful person checks. If you have no users yet, don’t invent them. The product is allowed to be new. The landing-page post says the same thing about the website. The store is not a loophole.
A tiny phone in a huge marketing background. The UI is the product. Let it be big. If the interface is the size of a stamp, you designed a poster about the app, not a poster of it.
The phone test
Do this before frames 2 to 10 exist, so you don’t decorate a weak poster.
- Put the frame on your phone, not on the monitor you designed it on.
- Hold the phone at arm’s length. Read the caption without squinting. If you can’t, the type is too small or too thin. Make it bigger than feels comfortable.
- Search your category on the App Store and look at the three apps above where you’d sit. Would you tap yours?
- Cover the caption with your thumb. Can you still tell what the app does from the screen alone? If the caption is doing all the work, the picture is a decoration.
- Cover the picture. Does the caption still mean something? If it only means something next to a diagram, it’s too clever.
Show it to someone who has never seen the app. Ask them what it does. If they describe a category (“some finance thing”) rather than the job (“it shows who owes me”), the frame isn’t specific enough. Add the concrete thing. A flatmate. A receipt. £37. Specifics are what make a poster tappable. Categories are what make it ignorable.
If you have an app preview, it plays before the screenshots, so frame 1 is the first still, not always the first thing seen. The poster frame of that video and screenshot 1 should be the same idea. Two different “wow” moments in a row feels like two products.
Rewrites
Same made-up apps as the other posts. The change is always the same: a vague noun becomes a verb and a thing you can point at.
| The frame people ship | The frame that says what it does |
|---|---|
| A logo, a gradient, “Welcome to Split” | A receipt, three names, one of them highlighted: “See who owes you” |
| A dashboard with twelve charts | One chart that answers one question: “What you spent on food” |
| An empty calendar and “Plan smarter” | A week already filled, one gap obvious: “Your week, in one tap” |
| Five feature icons in a ring | The single screen those icons were apologising for |
Then stop. Frame 2 can be how, frame 3 can be the detail people worry about (privacy, price, who can see it). Frame 1 does not do their jobs. If you try to make it, you get the collage back.
Once the app is live, App Store Connect’s product page optimisation is how you test a second version of frame 1 against the first. Arguing about it in a group chat is not a test. The checklist has that step. Don’t run it before the first version is honest.
The checklist
A full set, plus an honest look at the icon, is what we do for App Store screenshots: about a week, from £1,500, on the screenshot page. Frame 1 is the part we’d want to see first.
If you already have a set and you want someone to say whether frame 1 would get the tap, book a free 15-minute call. Bring the frame. We’ll tell you what a stranger sees.
