App Store Screenshot Sizes for iOS 2026 — The Complete Guide

App Store Connect is notoriously pedantic. Uploading screenshots that deviate from Apple's exact pixel specifications results in immediate metadata rejection. Even "accepted" assets that don't hit the canonical high-resolution targets often look soft or pixelated when downscaled by Apple’s delivery CDN for high-density Retina displays. This guide outlines every mandatory iPhone and iPad screenshot size for 2026, including the specific requirements for the iPhone 16 Pro Max and the iPad Pro M4, alongside technical configurations to ensure your assets pass review on the first attempt.

Required iPhone Screenshot Sizes (2026)

Apple requires at least one screenshot set for your app to be approved. In 2026, the 6.9-inch display is the primary target. While App Store Connect can technically "down-sample" from the largest size, manually providing optimized sets prevents layout shifts and blurry text renders on legacy 19.5:9 devices.

• 6.9" Display (iPhone 16 Pro Max / 17 Pro Max): 1320 × 2868 px (Portrait). This is the new gold standard for high-density listings.
• 6.7" Display (iPhone 16 Plus / 15 Pro Max): 1290 × 2796 px. Required if 6.9" assets are not provided; otherwise, Apple will upscale/downscale.
• 6.5" Display (iPhone 11 Pro Max / XS Max): 1284 × 2778 px or 1242 × 2688 px. Essential for legacy support if you aren't relying on the 6.9" auto-scaling.
• 5.5" Display (iPhone 8 Plus): 1242 × 2208 px. Still mandatory for apps supporting older 16:9 aspect ratio devices.

iPad Screenshot Sizes

If your binary supports iPadOS, providing at least one set of iPad screenshots is non-negotiable. With the introduction of the M4 architecture, the display density requirements have sharpened.

• 13" Display (iPad Pro M4 / M5): 2064 × 2752 px (Portrait). This is the required 2026 baseline for the largest iPad tier.
• 12.9" Display (iPad Pro 2nd–6th Gen): 2048 × 2732 px.
• 11" Display (iPad Pro / iPad Air): 1668 × 2388 px or 1640 × 2360 px. Recommended to prevent UI clipping on the smaller Pro and Air models.

Technical Format & Color Profile

App Store Connect is strict about the underlying file architecture. Submitting the wrong profile can lead to "washed out" colors or halos around your UI elements.

• File Format: Use 24-bit PNG for lossless UI clarity. JPEG is accepted but often introduces compression artifacts around text.
• Color Space: Must be sRGB. Using Display P3 or CMYK will cause color distortion during Apple's processing.
• Alpha Channels: Transparency is strictly prohibited. PNGs with an alpha channel are often flattened into a black background or rejected entirely.

Common Rejection Reasons in 2026

1. Dirty Status Bars: Screenshots showing low battery, cellular carrier names, or active notifications are frequently flagged. Apple expects a clean, standardized status bar (full battery, full bars, no clock/carrier).
2. Alpha Channel Haloing: Even if your image looks fine locally, a PNG with transparency will produce "halo" artifacts once flattened by App Store Connect's ingest system.
3. Localization Mismatch: If your metadata is in French but your screenshots show an English UI, you are at high risk for a Metadata Rejection. Every storefront should have native-language screenshots.
4. Competitor Hardware: Using device frames that clearly resemble non-Apple hardware (e.g., Pixel-style hole-punch cameras on an iPhone listing) is an immediate grounds for rejection.

The Developer’s Workflow: One-Click Compliance

Most "ASO tools" are essentially AI wrappers that struggle with precise pixel compliance or charge "credits" for every minor design iteration. For a production-ready workflow, you need a genuine design tool that understands these constraints natively.

AppScreenStudio’s iOS generator is built to handle this without the friction of paywalls. The core generator and the latest modern device frames (including the iPhone 16 Pro Max and iPad Pro M4) are completely free, exporting 24-bit sRGB PNGs at the exact resolution Apple requires. Furthermore, it solves the localization bottleneck with a built-in 13-language editor, allowing you to manage global screenshots in a single project rather than maintaining dozens of individual Figma layers.