App Store screenshot best practices
What actually converts on the App Store in 2026, shown weak vs strong: four principles, four set structures, and the 60/40 rule Apple does not really enforce.
What are App Store screenshot best practices?
App Store screenshot best practices are the design and sequencing rules that turn a store visit into an install: lead frame 1 with your single biggest benefit, wrap real app UI in a current device frame, keep captions readable at thumbnail size, hold one color and type system across the whole set, and keep most of every frame showing the actual app rather than marketing art (the widely-used 60/40 heuristic). Get those five right and the rest of app screenshot optimization is testing, not guessing.
They matter more than any other listing element because of placement. The first three screenshots show up directly in App Store and search results before anyone taps through, so they carry the install decision on their own. Everything below expands each principle into a weak-vs-strong example, gives you four ways to order your frames, and ends with a pre-flight checklist to run before you upload.
Weak frame, strong frame.
Every principle below is a side-by-side. Left is the mistake almost everyone ships. Right is the fix.
Lead with the value, not the app name
Frame 1 gets about 1.5 seconds to answer "what is this and why should I care" before the reader scrolls past. A logo and a greeting waste it. Name the outcome someone installs for.
- Put the single biggest benefit in frame 1
- Name the pain point so users self-identify
- Show real UI, never just an icon or a splash screen
Welcome to MyApp
Split bills in one tap
Give the eye one place to land
Readers scan a frame top-to-bottom in a moment, then move on. When every element has equal weight there is no focal point, so nothing registers. Compose one clear hero per frame.
- One dominant element per frame, supporting detail second
- Use whitespace to point at the thing that matters
- Keep a consistent flow from headline to UI to action
Everything, all at once
One inbox. Zero chaos.
Write captions that survive thumbnail size
The first three frames are first seen small, in search results, long before anyone opens the full listing. A sentence in light grey disappears there. Three to five bold words do not.
- Three to five words per frame, bold weight
- Minimum 16pt, ideally 18 to 24 for legibility
- Read every caption at thumbnail size, not full screen
manage your daily tasks more efficiently and stay on top of everything
PLAN YOUR DAY
Match the palette to your app icon
Color carries half the brand signal at gallery thumbnail size, before a single word is read. A rainbow of trend colors reads as a different app than the one in the icon. Match, do not decorate.
- Pull the palette from your app icon, not design trends
- High contrast for captions (WCAG AA, 4.5:1 minimum)
- Reuse one accent color across callouts and badges
TRACK YOUR RUNS
TRACK YOUR RUNS
Four ways to order the frames.
Pick the one that matches how your app earns the install. Whatever you choose, the first three frames still do most of the work.
Feature-focused
Use when your value is a set of distinct features.
User journey
Use when the "aha" only lands once people see the flow.
Social-proof first
Use when you have ratings or numbers worth leading with.
Problem and solution
Use when the pain is obvious and relatable.
Three things most guides get wrong.
The advice that gets repeated the most is the advice most worth double-checking.
"60% of the pixels have to be app UI."
There is no literal 60/40 rule in the App Store Review Guidelines. The split is a community heuristic. What Apple enforces is Guideline 2.3.3 (show the app in use, represent it accurately) and 2.3.10 (no references to other platforms). Keep most of every frame on real UI because it converts and stays compliant, not because a ratio is policed.
"More copy makes a screenshot more informative."
The first three frames are first seen at thumbnail size. Three to five words in a bold weight read there; a full sentence turns to mud. Cut the caption until only the benefit is left, then check it small, not on your full monitor.
"Save social proof for the ratings section."
Most scroll drop-off happens after frame 3. A rating or user-count frame around position 3 catches people while they are still looking. If you have proof worth showing, bake it into the set instead of hoping they scroll to the reviews.
Before you ship the set.
Two passes: the one that catches rejections, and the one that catches missed conversions.
Before you start
- Identify the single biggest reason someone installs your app
- Pull the app icon palette so the gallery matches the brand
- Check the top 3 competitors for layout patterns to avoid
- Pick the 3 to 5 features the set will explain
Before you upload
- Verify dimensions match App Store Connect exactly (no resizing on upload)
- Read every caption at thumbnail size, not on your full-screen monitor
- Confirm every frame shows real app UI in use (Guideline 2.3.3)
- Put social proof around position 3 if you have it to show
Common questions.
How many App Store screenshots should I have?+
Apple allows up to 10 screenshots per device size and requires at least one. Three to five is the practical sweet spot: the first three carry the install decision because they show in search and on the product page before anyone taps through, and the rest add depth for people who keep scrolling.
Do App Store screenshots have to show real app UI?+
Yes. App Store Review Guideline 2.3.3 requires screenshots to show the app in use and accurately represent it. You can add captions, backgrounds, and device frames, but the screen itself has to be your actual app, not a marketing illustration or a feature that is not in the build.
What is the 60/40 rule for App Store screenshots?+
The 60/40 rule is a community heuristic that says roughly 60% of a screenshot should show app UI and up to 40% can be marketing or lifestyle content. It is not written in the App Store Review Guidelines. What Apple actually checks is accuracy (2.3.3) and no references to other platforms (2.3.10). Keeping most of the frame on real UI is good practice, not a policed pixel ratio.
What size do App Store screenshots need to be?+
App Store Connect requires exact pixel dimensions per device: 1260 x 2736 for the 6.9-inch iPhone and 2064 x 2752 for the iPad Pro 13-inch are current required sizes. Uploading the wrong dimensions is one of the most common rejections, so match the spec exactly and never let the upload resize for you.
How often should I update my App Store screenshots?+
Refresh when the product changes meaningfully, when you have new social proof worth leading with, or when a test shows a stronger set. On iOS you can update screenshots without shipping a new build by editing the current version metadata, so there is no reason to leave a weak set live.
Do captions on screenshots help App Store keyword ranking?+
Not directly through the keyword field, but the App Store runs OCR on the text in your screenshots, and clear captions improve tap-through, which feeds conversion signals. Write captions for the human scanning the gallery first; the indexing is a bonus.
Keep going
Skip the best-practices spreadsheet.
Describe your app, see a full set with these principles already applied, then refine the frames that are not landing yet. That is the whole loop.