Playbooks

    App Store Screenshot Sizes and What to Put in Them

    The sizes Apple actually requires in 2026, plus how the first two screenshots decide whether anyone taps install.

    August 21, 2026 · 3 min read · By Wanilla Team

    App Store Screenshot Sizes and What to Put in Them

    Quick answer

    You must upload screenshots for the 6.9-inch iPhone display (1290 x 2796 px) and, if the app supports iPad, the 13-inch iPad display (2064 x 2752 px). Apple scales those to the smaller devices, so two sets are enough. You can upload up to 10 screenshots per device size, per localisation.

    Apple only asks for two screenshot sizes now, but the rules around them trip people up more than they should. Here is exactly what you need, at what pixel dimensions, and what actually converts once they are live.

    The required sizes in 2026

    App Store Connect requires one set of iPhone screenshots and, if your app supports iPad, one set of iPad screenshots. Everything else is scaled automatically.

    DevicePortraitLandscapeRequired?
    6.9" iPhone (Pro Max class)1290 x 2796 px2796 x 1290 pxYes
    6.5" iPhone (legacy set)1242 x 2688 px2688 x 1242 pxOptional
    13" iPad Pro2064 x 2752 px2752 x 2064 pxOnly if the app supports iPad

    You can upload up to 10 screenshots per device size, per language. Files must be PNG or JPEG, RGB, flattened, with no alpha channel and no rounded corners — Apple applies its own masking.

    App previews (video)

    You can add up to three app previews of 15 to 30 seconds each, recorded at the same device resolution. Previews autoplay muted in search results, so the first two seconds have to make sense without sound. They are optional, but on competitive terms they lift conversion noticeably.

    The first three screenshots do almost all the work

    Search results show two or three screenshots before anyone taps through to your product page. Treat those as an advert, not a tour:

    • Screenshot 1 — the outcome, in a short caption. "Turn your web app into a real iOS app", not "Dashboard".
    • Screenshot 2 — the single feature people are searching for.
    • Screenshot 3 — proof: numbers, results, or a before and after.
    • Screenshots 4 to 10 — depth for the people who kept scrolling.

    Caption text should be large enough to read at thumbnail size — roughly 60 px or more at full resolution. Full-bleed device frames with tiny UI screenshots inside are the most common mistake.

    Common reasons screenshots cause problems

    • Mismatched content. If a screenshot shows a feature the reviewer cannot reach in the build, expect a metadata rejection. This is one of the quieter App Store rejection reasons.
    • Status bar clutter. Use a clean simulator status bar; battery warnings and stray notifications look sloppy.
    • Placeholder or lorem text in the UI.
    • Pricing claims that contradict your in-app purchase configuration.
    • Wrong aspect ratio, which App Store Connect rejects at upload rather than at review.

    How to capture them

    The simplest route is the iOS Simulator at the 6.9" iPhone size, then Device > Trigger Screenshot, which saves at the exact required resolution. For framed marketing shots, export the raw captures and lay them out in Figma against a 1290 x 2796 artboard. Localise captions per market — the images are per-language, and a translated caption usually beats a translated description for conversion.

    Where screenshots sit in the wider launch

    Screenshots are conversion, not discovery. Discovery comes from your app name, subtitle and keyword field, which is covered in App Store keyword research, while the whole listing is covered in App Store listing optimisation. Get both right and the same traffic produces materially more installs.

    If you built with an AI builder and want the entire listing — screenshots, metadata, and the native build behind it — handled for you, see the managed launch offer.

    Where to go next

    Ready to ship to the App Store?

    Book a free Launch Review and we'll map a 24-hour path from your AI build to a live iOS app.

    More in Playbooks

    Samuel Olsson, Co-founder of Wanilla

    Samuel Olsson

    Co-founder, Wanilla

    Connect on LinkedIn