How to Make App Store Screenshots That Convert in 2026

Apple's research shows the first 3 App Store screenshots drive 60% of install decisions. The required iPhone 6.7" size is 1290 x 2796 pixels. You can upload up to 10 screenshots per device, and the first 2 appear in search results before users tap through. Get the first 2 right and conversion can climb 25% or more. Get them wrong and your install rate sits flat regardless of how good the product is.

This is the 2026 playbook: exact sizes, a 7-screenshot framework, copy patterns that actually convert, localization, A/B testing, the 8 rejection reasons that kill submissions, and an honest take on the tools that get you there fastest.

The 2026 App Store screenshot sizes you need

Before any design decisions, get the dimensions right. Apple rejects submissions even one pixel off. Below are the required sizes for 2026.

iPhone screenshot dimensions (2026, post-iPhone 17 launch)

iPad screenshot dimensions (2026)

If you only have time to make one size, make 1290 x 2796 (iPhone 6.7"). Apple scales it down for smaller devices, and it covers the vast majority of recent iPhones. For the full reference including Apple Watch sizes, see the App Store Screenshot Dimensions 2026 guide.

Format requirements

App Store screenshots must be PNG or JPEG, RGB color space, with no transparency or alpha channels. Max file size is 8 MB per screenshot. Apple recommends PNG for screenshots with text and UI elements because JPEG compression artifacts show up on sharp edges.

Why App Store screenshots actually move the needle

App Store Optimization (ASO) practitioners track three conversion metrics: tap-through rate (search result to product page), install rate (product page to install), and stay rate (install to active use). Screenshots affect the first two heavily.

Apple's own App Store Marketing Tools documentation treats screenshots as the single most important creative asset in a listing. Independent ASO studies (StoreMaven, AppFollow, Storemaven 2024) consistently show that the first two screenshots account for the majority of the install decision because users decide whether to tap through within 7 seconds of seeing them in search.

The practical implication: don't optimize equally across all 10 screenshot slots. Optimize screenshot 1 and 2 disproportionately, because they do the heaviest lifting.

The 7-screenshot framework

Most high-converting App Store listings follow a similar narrative arc. Here is the 7-screenshot framework that has emerged as the de facto pattern. Use as many slots as you need; you do not need to fill all 10.

Screenshot 1: The lead value prop

Answers the question "what does this app do?" in under 2 seconds. Show the core screen that makes the app's purpose obvious, with a 3-to-5-word headline naming the outcome (not the feature).

Examples of strong screenshot 1 headlines:

• "Track every expense automatically"
• "Read 60+ books in a year"
• "Calls translated in real time"

Examples of weak screenshot 1 headlines:

• "Welcome to the app" (says nothing)
• "AI-powered intelligent finance assistant" (jargon)
• "The all-in-one platform" (vague)

Screenshot 2: The differentiator

Now that the user understands what the app is, screenshot 2 shows why this app, not a competitor. If you have a clear differentiator (privacy, speed, design, price, AI), this is where it goes.

Screenshots 3 to 5: Three key features

One feature per screenshot. Show the feature in use with realistic data, paired with a benefit-driven headline.

Pattern that works: "[Verb] [outcome] [qualifier]."

• "Pay anyone in seconds."
• "Find quiet places nearby."
• "Auto-tag receipts forever."

Screenshot 6: Social proof

Reviews, ratings, press mentions, user counts. If a recognizable publication has written about the app, quote them. If the app has 100,000+ active users, say so. If it has 4.8 stars from 50,000 ratings, show it.

This screenshot moves conversion on the margin. It is most useful for apps in crowded categories where users are evaluating multiple options.

Screenshot 7: The close

A clean restatement of the value prop with a soft call-to-action. Often a brand shot with a tagline. Sometimes a screenshot of the onboarding screen, signaling that getting started is easy.

This is also the right slot for pricing context if the app is freemium ("Free to try. Pro from $4.99/mo.") though Apple discourages literal pricing text in screenshots.

Headline copy that converts

Headlines on App Store screenshots are not headlines like a blog post. They are closer to billboard ads: read in under 2 seconds at a 200-pixel screen height. The patterns that work are tight.

The 3 patterns that convert

Outcome-led: "[Verb] [outcome] in [time]." Examples: "Track expenses in 30 seconds." "Sleep better in 7 days." "Build apps in an afternoon." Differentiator-led: "Finally, [a thing] that [unexpected quality]." Examples: "Finally, a calendar that respects your time." "Finally, expense tracking that doesn't suck." Social-proof-led: "Loved by [number] [audience]." Examples: "Trusted by 2,000+ indie makers." "Used in 50,000+ classrooms."

Length and typography rules

Keep headlines to 5 words or fewer. Anything longer becomes unreadable at the size Apple renders screenshots in search results. Use a font size of at least 80 pt in the 1290 x 2796 px canvas, which is roughly 12 to 14% of canvas height. Bold weights survive compression better than light weights.

Maximum readable line length is about 25 characters. If the headline wraps to 3 lines, it is too long.

Avoid these copy mistakes

• Pricing claims ("Free!" "$0.99 only!") often get rejected and are easy to misuse.
• Feature lists ("Notifications, widgets, dark mode, sync")
• Marketing speak ("Revolutionary," "Game-changing," "Next-generation")
• Comparative claims about competitors by name
• Promises Apple considers misleading ("#1 app," "Best in class")

Device frames: which ones, when

Plain screenshots look like bug reports. Device frames give context, signal product polish, and let users mentally project themselves using the app. They consistently outperform unframed screenshots in A/B tests.

The 2026 device frame rules:

• Use a current frame. iPhone 12 or 13 frames in 2026 make the app look abandoned. Use iPhone 17, iPhone Air, or iPhone 16 Pro frames. The visual difference (Dynamic Island, titanium edge color, the iPhone Air's thinness) signals freshness.
• Match the frame to the audience. Pro-leaning apps use iPhone 17 Pro or 16 Pro frames. Consumer apps work fine with iPhone 17 or iPhone Air. Watch apps need an Apple Watch frame in at least one screenshot.
• Keep the frame consistent across screenshots. Mixing iPhone 17 Pro and iPhone 14 frames in the same listing looks careless. Pick one frame for the iPhone size and stick with it.
• Don't overdo bezel realism. A clean, slightly stylized frame reads better at thumbnail size than a hyper-realistic one with reflections and shadows. The screenshot itself should be the hero.

You can add iPhone 17 Pro Max, iPhone Air, iPhone 16 Pro, and iPhone 15 frames to any screenshot in seconds using the App Store screenshot generator or the iPhone mockup generator. No Photoshop.

Backgrounds: gradient, solid, or photo

Backgrounds do three things: separate the device frame from the canvas, add brand color, and provide negative space for the headline. They should not compete with the app UI for attention.

What works

• Soft gradients (the most common choice in top-ranking apps). Two-tone gradients in brand colors. Subtle, calm, never neon. Screenhance ships 50+ gradient presets calibrated for this use.
• Solid brand colors. Cleaner than gradients, works particularly well for utility and developer-tool apps where the audience prefers minimalism.
• Mesh or aurora gradients. Trendier in 2026. Higher visual interest, works for design-forward and creative apps.

What to avoid

• Photographic backgrounds. They almost always compete with the app UI and confuse the thumbnail.
• Patterns (dots, grids, abstract shapes). Same problem.
• Pure white or pure black. Looks unfinished and signals the app was thrown together.
• Neon, fluorescent, or oversaturated colors. They survive compression badly and look amateurish at small sizes.

Background-to-frame contrast

The device frame should have clear separation from the background. Light frame on light background (or dark on dark) loses the silhouette of the device at thumbnail size. Aim for a luminance difference of at least 30% between background and frame edge.

Localization: which markets, what to translate

If the app supports more than one language, the App Store lets each language have its own screenshot set. Localizing screenshots is one of the highest-ROI ASO moves available, because tap-through rate climbs sharply when users see headlines in their native language.

Which markets to prioritize

Most international iOS install volume comes from these 8 languages: English (US), English (UK), Spanish, French, German, Italian, Japanese, Simplified Chinese. If the app is in the App Store globally, localizing screenshots for these 8 covers the majority of addressable downloads.

Beyond the top 8, prioritize markets where the app already has install volume (visible in App Store Connect → App Analytics → Sources). Localizing markets that already convert organically is more impactful than localizing markets that don't.

What to localize

• Headline text in screenshots: always. This is 80% of the win.
• In-app UI text shown in screenshots: always. Mismatched UI language (English UI with French headline) reads as careless.
• Currency and units shown in screenshots: ideally. Show €, £, ¥ for the matching market.
• Cultural references: optionally. A US-coded photograph of a person may not land in Japan. Use abstract or universal imagery for markets where culture might mismatch.

RTL languages (Arabic, Hebrew)

For Arabic and Hebrew, the entire screenshot layout flips: device on the right, headline on the left, in-app UI right-to-left. Apps that ship to Arabic-speaking markets without RTL screenshots leave conversion on the table. The App Store screenshot localization guide has the full playbook.

A/B testing screenshots

Apple's Product Page Optimization (PPO) lets you test up to 3 alternate screenshot treatments against the default for up to 90 days. This is the single most underused ASO tool available.

How to set up a useful test

1. Hold all variables constant except one. Test the headline of screenshot 1, or the background color, or the device frame. Testing multiple variables at once leaves you guessing which one moved conversion.

2. Run the test on 100% traffic. Lower traffic splits take too long to reach significance.

3. Wait for at least 5,000 product page views per variant before reading results. Less than that and the variance is too high.

4. Set a 14-to-21-day test window. Shorter than 14 days picks up weekend or weekday bias.

What to test first

• Screenshot 1 headline. Highest leverage, easiest to vary.
• Screenshot 1 device frame style (realistic vs minimal).
• Screenshot 2 angle (differentiator vs feature deep-dive).
• Background color or gradient.

What not to bother testing: subtle font weight changes, single-pixel framing adjustments, anything that won't be noticed at thumbnail size.

The 8 most common rejection reasons

Apple's App Review team rejects screenshots that violate the App Review Guidelines section 2.3 (Accurate Metadata). These are the 8 reasons that cause the most rejections.

1. Wrong dimensions. Even 1 pixel off the required size. Always export at the exact pixel count.

2. Pricing text. "Free," "$0.99," "Save 50%," "Limited time." Apple wants pricing controlled through App Store metadata, not screenshot artwork.

3. Comparative claims. Naming a competitor or claiming "best" or "#1" without evidence.

4. Misleading content. Screenshots showing features the app doesn't actually have, or UI that hasn't shipped yet.

5. Beta or unreleased content. Screenshots from a TestFlight build with content not in the public release.

6. External platform references. "Available on Android," "Use with Apple Watch and Galaxy Watch." Apple doesn't accept screenshots that cross-promote competing platforms by name.

7. Trademark or copyright violations. Brand logos used without permission, copyrighted imagery, recognizable third-party content.

8. Status bar manipulation. Custom or fake status bars with edited time, signal, or battery. Apple wants the actual device status bar or none at all.

Most rejections come from dimensions and pricing text. Verifying both before upload eliminates 60% of resubmit cycles.

Accessibility in screenshots

App Store screenshots that respect accessibility convert better in older demographics and in regulated markets. The basic checklist:

• Headline contrast ratio of 4.5:1 or higher against the background. The WebAIM contrast checker is the standard reference.
• Headline font size of at least 80 pt in the 1290 x 2796 canvas. Smaller than 80 pt is unreadable at thumbnail size for users with low vision.
• No critical information communicated through color alone. If the screenshot relies on red-vs-green to convey meaning, color-blind users miss it.
• Real, non-placeholder content. Lorem ipsum and "John Smith" placeholder text both signal a careless product and fail screen-reader-equivalent visual parsing.

These are not regulatory requirements (yet) but they correlate with higher tap-through rates in research-backed ASO studies.

The 3 tools that get you there fastest

There is no single right tool. The honest comparison:

Xcode Simulator (for raw screenshots)

Best for capturing the underlying app screen at exact device dimensions. Free, comes with Xcode. Cmd + S in the simulator window saves a PNG at the right pixel count.

Limits: only captures the app screen, not the framed marketing version. You will need a separate tool to add device frames, backgrounds, and headlines.

Screenhance (for the framed marketing screenshots)

Built specifically for the App Store screenshot workflow. Drop in the simulator output, pick a device frame and gradient, add headlines, and export every required Apple size (6.9", 6.7", 6.5", 5.5", iPad 13", Apple Watch) from one design. Multi-language export in one pass. Free for 3 exports per month. Pro at $8/month, or a one-time $6 Week Pass for a single launch.

Honest take: if the app ships in one language and only needs the 6.7" size, the Week Pass is the cheapest path to a polished set. If the app ships in 5+ languages, Pro pays for itself in the first launch.

Figma (for full creative control)

The most flexible option if the team already lives in Figma. Set up artboards at each required dimension, build the screenshots manually, export. Strong if the marketing team has design capacity. Slow if the founder is doing it themselves.

Most indie launches use a combination: Simulator for the underlying app screen, Screenhance for the framed marketing version, Figma only when the design needs something unusual.

App Store screenshot examples worth studying

The fastest way to internalize what good looks like is to study top-ranking apps in your category in App Store Connect's "Apps Like Yours" view. Patterns that recur across categories:

• Finance (Wise, Revolut, Cash App): minimal backgrounds, outcome-led headlines, large numbers in screenshots ("$2,431 saved").
• Productivity (Notion, Linear, Things): clean UI screenshots, soft pastel backgrounds, feature-led screenshots 3 to 5.
• Health and fitness (Strava, Apple Fitness, Headspace): photographic backgrounds (rare exception to the no-photo rule) for emotional connection, large progress numbers.
• Games (every breakout casual game): chaotic, vibrant backgrounds, characters bursting out of the device frame, action-led headlines.

Save the listings that convert you to download. The shortcut is to study what already works in your specific category, not generic ASO advice.

Frequently Asked Questions

How many App Store screenshots should I upload?

Upload between 5 and 8 screenshots. Apple allows up to 10, but most top-converting apps use 5 to 8 because each additional screenshot dilutes the focus. Quality beats quantity. The first 2 screenshots do most of the work; the rest support the close.

What size should App Store screenshots be in 2026?

The required primary iPhone size in 2026 is 1320 x 2868 pixels (the 6.9" display covering iPhone 17 Pro Max, 16 Pro Max, and 15 Pro Max). For iPhone Air, provide 1260 x 2736 px (6.5"). For iPad, use 2064 x 2752 px (iPad Pro M4 13"). Apple scales down for smaller devices automatically.

What should the first App Store screenshot show?

Screenshot 1 should answer "what does this app do?" in under 2 seconds. Show the core screen that makes the app's purpose obvious, paired with a 3-to-5-word outcome-led headline ("Track expenses in 30 seconds," not "Welcome"). This is the screenshot that appears in App Store search results and drives 60% of the install decision.

Are device frames required for App Store screenshots?

Device frames are not required by Apple, but every meaningful ASO study shows framed screenshots outperform unframed ones. Plain screenshots look like bug reports. Framed screenshots add context, signal product polish, and let users picture the app on their device.

How do I make App Store screenshots without a designer?

Use a purpose-built tool like the App Store screenshot generator. The workflow is: capture screens in Xcode Simulator, drop into the screenshot tool, pick a device frame and gradient, add a headline, export every required Apple size from one design. Total time is roughly 30 seconds per screenshot once the template is set up.

Can I A/B test App Store screenshots?

Yes. Apple's Product Page Optimization (PPO) lets you run up to 3 alternate treatments against the default for up to 90 days. Test one variable at a time (headline, background, device frame), require at least 5,000 views per variant, and let the test run for 14 to 21 days before reading results.

What gets App Store screenshots rejected by App Review?

The 4 most common rejection reasons in 2026 are wrong dimensions (1 pixel off the required size), pricing text in screenshots, comparative claims naming competitors, and misleading content showing features the app doesn't have. Verifying dimensions and removing all pricing text before upload eliminates the majority of rejections.

Related reading

• App Store Screenshot Dimensions 2026: Every Size in One Chart
• App Store Screenshot Localization Guide
• ASO Screenshot Best Practices 2026
• App Store Screenshot Generator
• Play Store Screenshot Generator
• iPhone Mockup Generator

Conclusion

App Store screenshots are the highest-leverage piece of creative in an iOS launch. Two screenshots out of ten do most of the work. A 7-screenshot framework, outcome-led 3-to-5-word headlines, current-generation device frames, calm gradient backgrounds, and localized copy for the top 8 markets cover the playbook for 2026.

The technical floor is exact 1290 x 2796 dimensions, RGB color space, and no pricing text. The ceiling is well-tested copy in each market and A/B-tested screenshot order. Most apps stop at the floor. The ones that move install rate by 25% or more push to the ceiling.

When the playbook is ready, the App Store screenshot generator ships every required size from one design in minutes. Start with the first 2 screenshots; everything else follows.