App Store screenshot sizes in 2026: which ones are actually required

Apple and Google both reject uploads that are the wrong pixel size or have an alpha channel. The confusing part is that blog posts disagree on which iPhone sizes are "required" in 2026 — because Apple only forces the fallback sizes when you skip the newer ones.

The short answer (November 2026)

App Store

• Required: one Dynamic Island iPhone set at 1179 × 2556 (or 1206 × 2622).
• Required if iPad: 2064 × 2752 (or 2048 × 2732).
• Optional but useful master: design at 1290 × 2796, then export the required sizes from that artboard.

Google Play

• Between 320 and 3840 px per side; long side ≤ 2× short side.
• For featuring: at least 4 screenshots, 1080 px or wider (e.g. 1080 × 1920 portrait).

Full table with sources: App Store & Play screenshot sizes (Nov 2026) (6.5" fallback rules: #6-5-inch-display).

Common mistakes

1. Transparent PNGs — both stores reject alpha in listing screenshots. Export JPEG or flatten PNG.
2. Only 6.7" assets — fine if you also ship 1179 × 2556; otherwise Connect nags you for the medium Dynamic Island slot.
3. Stretching a 1080p capture — upscaling looks soft; capture on a device or emulator at native resolution, then frame it.

Free tool (nothing uploaded)

I made AppShot to drop a raw capture, add a frame + headline, and export exact store pixels in one zip — all client-side.

The size cheat sheet is kept up to date here: screenshot-sizes guide.

Pro layouts: if you want caption formulas + 30 layout presets (not just frames), AppShot Pro ($12 on Gumroad) imports into the free tool — still nothing uploaded.

Disclosure: this post was drafted by AI agents I run and fact-checked against Apple's screenshot specifications page on Nov 3, 2026. AppShot itself was also built with AI coding agents; MIT repo on GitHub.

Comments

[Alex Shev]

The operational risk is not only choosing the wrong dimensions but losing track of which screenshots describe which build. Pairing generated assets with the app version, device family, locale, and a small validation manifest would make the App Store upload step repeatable instead of a manual scavenger hunt.