App Store screenshots: sizes, best practices, and examples for 2026.

An App Store screenshot is a portrait image attached to an app's App Store or Google Play product page that previews the app's user interface and value proposition. Apple App Store accepts up to 10 screenshots per device family per locale, and Google Play accepts up to 8. The first three appear in App Store search results and on the small product card preview, which is why they carry the majority of install conversion lift.

Modern App Store screenshots are not raw OS captures. They are composed marketing units — a real product screen layered with a short headline, a benefit clause, and brand framing — exported in the exact pixel sizes Apple and Google require for upload to App Store Connect or Google Play Console. A 2022 capture of a Settings screen with no overlay is a screenshot in the literal sense but does not satisfy the format conventions buyers and the algorithm expect in 2026.

Throughout this guide, "App Store screenshot" refers to the composed marketing version. Where Apple's official Apple Developer documentation specifies size, slot, or format requirements, those rules are quoted directly.

Across AppGrowKit's analysis of customer App Store listings, screenshots consistently outperform every other listing element as a conversion lever. Ranking metadata (title, subtitle, keyword field) determines whether you appear in front of a searcher; screenshots determine whether the searcher taps Install. Across both store algorithms, the first three screenshots do roughly 80% of the conversion work — by the time a user scrolls to screenshot five, only about a quarter of viewers are still engaged.

The implication is simple: if you have one hour to spend improving a listing, spend it on the first three screenshots. Specifically:

• Screenshot 1 answers the question "what is this app?" — the single most important frame on the page.
• Screenshot 2 answers "what does it look like in use?" — typically the strongest interaction, animation, or interface flow.
• Screenshot 3 answers "why is this better than alternatives?" — a concrete benefit, integration, or unique feature.

Screenshots four and five are the deeper layer for users who tapped through the small-card preview into the full product page. They should round out the story (use cases, social proof, secondary features), but cannot rescue a weak first three.

Apple updates accepted screenshot slot families with each major iPhone launch. As of 2026, App Store Connect prioritizes the largest currently-shipping device family for the primary preview. The tables below cover every iPhone and iPad slot Apple still accepts; deeper per-device guides are linked alongside.

iPhone screenshot sizes

iPad screenshot sizes

Practical rule: upload one set at the largest current iPhone size (1290 × 2796 minimum, 1320 × 2868 recommended) and one set at the largest iPad size (2064 × 2752). App Store Connect uses these as the canonical sets and scales down for smaller devices in most cases. Only upload to additional slots if you have device-specific screenshots that demonstrably perform better.

Localization adds another dimension. Apple recommends submitting localized screenshot sets in the regions where you target installs. Listings localized into the 12 top App Store languages typically grow installs 26-47% in those markets in AppGrowKit's tracking of multi-locale launches. See the localized App Store screenshots guide for the per-language workflow.

These rules come from analyzing dozens of customer App Store listings and the screenshot iterations that did or did not move conversion. They are deliberately framework-level — every category needs its own creative direction, but these rules apply across categories.

Rule 1 — Lead with the outcome, not the feature

The first screenshot's headline should describe what the user gets, not what the app does. "Plan three meals in 60 seconds" outperforms "AI meal planner with smart suggestions" almost every time. Outcome framing answers the unspoken question — "why should I install this?" — in the user's language, not the product team's language.

Rule 2 — One idea per screenshot

Each screenshot should make exactly one claim. Listings that try to cram three features into screenshot one consistently underperform focused screenshots. Users reading at 200ms per frame cannot parse three ideas; they bounce. If you have five features worth showing, give each its own frame and trust the carousel.

Rule 3 — Show the interface, not just decoration

Screenshots dominated by lifestyle photos, illustrations, or branded backgrounds with the app UI as a small phone mockup underperform layouts where the app interface is the primary visual subject. Users want to see what they will use. The decoration should frame the interface, not replace it.

Rule 4 — Match the listing's promise

If your title says "fast" and your screenshots show a 5-step setup flow, you have an alignment problem. Screenshots are the visual proof of the listing copy's claim. Audit your title, subtitle, and first screenshot together and confirm they tell the same story. Mismatch is the silent conversion killer most teams never check for.

Rule 5 — Localize the headlines, not just the metadata

