App Store Screenshot Best Practices: 15 Rules That Convert
App Store screenshot best practices for 2026: 15 rules covering the first three screens, one message per screen, readable text, social proof and testing.
ScreenShipper team · · 8 min read
TL;DR: The best App Store screenshots lead with your strongest benefit in the first three slots, give each image one message, use short headlines that stay readable at search-result size, show real and current app UI, back claims with true social proof, are localized for every market you sell in, and get tested with Product Page Optimization instead of being chosen by taste.
The 15 Rules at a Glance
Use this table as a scorecard for your current set. Each rule is explained below with the reason behind it and a quick way to check it.
| # | Rule | Quick check |
|---|---|---|
| 1 | Lead with your strongest benefit | Would screenshot one alone make someone tap? |
| 2 | Design the first three as a unit | Do they read well side by side? |
| 3 | One message per screenshot | Can you state each image's point in five words? |
| 4 | Follow a deliberate sequence | Does the order build a story? |
| 5 | Write for thumbnail size | Is the headline legible on a phone in search? |
| 6 | Keep headlines short and benefit-first | Are most headlines 3–6 words? |
| 7 | Make the UI the hero | Is the key detail big enough to see? |
| 8 | Use one consistent visual system | Same fonts, margins and frame style throughout? |
| 9 | Show the real app | Would a reviewer find every screen in the build? |
| 10 | Keep social proof true and current | Can you prove every rating and award? |
| 11 | Be clear about what costs extra | Are paid features labeled? |
| 12 | Localize text and UI | Does each market see its own language? |
| 13 | Design each device on its own terms | Does the iPad set show real iPad layouts? |
| 14 | Test instead of guessing | Is a PPO test running or planned? |
| 15 | Refresh with your product | Do screenshots match the current version? |
Rules for Order and Message (1–4)
1. Lead with your strongest benefit
Many people decide from the search result without ever opening your product page. Apple notes that the first one to three images can appear in search results when no app preview is available, so slot one should carry the promise that best explains why your app exists. Our guide to the first App Store screenshot breaks down formulas for that opener.
2. Design the first three as a unit
With portrait screenshots, three images sit side by side in a search result. Treat them like a small billboard: consistent background, aligned headlines, and a combined message that works even if nobody reads the rest.
3. One message per screenshot
A screenshot that tries to show three features communicates none. Apple's own product page guidance recommends focusing each subsequent screenshot on a main benefit or feature. If you can't summarize an image in five words, split it.
4. Follow a deliberate sequence
Order screenshots so they build understanding. Proven sequences include the core loop (capture, organize, share), problem to solution to proof, or most-used feature to secondary features to breadth. End with something that reassures: integrations, privacy, or social proof.
Rules for Readability and Design (5–8)
5. Write for thumbnail size
In search results each screenshot is shown small. Headline text that looks generous on your 27-inch monitor can become unreadable on a phone. Shrink your design to search-result size before approving it. If you squint and can't read the headline, it is too small or too long.
6. Keep headlines short and benefit-first
Aim for roughly 3–6 words that describe an outcome, not a feature name. "Plan meals in minutes" beats "Meal planning module." Highlight one word in your accent color to guide the eye. See our App Store screenshot captions guide for formulas and examples.
7. Make the UI the hero
The headline makes a claim and the UI proves it. Crop or zoom so the proof is visible: the chart, the finished photo, the completed checklist. A full screen of tiny list items proves nothing at thumbnail size. Zoom callouts and frameless layouts are useful when details matter.
8. Use one consistent visual system
Same font family, same headline position, same margins and the same frame style across the set. Pick a palette derived from your icon so the result reads as one brand. Consistency makes the set feel like a product rather than a collage. Our guide to App Store screenshot colors shows how to build that palette.
Rules for Trust and Accuracy (9–11)
9. Show the real app
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. Guideline 2.3 asks that metadata accurately reflect the app's core experience. Mockups of features you haven't shipped can get your metadata rejected, and they disappoint the people who do install. Our explainer on App Store screenshot guidelines covers each rule.
10. Keep social proof true and current
Ratings, review quotes, press mentions and awards can lift trust, but only when they are real, attributable and current. Don't round a 4.4 average up to five stars or keep an award badge from years ago on the first screen. Read more on social proof in App Store screenshots.
11. Be clear about what costs extra
Guideline 2.3.2 asks that your description, screenshots and previews clearly indicate when featured items, levels or subscriptions require additional purchases. If a screenshot features a premium tool, a small "Premium" label avoids misleading people. Separately, Guideline 2.3.7 says screenshots shouldn't include prices, so describe the value, not the price tag.
Rules for Markets and Devices (12–13)
12. Localize text and UI
Translate captions for every App Store localization you support, and swap in localized captures where your app's UI is translated. An English headline in the Japanese storefront signals that the app may not be fully localized either. Account for text expansion in German and French, right-to-left layouts for Arabic and Hebrew, and fonts that cover CJK characters. Our screenshot localization guide helps you pick markets in a sensible order.
13. Design each device on its own terms
The iPad 13″ set is required if your app runs on iPad, and it should show your real iPad layout, not a stretched phone screen. The same applies to Mac (16:10 landscape) and Apple Watch. If your app supports Dark Mode, Apple suggests including at least one screenshot showing it. Exact dimensions for every slot are in the App Store screenshot sizes guide.
If you also publish on Google Play, adapt rather than copy. Google's Play Console help recommends avoiding claims like "Best," "#1" or "Free," keeping taglines to a small part of the image, and never showing other stores' badges.
Rules for Testing and Upkeep (14–15)
14. Test instead of guessing
Opinions about screenshots are cheap and often wrong. App Store Connect's Product Page Optimization lets you test up to three treatments against your original product page, varying screenshots, previews or the icon. Test one big idea at a time, such as a different first screenshot or a different benefit order, and let the test run long enough to reach confidence. The Product Page Optimization guide walks through setup.
Custom Product Pages, currently up to 70 per app, let you show different screenshot sets to different audiences, for example to match an ad campaign's message.
15. Refresh with your product
Guideline 2.3 asks you to keep metadata up to date with new versions. Update screenshots when your UI changes visibly, when you ship a feature worth leading with, or when a localization goes live. Outdated screenshots erode trust and can trigger rejections.
How to Audit Your Current Screenshots in 10 Minutes
Run this quick review before your next submission:
- Search for your app's main keyword on an iPhone and look at your result next to the competitors around it.
- Cover everything except your first screenshot. Is the benefit obvious in two seconds?
- Read only the headlines, top to bottom. Do they tell a coherent story?
- Check every claim against the current build and your actual ratings.
- Open two non-English localizations and look for English text, overflow or untranslated UI.
- Compare the iPad set with your real iPad app.
- Pick the weakest screenshot and write down one change you will test.
If the audit turns up structural problems, rebuilding from a plan is often faster than patching. Our step-by-step guide on how to make App Store screenshots takes you from storyboard to upload.
Frequently Asked Questions
Should I copy my competitors' screenshot style?
Study competitors to learn your category's conventions, then differentiate. If every app in your search results uses the same blue framed layout, a set that follows these rules but looks different is more likely to be noticed.
Should App Store screenshots have device frames?
Frames are optional. They help signal the platform and give the UI a clean edge, while frameless layouts show the interface larger. Pick one approach and keep it consistent across the set.
Is it better to use portrait or landscape screenshots?
Portrait suits most apps because up to three images can show in search results. Landscape suits games and video apps that run in landscape, but typically only one landscape image appears in a search result.
Can I put text in App Store screenshots?
Yes. Guideline 2.3.3 allows text and image overlays on screenshots that show the app in use. Keep the text short, accurate and free of prices.
How often should I update App Store screenshots?
Update them whenever the UI changes visibly or a new key feature ships, and plan a review at least with every major release. Screenshot updates go through review with an app version.
Sources
Design your App Store screenshots now
Pick one of 102 templates, drop in your app screens and export every iPhone, iPad and Android size from one design.