App Store screenshots are the highest-leverage art an indie app ships, yet most look like cropped device screens with hope attached. App Store search and the editorial feed show your first 2-3 screenshots inline, before anyone taps the listing, so those frames carry as much install weight as the icon and subtitle combined. This guide gives the layout patterns that convert in 2026, the exact App Store Connect dimensions current as of June 2026, and the per-device variants that hold up across the Apple ecosystem.
TL;DR
- Use the caption-first frame: a bold one-line caption (8 words or fewer) at the top, a real product screen below, one consistent background color across all 10 slots.
- Front-load the first three frames with your strongest benefits. Most users decide there.
- Design at the 6.9-inch source size, 1320 x 2868 portrait, and let App Store Connect downscale to older devices. Submissions even one pixel off the spec are rejected.
- Ship light and dark variants; the App Store renders the viewer’s system theme.
- Healthy page-view-to-install conversion sits around 25% in the US App Store as of 2026, but Apple’s own Benchmarks tab compares you to your category, which matters more than any cross-industry number.
When this applies to you
- You are launching for the first time, or refreshing screenshots after a UI redesign.
- Your App Store Connect conversion rate is below your category benchmark (check the Benchmarks tab, not a generic 25%).
- Your screenshots are pure device screens with no captions.
- Your screenshots read well at full size but are illegible at the thumbnail size shown in search.
The first 3 frames
Search results and the Today/Apps feed surface your first frames before a tap, so the opening three do most of the work:
- Frame 1 — primary promise. The one-sentence answer to “why install this.” The caption restates the subtitle in a tactile way; the screen shows the most representative real state of the app.
- Frame 2 — key differentiator. Why this app over the obvious competitor. The caption is concrete (“21-day streaks,” not “powerful features”); the screen shows the unique feature in use.
- Frame 3 — proof or specificity. A press quote, a user testimonial line, or a very specific number. The screen can be an achievement or share view, not the home screen.
Frames 4 through 10 are for depth: feature tour, integrations, privacy posture, before and after. Most users never scroll that far, so do not park critical content there.
Caption rules
- Eight words maximum. Anything longer is unreadable at thumbnail size.
- Lead with a verb or a number: “Build a habit in 5 minutes,” “21 days to a routine.”
- Drop marketing adverbs (“smoothly,” “easily,” “magically”). They are placeholders where a concrete benefit belongs.
- One caption per frame. Stacking a title plus a subtitle roughly halves readability.
- Same font, color, and position across all frames. Visual consistency reads as brand.
Exact dimensions (App Store Connect, June 2026)
Apple now treats the 6.9-inch iPhone and the 13-inch iPad as the mandatory source images and scales them down to populate older and smaller hardware. Design at the source size, then let App Store Connect handle the rest.
| Device class | Portrait (px) | Status |
|---|---|---|
| iPhone 6.9” (17 Pro Max, 16 Pro Max, 16 Plus) | 1320 x 2868 | Required if no 6.5” set |
| iPhone 6.5” (14 Plus, 13 Pro Max) | 1284 x 2778 | Fallback source; scaled if 6.9” absent |
| iPad 13” (iPad Pro, iPad Air) | 2064 x 2752 | Required if the app runs on iPad |
| Apple Vision Pro | 3840 x 2160 | Required if you ship visionOS |
File rules as of June 2026: PNG or JPEG, RGB color space, no alpha channel, exact pixel dimensions (no off-by-one tolerance — a one-pixel mismatch is rejected at upload), up to 10 screenshots per localization, 10 MB per file. Localize captions per language; you do not need separate device frames per language, only translated caption text plus translated in-screen UI strings. See Apple’s screenshot specifications for the full current table.
Light vs dark
- Ship both. The App Store renders the viewer’s system theme by default.
- Match the background to your app’s primary brand color in light mode and its dark-mode equivalent in dark mode. Do not invert blindly.
- Keep captions high-contrast: black text on light, white text on dark, never mid-gray.
- The screen inside each frame must match its outer theme. A light-mode frame wrapped around a dark-mode UI screenshot looks broken and erodes trust.
App preview video (optional, high-yield)
App previews autoplay silently in the listing and convert well when the first seconds land:
- Up to three previews per localization, 15 to 30 seconds each (Apple rejects anything shorter than 15s or longer than 30s).
- The first frame becomes the poster shown when a viewer has autoplay off, so open on your strongest UI state. No intro logo, no fade-in.
- An audio track must be present even when silent; a silent stereo AAC track satisfies the requirement.
- Captions appear in-video the same way as in screenshots: top, bold, one line.
- Screen-record at 60fps, trim aggressively. Skip background music; in our tests it lowers conversion versus a silent preview.
Production workflow
- Keep one source-of-truth Figma file with one frame per screenshot, organized by language and theme. Make the caption block a component instance so font and color changes propagate.
- Capture real device screens with Fastlane snapshot or Xcode UI testing at the exact pixel dimensions. Avoid manually scaled grabs; they look soft.
- Script the compositing step (Figma frame export plus captured screen, one image per locale) so a refresh takes minutes, not an afternoon.
- Version-control the Figma file and the export script alongside app code so screenshot history lines up with release history.
A/B testing and per-audience pages
You do not have to guess which frames convert:
- Product Page Optimization (PPO) in App Store Connect runs up to 3 treatments against your live page for up to 90 days, then you apply the winner. Give each treatment at least a week before you trust it; weekly variance can fool you, and statistical confidence usually needs meaningful install volume.
- Custom Product Pages (CPP) let you ship up to 70 alternate pages (Apple doubled the cap from 35 in October 2025), each with its own screenshot set and a deep link, so a paid campaign or a specific keyword can land on tailored frames. CPPs are for targeting; PPO is for testing.
Common mistakes
- Walls of marketing text over the screen. The frame should be roughly 80% real product, not 80% caption.
- No caption at all. Users do not interpret a bare screen; the caption is the bridge between their need and your UI.
- Different background colors across frames. Each looks “designed” in isolation and chaotic in a row.
- Mockup phones with hands. The App Store already frames screenshots; nested chrome is noise.
- Skipping localization. A native-language caption plus a quick in-screen translation converts noticeably better than English everywhere.
- Optimizing for full-size display only. Always preview at thumbnail size; that is what most search users actually see.
FAQ
- How many screenshots can I upload, and do I need all 10?: Up to 10 per localization, but six strong frames beat ten mixed ones. Apple does not penalize fewer slots, and most viewers scroll only the first three to five.
- What is the single most important dimension to design at?: The 6.9-inch iPhone portrait size, 1320 x 2868, as of June 2026. App Store Connect scales it down to older iPhones; you only need a separate set for iPad 13” and (if you ship visionOS) Vision Pro.
- Device frames or full bleed?: Either, but stay consistent. Apple’s own apps lean full-bleed; many indie apps keep device frames for clarity. Pick one and hold it across all slots.
- How do I A/B test screenshots safely?: Use PPO (up to 3 treatments, up to 90 days). Run each variant at least a week, and do not call a winner on a few days of noisy traffic.
- How often should I refresh?: At every major UI change, or every 4 to 6 months, whichever comes first. Screenshots that no longer match the live UI draw “the app looks different than the listing” reviews.
- Can I use AI-generated illustrations?: Sparingly, and only for backgrounds or decorative elements. The screen content must be your real UI; AI-rendered fake screens usually fail review and tank trust.
- Should I show user data?: Use realistic fake data, never lorem ipsum and never real user data. Names like “Alex Morgan” and “Sam Chen” read as real without pointing at a specific person.
Related
- In-app purchase pricing strategy for indie apps
- Writing your App Store listing so people actually install
- What an indie developer should prepare before launching on the App Store
- App Store review — the rejection reasons you can avoid in advance
Tags: #Indie dev #App Store #Launch #design