What to Put on Your First App Store Screenshot
Your first App Store screenshot often shows in search before anyone opens the listing. Here's what it has to say, the patterns that work, and examples.
Your first App Store screenshot should tell a stranger, in a couple of seconds and at thumbnail size, what they get from your app, and show the real screen that proves it. In practice that means one short outcome headline above your most convincing piece of UI. It is the most visible image you have, because on iPhone it appears in App Store search results before anyone opens your product page.
Below: what the first screenshot has to do, the patterns that tend to work, weak and strong examples by app type, and how search results differ between iPhone and Google Play.
- The first App Store screenshot is the first image in your set; Apple shows the first one to three screenshots in search results when you have no app preview video.
- With portrait screenshots, up to three appear side by side in an iPhone search result, so screenshot 1 is read alongside screenshots 2 and 3.
- A strong first screenshot pairs an outcome headline of roughly 3 to 7 words with real app UI that proves it.
- Apple's guideline 2.3.3 says screenshots should show the app in use, not merely title art, a login page or a splash screen, so a logo-only first screenshot is a risk.
- Google Play leads the listing with the feature graphic and video, and its guidance bans words like Best, #1 and Free in screenshots.
What the first App Store screenshot has to do
The first screenshot has one job: earn the tap. It is usually seen in a search result next to several competitors, at a fraction of its real size, by someone who typed a generic query like "budget app" or "sleep sounds". In that moment it has to answer three questions:
- What is this? The category should be obvious from the UI alone.
- What do I get? The headline names the outcome, in the user's words.
- Is it any good? The UI looks finished, real and populated with believable data.
Your app name, icon and subtitle sit right above the screenshots in the search result, so the first screenshot doesn't need to repeat the name. It should add what the subtitle can't: a visual promise.
How App Store search results show your first screenshots
Apple's product page guidance says that "depending on the orientation of your screenshots, the first one to three images will appear in search results when no app preview is available." In practice:
| Your set | What an iPhone search result shows |
|---|---|
| Portrait screenshots, no app preview | The first three screenshots, side by side |
| Landscape screenshots, no app preview | The first screenshot only, full width |
| An app preview video | The preview takes the first slot in search (autoplaying muted where autoplay is on), followed by screenshots |
Two consequences follow. First, with portrait screenshots your first image is never seen alone in search; screenshots 2 and 3 sit beside it, so design them as a row that reads left to right. Second, if you add an app preview, its opening seconds and poster frame become your first impression in search, and the first screenshot moves to second place. Our post on app preview videos vs screenshots covers that trade-off.
Screenshots also don't help your keyword ranking directly in the way the title and keyword field do; we looked at that question in do App Store screenshots affect search rankings? Their job is conversion: turning an impression into a tap and a tap into a download.
How Google Play differs
On Google Play the first screenshot carries less weight on its own. The store listing leads with the feature graphic (a 1024 × 500 px banner) and your promo video if you have one, and screenshots follow in a horizontal row. Google also uses your graphics on browse and recommendation surfaces, which is why its preview asset guidance asks for at least four screenshots at 1080 px or more for apps to be eligible for promotion.
The same guidance also limits what your first screenshot can say. Google lists these among things screenshots must not contain:
- Promotional wording such as "Best", "#1", "Top", "New", "Free", "Discount", "Sale" or "Million Downloads"
- Calls to action such as "Download now" or "Try now"
- Time-sensitive taglines, or taglines covering more than 20% of the image
- Device imagery and Google Play or other store badges
So a first screenshot that says "The #1 budget app. Download free!" is a problem on Google Play even if it would get through on Apple. A neutral outcome headline over real UI works on both.
Patterns that work for the first screenshot
1. Outcome headline + hero UI
The default, and the safest. A short headline that names the result ("See where every dollar goes") above the screen that shows it (a populated spending breakdown). Most strong first screenshots are some version of this.
2. The finished result, big
For creative and utility apps, show the output rather than the tool: the edited photo, the clean scanned PDF, the finished invoice. Crop in so the result fills most of the canvas, and let a small slice of the UI around it show that it was made in the app.
3. Social proof hook
A headline built on genuine recognition (an Apple award, an editorial feature, a rating you can back up) above hero UI. This works best for apps whose reputation is already their strongest argument. Keep it truthful and current, and keep the UI on screen; a laurel wreath with no app in sight doesn't show the app in use.
4. Before and after
Split the canvas: a messy inbox and a sorted one, a blurry photo and a sharp one. It works when the transformation is visual and instant. It doesn't work for apps whose benefit unfolds over weeks.
5. Hook for the first three
Because the first three portrait screenshots appear together in search, some teams treat screenshot 1 as the opening line of a three-panel strip: a single headline that spans the row, or a visual that continues across. This only pays off if each screenshot still makes sense when viewed alone on the product page.
Weak vs strong first screenshots, by app type
These are illustrative rewrites, not real listings, but they reflect the patterns we see most often when looking through categories.
| App type | Weak first screenshot | Stronger first screenshot |
|---|---|---|
| Budgeting | Logo on a gradient, “Smart Finance” | “See where every dollar goes” over a populated monthly breakdown |
| Fitness | Empty workout list, “Workouts” | “Run your first 5K in 8 weeks” over a plan with week 3 ticked off |
| Language learning | Onboarding screen with a language picker | “Hold a real conversation in Spanish” over a lesson mid-dialogue |
| Photo editing | Toolbar with every tool visible | “Fix lighting in one tap” with a before/after of the same photo |
| Habit tracker | “The best habit app” with a 5-star badge | “Build habits that actually stick” over a 30-day streak calendar |
| Game | Title art and logo | Live gameplay at a dramatic moment with a 3–5 word line about the core mechanic |
The weak versions share the same problems:
- They name a feature or category ("Workouts", "Smart Finance") instead of a result.
- They show an empty or setup state, which reads as "you have work to do".
- They lean on unbacked claims ("the best"), which persuade nobody and run into Google Play's wording rules.
- They show title art, which Apple's guideline 2.3.3 explicitly says isn't enough.
Practical rules for the first screenshot
- Headline length. Roughly 3 to 7 words. Long headlines turn into grey lines at search size. For headline formulas, see App Store screenshot copywriting.
- UI size. Let the device or crop take up most of the canvas. If the UI is too small to recognise in a zoomed-out view, crop tighter or drop the frame.
- Contrast. Your screenshot sits on the App Store's white (or black, in Dark Mode) background. A pale first screenshot can disappear against white; check it on both.
- Clean captures. A tidy status bar and realistic data make the first screenshot look finished. Our guide to clean simulator and emulator screenshots has the exact commands.
- Localize it first. If you only localize one screenshot per market, make it this one.
How to check your first screenshot before you ship it
You don't need a test to catch the obvious problems. Three quick checks catch most of them:
The search-row check
Search the App Store on an iPhone for the main keyword you want to rank for and screenshot the results. Then mock your own first three screenshots into the same row at the same size. Does yours read as clearly as the apps around it? Is it the one your eye goes to, or the one it skips? Doing this against the actual competitors for your keyword is more useful than judging the screenshot on its own at full size on a laptop.
The five-second check
Show the first screenshot, shrunk to roughly search-result size, to someone who hasn't seen the app, for about five seconds. Then ask what the app does and who it's for. If they describe a feature instead of an outcome, or guess the wrong category, the headline or the UI choice needs another pass.
The rules check
- Does it show the app in use, not just a logo or splash screen? (Apple 2.3.3)
- If the hero feature needs a subscription or in-app purchase, is that clear somewhere in the listing? Apple's guideline 2.3.2 asks that screenshots and descriptions make it clear when featured items require additional purchases.
- Is it free of prices? Apple's guideline 2.3.7 says screenshots should not include prices.
- Is any rating, award or press quote real and current?
Those references are all in Apple's App Review Guidelines, section 2.3 (Accurate Metadata), which is short enough to read in full before a launch.
Design store-ready screenshots in minutes — free, no export watermarks.
Launch Shots is free to start. Every template (110+), 220+ device frames plus 3D mockups, AI localization, and direct upload to App Store Connect and Google Play Console. No credit card needed.
Start creating free →Test it instead of guessing
The first screenshot is the best single thing to A/B test, because it's the image most people see. Apple's Product Page Optimization in App Store Connect lets you test alternate screenshots against your original, and Google Play's store listing experiments do the same for graphics. Change only the first screenshot, let the test run long enough to reach a confident result, and keep the winner. Our guide to A/B testing App Store screenshots walks through the setup.
If you're building the whole set from scratch, start with our step-by-step guide on how to make App Store screenshots and come back here when you get to screen 1.
The short version
- One outcome headline, roughly 3 to 7 words, no feature names
- Real, populated app UI that proves the headline, large enough to recognise small
- No logo-only, splash or login screens (Apple 2.3.3)
- No "Best", "#1", "Free" or "Download now" if you also ship on Google Play
- Designed to sit beside screenshots 2 and 3 in an iPhone search result
- Localized and A/B tested before any other screenshot
Frequently asked questions
04- Should the first App Store screenshot show the app's main screen?
- Usually, yes, but not always the literal home screen. The first screenshot should show the screen that best proves the app delivers its main outcome, which is often a result screen (a finished budget, a completed workout, an edited photo) rather than the empty dashboard people land on after sign-up. Apple's guideline 2.3.3 also rules out using a login page or splash screen as a screenshot.
- Can my first App Store screenshot be just text or a logo?
- Not on its own. Apple's App Review Guidelines, section 2.3.3, say screenshots should show the app in use and not merely title art, a login page or a splash screen. A first screenshot that is only a logo or a slogan risks rejection and wastes the most visible slot in search. Pair the headline with real app UI, even if the UI is cropped or partly off-canvas.
- Does the first screenshot need to be the same on iPhone and iPad?
- The message should be the same, but the image shouldn't be a stretched copy. iPad screenshots are uploaded separately at 13-inch iPad sizes, and the first iPad screenshot appears in iPad search results the same way the iPhone one does. Keep the same headline and story, and rebuild the layout around a real iPad capture so it fits the wider canvas.
- How do I know if my first App Store screenshot is working?
- Compare product page views to downloads, and impressions to product page views, in App Store Connect's App Analytics before and after a change. For a cleaner answer, run a Product Page Optimization test in App Store Connect with a different first screenshot as the only change. On Google Play, store listing experiments do the same for your main listing graphics.