App Store Screenshots That Convert: 2026 Sizes & Copy
By Yogesh Devaliya
Published · Last updated
Open the App Store on your phone and search for an app in your category. Do not tap anything. Look at the result card.
You get an icon, a name, a rating, and two or three screenshots. That is the listing for most people. Description, reviews, and the rest of the gallery sit behind a tap a lot of visitors never make.
If those first frames do not answer “what do I get if I install this?”, the rest of your ASO work is decorating a page nobody finishes.
This is the practical version of how to create App Store screenshots that convert in 2026: current iPhone sizes, the first-three-frame order, benefit copy, ASO, tests, and localization. Cross-check pixel specs in the size guide. The words on the frames have their own post: screenshot copy that increases downloads.
When you are ready to build the files, Nakxi’s App Store screenshot generator exports App Store Connect sizes from one canvas. The craft below is what you put on that canvas.
Table of Contents
- Why App Screenshots Matter for ASO
- What Makes App Screenshots Look Premium
- What changed in screenshot design in 2026
- Step 1 — Use the Right Screenshot Size
- Step 2 — Use Device Mockups
- Step 3 — Focus on Benefits, Not Features
- Step 4 — Use Clear Typography
- Step 5 — Maintain Visual Consistency
- Step 6 — Apply an ASO Screenshot Strategy
- Step 7 — A/B Test Your Screenshots
- Step 8 — Localize Your Screenshots
- Step 9 — Use the Right Screenshot Tool
- Common Mistakes to Avoid
- Design Checklist
- FAQ
Why App Screenshots Matter for ASO
App Store Optimization is usually described as keywords. Keywords get you onto the results page. Screenshots decide whether anyone installs once you are there.
That distinction matters because the stores do not rank screenshots the way they rank a title. They rank listings that convert. Conversion is a quality signal. If two apps target the same query and one turns visitors into installs at a much higher rate, that listing tends to keep the impression share.
Screenshots are the fastest quality signal on the page:
- They show up in search before the product page opens
- They explain the product without a “Read More” tap — SplitMetrics has long reported that only a small slice of visitors expand the description
- Apple can OCR caption text, so the words on the frames also reinforce relevance
- Google Play explicitly asks developers to put real UI in the first three screenshots for featured placements
If you are still mapping how screenshots sit inside the wider ASO loop, start with what ASO is and how screenshots affect it. This page is the build guide.
What Makes App Screenshots Look Premium
“Premium” here is not gradients and 3D phones. It is whether a stranger can read the listing at arm’s length.
| Element | What to actually do |
|---|---|
| Layout | One headline, one device, leftover space. If a second caption is competing with the UI, delete it. |
| Hierarchy | Headline first, UI second, badges last. Search thumbnails kill everything in the middle. |
| Color | Two or three colors that match the app, not a new palette invented for the store. |
| Type | Heavy enough to survive a 200px-wide preview. Thin fonts disappear. |
| Device frame | Same model, same angle, across the set. Mixed mockups look like two teams shipped the listing. |
| Message | An outcome, not a feature label. “Never miss a bill” beats “Smart notifications.” |
A working canvas split I keep coming back to: roughly 15% headline / 65% device / 15% padding. That is craft, not a store rule. Below about 50% device, the UI is unreadable. Above about 75%, the headline has nowhere to sit. The longer version of this layout lives in first 3 screenshots, frame size, and copy.
Apple’s guideline 2.3.3 is the compliance version of the same idea: show the app in use. Not a splash screen. Not a logo on a gradient. Not a login wall. Apple’s 2026 guideline notes are worth a pass if your listing still looks like a template with the name swapped.
What changed in screenshot design in 2026
The conversion rules did not flip. The hardware and chrome around them did.
Sizes moved with iPhone 17. The required iPhone upload is still the 6.9-inch class, but 1320×2868 is now the sharpest match for Pro Max. 1290×2796 is still accepted. Teams still exporting “iPhone 15 Pro Max” as if it were the current flagship are a year behind App Store Connect.
iOS 26 reskinned system UI. Liquid Glass makes tab bars and navigation chrome translucent. A listing shot on last year’s opaque bars looks like a different app the moment someone installs. The refresh window and capture notes are in iOS 26 Liquid Glass and iPhone 17 screenshots.
Caption-first still wins in search. Device-only screenshots look clean on a Figma artboard and vanish in the search strip. Benefit headlines on frames 1–3 are still the pattern you see on listings that hold attention. We wrote up the recurring patterns — without invented lift percentages — in screenshot patterns among top-ranking apps.
Localization is no longer optional if you rank outside English. US searchers are picky about titles and snippets; non-English markets are picky about whether the screenshots are even in their language. Caption-only translation is the minimum. The workflow is in App Store localization for 2026.
Trends worth ignoring: seasonal color-of-the-year palettes, glassmorphism piled on top of Liquid Glass, and “AI-generated screenshot sets” that do not show your UI. Stores reward recognizable product, not a new aesthetic every quarter.
Step 1 — Use the Right Screenshot Size
Wrong dimensions get you a rejection or a soft, upscaled mess. Design at the largest size you need, then scale down.
App Screenshot Size Reference (2026)
| Platform | Size | Notes |
|---|---|---|
| iPhone 6.9” (required) | 1320 × 2868 | Best match for iPhone 17 Pro Max. Apple also accepts 1290 × 2796 and 1260 × 2736 in this slot. |
| iPhone 6.9” (accepted) | 1290 × 2796 | Still valid. Fine if you are not rebuilding the set this cycle. |
| iPhone 5.5” (optional) | 1242 × 2208 | Only if you still care about older Plus-class devices. |
| iPad 13” (required if iPad) | 2064 × 2752 | 2048 × 2732 is also accepted in the same slot. Do not mix both in one localization. |
| Google Play portrait | 1080 × 1920 | Standard Android screenshot. Play also accepts other 16:9 / 9:16 sizes in range. |
| Google Play feature graphic | 1024 × 500 | Separate from screenshots. Required if you want to be featured. |
Apple scales the 6.9-inch set down to smaller iPhone classes if you skip those uploads. That is usually the right trade. Pixel-perfect 6.3” and iPhone Air sizes only matter if those devices are a real slice of your audience.
Official sources, not a blogger’s spreadsheet:
On Android, the same story at Play sizes: how to create Play Store screenshots.
Step 2 — Use Device Mockups
A raw simulator export tells people you shipped the listing from Xcode. A current device frame tells them this is a phone app, on a phone they recognize.
Use the same model and angle across the set. Match the bezel to the palette if you can (black frame on dark UI, light frame on light UI). Do not stretch the UI to fill a frame — crop or pick a different capture.
Skip mixing flat screenshots with 3D hero shots in the same carousel. One of them will look like leftover marketing.
Frames go stale fast. iPhone 15 bezels on an iOS 26 listing are a quiet trust leak. If you need current iPhone 17 and Android frames without hunting mockup packs, that is what the app mockup generator is for.
Step 3 — Focus on Benefits, Not Features
Developers write the settings screen. Users buy the Tuesday-night outcome.
| Feature caption (skip) | Benefit caption (use) |
|---|---|
| Smart Notification System | Never miss an important update |
| Advanced Analytics Dashboard | See exactly where your money goes |
| Multi-device Sync | Pick up where you left off |
A feature describes what the app has. A benefit describes what the user gets. If you cannot finish the sentence “After I install this, I will be able to…”, the headline is not ready.
Recommended Screenshot Flow (5-Screen Strategy)
| Screenshot | Job | What belongs here |
|---|---|---|
| 1 | Promise | Strongest outcome. This is what search shows. |
| 2 | Proof | The one screen that makes the promise believable. |
| 3 | Payoff | Result, progress, or “after” state. |
| 4 | Trust | Rating, review excerpt, user count — only if it is real. |
| 5 | Invite | Who it is for, or a calm next step. Not “Download now” in 80pt. |
Most people never see 4 and 5. Spend the afternoon on 1–3. Category examples if you want to steal a layout rather than a blank canvas: fitness app templates, dating app templates, digital wallet templates, crypto wallet templates. Those categories already attract listing traffic on Nakxi; the structure above still applies.
For live listings instead of templates, browse ScreenVault.
Step 4 — Use Clear Typography
Store search shrinks your screenshot to a strip. Design for that strip, then check the full canvas.
- One headline, 4–7 words, high contrast
- Supporting line optional, and shorter than the headline
- Two type styles across the whole set, not per slide
- No light or hairline weights
- Squint test: if you cannot read it at ~200px wide, rewrite or enlarge
Fonts that survive thumbnail size:
- Inter — boring on purpose. Holds up small.
- Outfit — a bit more geometric, still safe for headlines
- Plus Jakarta Sans — similar job, slightly friendlier
Script, serif display, and ultra-condensed faces fail this test. So does putting the headline in your brand font just because the brand font exists.
Play’s own note is useful even on iOS: if you use a tagline, keep it from eating the image. Their screenshot guidance caps promotional text at about 20% of the image.
More on caption length and OCR: App Store screenshot text best practices and the copy guide.
Step 5 — Maintain Visual Consistency
Five screenshots should look like one product, not five Dribbble shots.
Lock these before you design slide 2:
- Palette (two or three colors)
- Type family and headline size
- Device model and angle
- Headline placement (top vs. overlay — pick one)
- Background treatment
Open the set as thumbnails, side by side. If any frame could belong to a competitor, it does not belong in your listing.
Inconsistency is the tell that the listing was assembled in a hurry. Users read that as quality, whether that is fair or not.
Step 6 — Apply an ASO Screenshot Strategy
Treat screenshots as part of the listing, not a design task that starts after metadata is “done.”
ASO screenshot best practices that actually move the needle:
- Screenshot 1 carries the keyword-shaped promise. If people find you for “expense tracker,” frame 1 should look like an expense tracker, in words and UI — not a generic dashboard.
- Tell one story across the set. Frame 2 should prove frame 1, not introduce a second product.
- Show the differentiator once. If the only reason you exist is offline mode, widgets, or a particular workflow, that belongs on frame 2 or 3, not buried on 7.
- Keep captions short enough for OCR and humans. Apple reads text in images. Keyword stuffing captions is still stuffing. One relevant phrase per frame is plenty.
- Match title, subtitle, and screenshots. A subtitle that says “invoice scanner” next to screenshots of a social feed is how you burn conversion on traffic you paid to rank for.
The compounding loop is boring and real: clearer screenshots → more installs per impression → the store has less reason to stop showing you. I will not invent an “8% vs 4%” lift. Your category baseline is whatever App Store Connect and Play Console already show you. Improve that number; do not chase a blog percentage.
Shorter companion if you only want the rules of thumb: App Store screenshots best practices. The ASO-plus-design pairing is in ASO and screenshot design.
Step 7 — A/B Test Your Screenshots
A first version can be “good.” A converting version is usually the third or fourth headline on frame 1.
Native tools, not a third-party guessing panel:
- App Store — Product Page Optimization (up to three treatments vs original)
- Google Play — Store listing experiments
How to not waste a month:
- Change one thing. Headline on screenshot 1, or palette, not both.
- Run 2–4 weeks unless traffic is huge. A weekend test is noise.
- Optimize conversion rate, not impressions on the variant.
- Write down what you tried. ASO memory is worse than we admit.
Start with screenshot 1. It is the only frame most searchers see.
Custom Product Pages (iOS) and Custom Store Listings (Play) are a different lever — paid traffic and specific audiences. If that is the job, use CPP / CSL screenshot design, not this default listing set.
Step 8 — Localize Your Screenshots
Translated metadata with English screenshots is a half-shipped listing. People notice.
Minimum viable localization:
- Translate captions for your top traffic countries
- Keep the same layout so you are not redesigning per language
- Swap social proof if the original number is US-only
- Watch line length. German and French will break a 5-word English headline.
You do not need twenty locales on day one. Cover the markets already sending impressions. Search Console will tell you; vanity locale lists will not.
In Nakxi, caption translation is a pass over the existing set rather than a rebuild — App Store localization if you want that workflow instead of a design-tool copy-paste.
Step 9 — Use the Right Screenshot Tool
General design tools will produce a listing. They will also make you babysit sizes, frames, and exports every time Apple adds a slot.
What the job actually needs:
- Current platform presets (do not type 1320×2868 from memory)
- Device frames that match this year’s phones
- Resize to every required slot from one design
- Type and layout control for captions
- PNG/JPEG at store resolution
| Tool | Honest fit | Localization |
|---|---|---|
| Nakxi | ASO workflow: screenshots, templates, metadata, export | Built in |
| AppScreens | Automation-heavy teams | Strong |
| Previewed | 3D / motion mockups | Manual |
| The App Launchpad | Template volume | Yes |
| Figma + plugins | Full custom control | Manual |
If you are comparing screenshot generators rather than learning the craft, AppScreens alternatives is the shopping post. Why Canva fights this job is the “we already have a design tool” post.
Create App Store Screenshots →
Common Mistakes That Make Screenshots Look Cheap
| Mistake | What it costs you |
|---|---|
| Feature dump on one frame | People stop reading. One idea per screenshot. |
| Raw simulator captures | Looks unfinished. Frame it or crop with intent. |
| Headline unreadable at search size | Frame 1 is wasted. That is most of your traffic. |
| Splash / logo / login as screenshot 1 | Against Apple 2.3.3, and it converts poorly. |
| Mixed device models | Reads as a collage, not a product. |
| Stale OS chrome | iOS 26 vs last year’s bars. Quiet uninstall of trust. |
| Fake reviews or inflated counts | Short-term clever, long-term review risk. |
| English-only captions in non-English rankings | You already paid for the impression. |
The longer autopsy is screenshot mistakes creators ignore. Fixing three items in the table above is usually enough to see a movement in conversion. You will not get a movie-trailer before/after. You will get a less embarrassing listing.
Professional Screenshot Design Checklist
Run this against the export folder before App Store Connect:
- 6.9-inch iPhone upload is 1320×2868 (or an accepted 6.9” size), not an old 6.5” export
- iPad 13” uploaded if the app runs on iPad (2064×2752)
- Play set at 1080×1920 if you ship Android
- Frame 1 states the outcome in 4–7 words
- Frames 1–3 show real in-app UI (Apple 2.3.3)
- Same device, type, and palette across the set
- Headline survives a ~200px-wide preview
- Title / subtitle / screenshots tell the same story
- Captions localized for the markets that already send traffic
- PPO or Play experiment queued for screenshot 1
If you want a second pair of eyes on a live listing, Analyze My App scores a store URL. It will not replace Product Page Optimization. It will catch the obvious holes.
Browse App Store screenshot templates if you would rather start from a layout than a blank canvas. Android: Play Store templates.
FAQ
How many screenshots should I upload to the App Store?
Apple allows 10. Play allows 8. Five is a working minimum. The first two or three are the ones search actually shows. Extra frames are for people who already opened the page — still useful, not where you should spend the week.
What App Store screenshot size should I use in 2026?
The 6.9-inch iPhone class is the required iPhone set. Prefer 1320 × 2868. 1290 × 2796 is still accepted. iPad apps also need 2064 × 2752 for the 13-inch slot. Full table: App Store screenshot sizes 2026.
Do App Store screenshots affect rankings?
Indirectly. They are not a keyword field. They change conversion, and conversion changes how much the store wants to show you. That is the whole ASO screenshot argument, without the mythology.
Should App Store screenshots be portrait or landscape?
Portrait, unless the product is landscape-native. Do not mix orientations in one listing.
What fonts work best on App Store screenshots?
Heavy sans-serifs: Inter, Outfit, Plus Jakarta Sans. Two styles max. If it fails at thumbnail size, it fails in the store.
Do screenshots need to show the real app?
Yes. Guideline 2.3.3: app in use, not title art, login, or splash. Keep them current under 2.3. Template carousels with a logo swap are a review and conversion problem.
How often should I update App Store screenshots?
When the UI changes, when a new size class ships, and when OS chrome users will notice (Liquid Glass is the 2026 example). Test screenshot 1 at least quarterly.
Should I use video previews instead of screenshots?
Video helps games and highly interactive apps. It does not replace screenshots. Optimize the stills first. App previews are a production project; screenshots are a listing you can ship this week.
Conclusion
Converting App Store screenshots answer one question before the user scrolls: why install this?
Frame 1 does most of that work. Current sizes, a real device, a short outcome headline, and a set that looks like one product will beat a prettier carousel that starts with a logo.
Work the steps in order — size, frame, benefit copy, consistency, ASO, a real A/B test, then localization. Skip the ones that do not apply to your market. Do not skip frame 1.
Ready to build the set: App Store screenshot generator. Templates if you want a head start: App Store and Play Store.