App Store Screenshots in 2026: Sizes, Specs & Testable Ordering

Your app store screenshots are visible product-page assets for explaining the app's value and interface. This guide covers the current 2026 app store screenshot sizes for iPhone and iPad, a testable starting order, and a pre-upload checklist. Creative performance varies by category, storefront, device, and traffic source, so ordering advice is a hypothesis rather than a universal conversion formula.

The 2026 App Store screenshot sizes (spec table)

Apple accepts several exact resolutions for each display class and scales supplied screenshots for smaller devices where its reference says it can. In the common path, provide an accepted largest-iPhone set and, when the app runs on iPad, an accepted 13-inch iPad set. Do not assume there is only one valid pixel size: check the current table before every release.

The current required portrait sizes look like this:

A few rules that trip people up:

• Files must be PNG or JPEG, in the RGB color space, with no alpha channel (no transparency).
• Dimensions must be pixel-perfect — App Store Connect rejects anything off by even a pixel.
• You can upload up to 10 screenshots per localization, and a minimum of one (Apple recommends at least three).
• If your app runs on iPad, iPad screenshots are mandatory — you cannot skip them.

Tip: start with one of Apple's accepted 6.9-inch resolutions and preview every scaled result. Scaling reduces upload work, but it does not guarantee that captions, device frames, and safe areas remain ideal on every display.

These dimensions change as Apple ships new hardware, so always confirm against the current Apple Developer screenshot specifications before a release. For a maintained cross-reference, MobileAction's screenshot guide tracks each generation.

How many screenshots should you use

The technical ceiling is 10, but the useful count depends on how many distinct, accurate messages the listing needs. Three to ten can be a practical production range, not an official optimum.

On the search results page and at the top of a product page, Apple can show opening screenshots without a swipe. The visible count depends on orientation, device, and layout. Put the core proposition early, then validate that choice with a supported experiment instead of assuming a fixed swipe-through rate.

A practical distribution:

• Screenshots 1–3: introduce the core value and primary workflow.
• Screenshots 4–6: add secondary features, breadth, or substantiated reassurance.
• Screenshots 7–10: use only when they add a distinct, useful message.

If you can produce only three strong frames, prioritize clarity and accuracy in those three, then measure whether more frames help.

A screenshot order to test

Order is a controllable creative variable. Core value, primary workflow, substantiated proof, feature depth, CTA is one starting structure to test; it is not the only order that can work.

Screenshot 1 — the hook

Lead with your single strongest benefit, stated in plain language, paired with a clean hero shot of the app. This is your primary marketing image in search — it has to stop the scroll on its own. Use a short, benefit-driven caption (think "Track every keyword in one place," not "Dashboard"). Avoid burying the value behind a generic welcome screen.

Screenshot 2 — the core value

Show the one thing your app does better than the alternatives. If screenshot 1 made a promise, screenshot 2 proves it with the actual interface. This is where you convert skeptics, so make the value obvious at a glance.

Screenshot 3 — substantiated proof

If you have current ratings, awards, licensed publication marks, or a genuine testimonial, test a properly substantiated proof frame. Do not invent a user count or assume that adding an overlay will lift conversion.

Screenshots 4–6 — feature depth

Now you can go wider: secondary features, breadth of coverage, integrations, and any "wow" moments that did not fit the opening. Keep one idea per frame and keep captions short.

Final screenshot — the CTA

Close with a directive: "Start free today" or "Try it in 30 seconds." A clear call to action at the end gives motivated swipers an obvious next step.

Tip: screenshot 1 can be a focused first experiment because it appears early in the sequence. Apple's Product Page Optimization lets you compare supported product-page variants; interpret the result within the experiment's audience and confidence.

Want to reverse-engineer what works in your category? See which screenshots your competitors use and analyze their ordering with Lite ASO — it is the fastest way to benchmark before you redesign.

Treat screenshot text as conversion copy, not native-search metadata

Screenshot captions help people understand the product, but Apple does not document screenshot OCR as an input to native App Store keyword indexing. Do not put target terms into images on the assumption that rendered words receive a ranking boost. Apple's current platform-version reference lists the private keyword field separately and describes screenshots as localized product-page assets.

What to do instead:

• Write clear, benefit-led captions for the audience viewing the product page.
• Keep captions legible and high-contrast at thumbnail size.
• Keep one message per frame and avoid keyword-stuffed creative.
• Treat caption wording and screenshot order as hypotheses, then validate them with Product Page Optimization or another controlled conversion experiment.

This keeps two jobs separate: documented metadata fields support search relevance, while screenshots communicate value and can be tested for conversion. If you have not aligned your title and keyword field yet, start with our App Store optimization guide, then use a tool to research candidate terms — our roundup of the best ASO tools of 2026 covers the options.

Google Play screenshots: sizes & differences

If you ship on both stores, do not assume the Apple files drop straight into Google Play. The constraints are different, and Play has assets Apple does not — most notably the feature graphic.

Key differences from Apple to keep straight:

• Minimum count is two on Google Play, versus one on the App Store — but the same conversion logic applies: nail the first frames.
• The feature graphic (1024 × 500) has no App Store equivalent. It headlines your listing and can appear in promotional spots, so treat it as a billboard, not a screenshot.
• No fixed device sizes. Play accepts a wide pixel range as long as you stay within the aspect-ratio bounds, which is why 1080 × 1920 is the safe industry default.
• No alpha channel on PNGs here either, and the per-file cap is 8 MB.

For the full Android playbook — listing structure, keyword placement, and store-specific ranking factors — see our Google Play ASO guide. Specs should be cross-checked against Google Play's official preview-asset requirements before each submission.

A pre-upload checklist

Run this before you hit submit on either store:

• Dimensions match an accepted size exactly — for example 1320 × 2868 (iPhone 6.9") or 2064 × 2752 (iPad 13"), or another resolution in Apple's current table.
• Format is PNG or JPEG, RGB, no alpha channel. Strip transparency before export.
• iPad screenshots are present if your app supports iPad (Apple requires them).
• Feature graphic (1024 × 500) is ready for Google Play.
• Opening frames communicate the core story and stand alone without relying on unverified proof.
• Captions communicate real benefits, are high-contrast, and are legible at thumbnail size.
• Caption wording and order are testable conversion hypotheses, not assumed native-search signals.
• A final CTA frame points motivated users to install or start a trial.
• Text is not cut off by device bezels, notches, or the dynamic island in your mockups.
• Localized variants exist for every market you target — you get up to 10 screenshots per localization on the App Store.
• File sizes are under 8 MB each (Google Play hard limit).

Use the checklist to avoid technical rejection and form clear creative hypotheses. Competitor assets can supply ideas, but their order does not predict your result. Compare dated competitor screenshots with Lite ASO, then validate your own variant in a supported experiment.