App Store Screenshot Sizes 2026

The short answer: iPhone screenshots must be 1320×2868 pixels (portrait) or 2868×1320 (landscape), the 6.9-inch display class. If your app runs on iPad, you also need 13-inch iPad screenshots at 2064×2752 or 2048×2732 (portrait). Each localization takes 3 to 10 screenshots, filenames upload in alphabetical order, and PNGs must not contain an alpha channel.

Updated July 2026

The complete size table

Device classPortrait (px)Landscape (px)Required?
iPhone 6.9″
(iPhone 16 Pro Max class)
1320 × 2868 2868 × 1320 Yes, for every iPhone app.
iPad 13″ 2064 × 2752 2752 × 2064 Yes, if the app declares iPad support.
iPad 13″ (alternate) 2048 × 2732 2732 × 2048 Accepted alternative pixel count for the same 13″ slot.

Sizes must match exactly. A 1290×2796 capture (the older 6.7-inch class) will not fill the 6.9-inch slot. Not sure what you have? Drop your files into the free size checker; it reads the dimensions locally and tells you which slot they match.

The naming trap: one canvas, three names

The 6.9-inch screenshot slot goes by a different identifier in every tool that touches it. Confusing them produces uploads that silently land in the wrong slot, or fail:

WhereIdentifierMeaning
Your design canvas 1320 × 2868 The actual pixels you export.
App Store Connect API APP_IPHONE_67 The display-family enum. Yes, it says 67 for the 6.9″ canvas: the enum name lags the hardware.
asc CLI IPHONE_69 What you pass to --device-type when uploading with App-Store-Connect-CLI.

All three refer to the same screenshot slot. If you automate uploads, hardcode this mapping once and never think about it again:

# Upload a localized folder tree with the asc CLI
asc screenshots upload --app APP_ID --version 1.0 \
  --path ./shots --device-type IPHONE_69
# ./shots/en-US/*.png, ./shots/es-MX/*.png -> fan-out per locale

The rules beyond pixel size

3 to 10 screenshots per localization

Every localization accepts between 3 and 10 screenshots per device class, and each localization can carry a completely different set. That means your es-MX listing can show Spanish UI and Spanish marketing copy while en-US shows English, same layout, different strings.

Alphabetical filename order = product page order

When you bulk-upload, App Store Connect sorts your files alphabetically and that becomes the order on your product page. Prefix filenames with numbers to control the sequence:

01-hero.png
02-editor.png
03-localization.png
04-export.png
05-social-proof.png

No alpha channel, ever

App Store Connect rejects PNGs that declare an alpha channel with IMAGE_ALPHA_NOT_ALLOWED, even when the image is visually opaque. Most design tools export RGBA by default, so this bites almost everyone once. The fix takes seconds with the free in-browser Alpha Channel Fixer, and the full explanation lives in the IMAGE_ALPHA_NOT_ALLOWED guide.

FAQ

Do I need landscape screenshots too?

Only if your app's primary orientation is landscape. You pick one orientation per device class; the accepted pixel sizes for landscape are the portrait sizes with width and height swapped (2868×1320 for iPhone 6.9″).

Can I still upload 6.5-inch or 6.7-inch screenshots?

The 6.9-inch class (1320×2868) is the size App Store Connect asks for on current submissions. Older classes exist for legacy listings, but new uploads should target 6.9″; smaller devices get scaled versions automatically.

PNG or JPEG?

Both are accepted. PNG gives you crisp UI text; just make sure it has no alpha channel. JPEG can't carry alpha at all, which is why converting to JPEG is a quick (lossy) way around IMAGE_ALPHA_NOT_ALLOWED.

Do different locales really need different screenshots?

They don't need to differ, but they can, and localized screenshots convert better. Each locale holds its own set of 3 to 10, so you can keep one layout and swap the language of the UI and the marketing copy.

Check your files now

Right sizes are the floor, not the ceiling.

ScreenshotPunch generates App Store screenshots with editorial art direction, exported at exactly these sizes with no alpha channel. Coming soon.

About ScreenshotPunch