Localizing the App Store description while leaving English headlines on the screenshots is the most common partial-localization mistake. Users in non-English markets convert at meaningfully lower rates when the screenshot copy stays in the original language. If you localize for a market, localize the screenshots too.

Uploading raw OS screenshots without overlays

A screenshot of a Settings screen with no headline, no framing, and no benefit clause is technically a valid upload but tells the user nothing. Apple's own guidelines now specifically reference "marketing screenshots" as the expected format. Raw OS captures are the format equivalent of submitting a Word doc as a resume — accepted, but a signal that the team doesn't understand the medium.

Putting the most important text in the bottom third

On the App Store search results card, only the top two-thirds of the first three screenshots is fully visible. Headlines or benefit clauses placed in the bottom third get cropped or de-prioritized visually. Move the most important text to the upper-half of every screenshot.

Reusing the same headline across all five frames

"Beautifully simple meal planning" repeated on every screenshot wastes four frames. Each headline should advance the story or address a different objection. If you can write one headline that applies to every frame, your headlines aren't specific enough.

Skipping iPad even when you support it

Apps that work on iPad but ship without iPad screenshots get a store-side ranking penalty in iPad searches and lose the iPad installs entirely. If you have any iPad layout, generate at least the primary iPad screenshot set. iPad users convert at a higher dollar value than iPhone for most paid app categories.

For most teams, the bottleneck is not strategy — it's production. A designer shipping screenshots for one device family in Figma takes roughly 4-6 hours to produce a five-frame set, and that scales linearly with localization and device variants. There are three viable approaches in 2026:

Option 1 — Hand design in Figma

Highest creative ceiling, slowest cycle time. Justified for flagship launches where the screenshots double as marketing assets used in press, App Store features, and paid acquisition. Budget 4-6 hours per device family per locale.

Option 2 — Template tools

Faster than Figma, lower creative ceiling. Template-based screenshot builders generate decent output in 30-60 minutes but the "AI screen on a phone frame with a stock background" aesthetic shows up in thousands of listings. If your category is undersaturated, this works; if you are competing in a crowded category, the templated look is a competitive disadvantage.

Option 3 — AI-assisted generation

Closest to the Figma quality ceiling at the template-tool cycle time. AppGrowKit generates polished iPhone and iPad screenshot sets from raw app screens or your existing App Store URL, with AI-written headlines that follow the framework above and exports in the exact pixel sizes Apple and Google require. The first preview generates in under five minutes; finals follow once you approve direction.

Whichever option you choose, ship the set, run a paid acquisition test against the new screenshots, and iterate based on conversion data. The first version of your screenshots is rarely the version that ships in month six.

What size should App Store screenshots be in 2026?

For iPhone, target 1290 × 2796 (accepted in the 6.7" and 6.9" slots, covers iPhone 14 Pro Max through 16 Pro Max). For iPad, target 2064 × 2752 (covers iPad Pro 13" and iPad Air). One iPhone set and one iPad set is enough for most apps.

How many screenshots should I upload?

Apple App Store accepts up to 10 per device family per locale; Google Play accepts up to 8. Ship at least three (the cards visible in search results) and ideally five (the visible set on the full product page above the fold). Ten is overkill for most apps.

Do I need different screenshots for each iPhone size?

No. Upload the largest size (1290 × 2796 minimum) and Apple scales down for smaller iPhones. Only upload device-specific screenshots if you have proof a smaller iPhone variant performs differently and is worth the extra production time.

Do screenshots need to be in PNG or JPG?

App Store Connect accepts both PNG and JPG. PNG is preferred for screenshots with sharp UI edges and text overlays — text rendering looks crisper. JPG is acceptable for photo-heavy screenshots but introduces compression artifacts on UI text.

Can I A/B test App Store screenshots?

Yes. App Store Connect supports Product Page Optimization (PPO) tests with up to three treatments running against a control. Run one variable at a time — the headline copy, the screenshot one composition, or the screenshot order. PPO reports usually need roughly 10-14 days at meaningful traffic to reach significance.

How fast can I generate screenshots with AppGrowKit?

A first preview concept generates in a couple of minutes. After you approve the preview, the full iPhone or iPad screenshot set renders in under five minutes. New accounts get 5 free screenshot credits on signup with no credit card required — Pro plans from $19/mo after that, cancel anytime.