Skip to main content
App Store metadata and localizations Level: Developer 11 min read

App Store Screenshot Sizes: Complete Dimension Guide for iPhone and iPad

Master Apple's App Store screenshot dimensions, display sets, accepted formats, scaling rules, and automated upload workflows for iPhone and iPad apps.

Published: 2026-11-01 • Last Updated: 2026-11-01 • Author: Kip Lawrence
Key MCP Tools: app_screenshots_listapp_screenshot_upload_planapp_screenshot_upload_execute

Preparing marketing screenshot assets for App Store Connect is often a frustrating bottleneck when releasing an iOS app. Apple enforces strict pixel-dimension standards, aspect ratio rules, and color profile requirements across device generations. An image off by even a single pixel or exported with an active alpha channel will be rejected immediately by App Store Connect's ingestion pipeline.

Managing screenshots effectively is a hybrid workflow. FlightDeck does not capture simulator screens, crop canvas borders, or resize image dimensions; you capture and export your visual assets using design tools or the Xcode Simulator. Once your image assets are prepared locally, your AI coding assistant uses FlightDeck to inspect existing remote screenshot sets, validate local file dimensions against Apple specifications, and stage uploads directly to App Store Connect.


What You Need

Before preparing and uploading App Store screenshots:

  • An active Apple Developer account with an application record in App Store Connect.
  • FlightDeck installed and connected to your Apple Developer account.
  • An AI coding assistant (Cursor, Claude Code, Antigravity, Windsurf, or Roo Code) connected to FlightDeck's MCP server. See Connecting Cursor to App Store Connect.
  • Locally exported screenshot PNG files matching Apple's dimension specifications.

Quick Reference: Required Minimum Screenshot Sets

If your app runs on iPhone and iPad, you do not need to capture screenshots for every historical device model. Apple uses a simplified submission architecture where two primary sizes provide baseline coverage across the entire App Store:

  1. 6.7" / 6.9" iPhone Display (APP_IPHONE_67): Required for all iPhone apps. Apple automatically downscales these screenshots to display across 6.5", 6.3", 6.1", and 5.8" devices.
  2. 13" / 12.9" iPad Pro Display (APP_IPAD_PRO_3GEN_129): Required** for all apps that support iPad. Apple scales these down for 11" iPad Pro, iPad Air, and iPad mini models.
Note

If your application includes custom user interfaces tailored specifically for legacy 16:9 home-button devices, you may optionally supply dedicated 5.5" screenshots (APP_IPHONE_55). If omitted, Apple serves scaled 6.7" assets.


Comprehensive iPhone Screenshot Dimensions Matrix

All screenshots may be uploaded in either portrait or landscape orientation. However, all screenshots within a single display set must share the same orientation.

Display Category Apple Display Type Identifier Portrait (Pixels) Landscape (Pixels) Compatible Hardware Models
6.9" Super Retina XDR APP_IPHONE_67 1320 x 2868 2868 x 1320 iPhone 16 Pro Max
6.7" Super Retina XDR APP_IPHONE_67 1290 x 2796 2796 x 1290 iPhone 16 Plus, 15 Pro Max, 15 Plus, 14 Pro Max, 14 Plus
6.5" Super Retina APP_IPHONE_65 1242 x 2688 2688 x 1242 iPhone 11 Pro Max, XS Max
6.3" Super Retina XDR APP_IPHONE_61 1206 x 2622 2622 x 1206 iPhone 16 Pro
6.1" Super Retina XDR APP_IPHONE_61 1179 x 2556 2556 x 1179 iPhone 16, 15 Pro, 15, 14 Pro, 14, 13 Pro, 13
5.8" Super Retina APP_IPHONE_58 1125 x 2436 2436 x 1125 iPhone 11 Pro, XS, X
5.5" Retina HD (16:9) APP_IPHONE_55 1242 x 2208 2208 x 1242 iPhone 8 Plus, 7 Plus, 6s Plus
4.7" Retina HD (16:9) APP_IPHONE_47 750 x 1334 1334 x 750 iPhone SE (2nd & 3rd gen), iPhone 8


Comprehensive iPad Screenshot Dimensions Matrix

If your Xcode build target checks the iPad deployment destination, you must supply at least one set of iPad screenshots:

Display Category Apple Display Type Identifier Portrait (Pixels) Landscape (Pixels) Compatible Hardware Models
13" iPad Pro (M4) APP_IPAD_PRO_3GEN_129 2064 x 2752 2752 x 2064 13-inch iPad Pro (M4)
12.9" iPad Pro (Gen 3–6) APP_IPAD_PRO_3GEN_129 2048 x 2732 2732 x 2048 12.9-inch iPad Pro (3rd through 6th gen)
11" iPad Pro (M4) APP_IPAD_PRO_3GEN_11 1668 x 2420 2420 x 1668 11-inch iPad Pro (M4)
11" iPad Pro / Air APP_IPAD_PRO_3GEN_11 1668 x 2388 2388 x 1668 11-inch iPad Pro (1st–4th gen), iPad Air 11"
10.9" iPad (10th gen) APP_IPAD_105 1640 x 2360 2360 x 1640 iPad (10th generation), iPad Air (4th & 5th gen)
10.5" iPad Pro / Air APP_IPAD_105 1668 x 2224 2224 x 1668 10.5-inch iPad Pro, iPad Air (3rd generation)


Technical Image Specifications & Ingestion Rules

App Store Connect strictly validates every uploaded image asset:

  1. Color Space: Standard sRGB or Display P3. High-dynamic range (HDR) images with unbounded profiles will fail ingestion.
  2. File Format: High-resolution PNG or flattened JPEG.
  3. No Alpha Channel (Transparency): This is the single most common cause of screenshot upload errors. PNG images must have No Alpha Channel. Even a 100% opaque alpha channel header causes Apple's validator to reject the file.
  4. Resolution: 72 DPI target resolution (pixel dimensions govern acceptance).
  5. Quantity: Between 1 and 10 screenshots per display type per localization.
  6. Orientation Consistency: You cannot mix portrait and landscape images within the same device display set.

Validation Boundaries: FlightDeck vs. Local AI Tools vs. Apple Ingestion

Understanding which system validates which attribute prevents unexpected upload rejections:

Validation Check Evaluated By Mechanism & Behavior
File Existence & Integrity FlightDeck (Local) Resolves symlinks, verifies regular file, computes SHA-256 digest, and enforces TOCTOU protection before streaming.
Basic Image Format (PNG/JPEG) FlightDeck (Local) Checks magic bytes (PNG 89 50 4E 47 / JPEG FF D8) in file header.
Dimension Extraction FlightDeck (Local) Parses width and height from PNG IHDR / JPEG SOF0 headers without loading entire image in memory.
OpenAPI Display Type FlightDeck (Local) Validates that the requested display type identifier exists in Apple's OpenAPI schema.
10 MB Size Guideline FlightDeck (Local) Warns if file exceeds Apple's standard 10 MB asset guideline.
Alpha Channel Inspection Local Tools / Assistant FlightDeck does not inspect alpha channels locally. Use macOS sips -g hasAlpha or have your AI assistant inspect the file.
Alpha Channel Stripping Local Tools / Assistant macOS sips cannot strip alpha while retaining PNG directly. Remove transparency by exporting without alpha in design tools, converting to JPEG (sips -s format jpeg input.png --out output.jpg), or flattening via Preview / ImageMagick.
Color Profile Verification Local Tools / Assistant Inspect using sips -g space or sips -g profile to ensure sRGB or Display P3.
Pixel Dimension Match Apple Backend Apple's server-side ingestion pipeline verifies whether extracted dimensions match allowed resolutions for the target display type.
Strict Transparency Rejection Apple Backend Apple rejects files containing an active alpha channel during asynchronous server-side processing.
Set Capacity (1–10) FlightDeck + Apple FlightDeck checks remote set capacity during planning; Apple enforces limits during container reservation.

Important

Local Checks Do Not Guarantee Apple Acceptance: Passing FlightDeck's local planning checks verifies that the file is well-formed, non-empty, and correctly fingerprinted. However, Apple performs asynchronous validation after byte upload for exact pixel dimension matching, color profile conformance, and alpha-channel absence. Always run a read-back verification after uploading.


Screenshot Inheritance & Downscaling Mechanics

Apple's App Store client uses intelligent scaling rules to minimize developer workload:

TEXT
┌──────────────────────────────────────────────┐
│  6.7" / 6.9" Display Set (APP_IPHONE_67)     │ (Master iPhone Set)
└──────────────────────┬───────────────────────┘
                       │
         ┌─────────────┴─────────────┐
         ▼                           ▼
┌──────────────────┐        ┌──────────────────┐
│ 6.1" / 6.3"      │        │ 5.8"             │
│ iPhone 16 / 15   │        │ iPhone X / 11 Pro│
│ (Scaled down)    │        │ (Scaled down)    │
└──────────────────┘        └──────────────────┘
  • When to provide 6.7" only: If your app uses standard auto-layout or responsive Flutter / React Native UI that adapts fluidly across notch and Dynamic Island sizes, supplying APP_IPHONE_67 (such as 1290 x 2796) is sufficient.
  • When to provide custom sizes: If your user interface requires pixel-perfect positioning on 16:9 home-button devices (e.g., iPhone SE), upload an explicit APP_IPHONE_55 set. If custom screenshots are uploaded for a size, Apple serves those instead of scaling the master set.

Capturing Pixel-Perfect Screenshots Locally

Before uploading, capture clean images from the Xcode Simulator or your terminal:

BASH
# 1. Override status bar to standard Apple marketing layout (9:41 AM, full battery)
xcrun simctl status_bar booted override --time "9:41" --batteryState charged --batteryLevel 100

# 2. Capture exact native resolution from running simulator
xcrun simctl io booted screenshot ./assets/screenshots/6.7_screen_01.png

# 3. Check for presence of an alpha channel (must return "no")
sips -g hasAlpha ./assets/screenshots/6.7_screen_01.png

# 4. Check color space (must be RGB)
sips -g space ./assets/screenshots/6.7_screen_01.png

# 5. Remove alpha channel if present (PNG re-encoding preserves alpha; use JPEG or flatten)
sips -s format jpeg ./assets/screenshots/6.7_screen_01.png --out ./assets/screenshots/6.7_screen_01.jpg

Inspecting and Uploading Screenshots with Your AI Assistant

Once your screenshots are saved locally, use your AI coding assistant and FlightDeck to manage remote sets without manual portal drag-and-drop.

MERMAID
flowchart TD
    A["Developer Prompt in AI Chat"] --> B["AI Assistant Queries app_screenshots_list via FlightDeck"]
    B --> C["Assistant Audits Remote Sets & Identifies Missing Targets"]
    C --> D["Assistant Stages Upload Plan for Local Files"]
    D --> E["FlightDeck Desktop Approval Center Shows File & Dimension Card"]
    E --> F["Developer Reviews & Clicks Approve"]
    F --> G["FlightDeck Streams Assets Directly to Apple Ingestion API"]

Step 1: Prompt Your AI Assistant to Audit Existing Screenshots

Ask your assistant to inspect your current store listing:

TEXT
Inspect the screenshot sets for [Your App Name] in App Store Connect for our draft release. Check the English (en-US) localization and tell me which display sets currently exist, how many images are uploaded, and whether required targets like 6.7-inch iPhone or 12.9-inch iPad Pro are missing.

What Your Assistant Does Behind the Scenes:

  1. It queries App Store Connect using app_screenshots_list to list all existing screenshot sets and their image counts.
  2. It compares the existing sets against your target platforms (iPhone and iPad) to identify missing requirements.
  3. It reports the current state and asks where your prepared local image files are stored.

Step 2: Prompt Your Assistant to Stage Screenshot Uploads

Once you specify the directory of prepared screenshots, instruct your assistant to stage the upload:

TEXT
I have prepared new 6.7-inch iPhone screenshots in ./assets/screenshots/6.7/. Please inspect the local image dimensions to verify they match APP_IPHONE_67 (1290 x 2796), and stage an upload plan to replace the existing set.

What Your Assistant Does Behind the Scenes:

  1. It inspects the local files, verifying pixel dimensions, format (PNG/JPEG), and confirming the absence of alpha channels.
  2. It prepares a staged upload request using app_screenshot_upload_plan.
  3. FlightDeck opens a confirmation card in the Desktop Approval Center.

FlightDeck Desktop Approval Center:

Because uploading screenshots modifies your public App Store assets, FlightDeck presents the file details for review:

Illustrative representation of the FlightDeck Approval Center sheet:

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   FlightDeck Desktop Approval Center                   │
├────────────────────────────────────────────────────────────────────────┤
│ Operation: Upload App Store Screenshot                                 │
│ App: FocusPulse (ID: 6471234567) | Locale: en-US                       │
│ Display Target: APP_IPHONE_67 (6.7" Super Retina XDR)                  │
│ Local File: ./assets/screenshots/6.7/01_dashboard.png                  │
│ Dimensions: 1290 x 2796 (Portrait) | Alpha Channel: NONE (Opaque)    │
│ Target Slot: Position 0                                                │
│                                                                        │
│              [ Reject ]                  [ Approve & Upload ]          │
└────────────────────────────────────────────────────────────────────────┘

Inspect the thumbnail, dimensions, and target slot, then click Approve & Upload. FlightDeck reserves the asset slot on Apple's servers, streams the image data directly over HTTPS, and commits the asset.


Verify Success: Read-Back Screenshot Verification

Once uploaded, instruct your AI assistant to verify that Apple has received and processed the asset:

TEXT
Query App Store Connect for [App Name] and verify that the English (en-US) APP_IPHONE_67 screenshot set now contains our newly uploaded screenshots in the correct order.

Your assistant queries app_screenshots_list and confirms that the asset state is complete and displayed in the target order.


Top Five Screenshot Rejection Triggers

  1. Transparency in PNG Files: Exporting from Figma or Photoshop often includes an alpha channel. Apple strictly rejects screenshots containing alpha channels. Always uncheck "Alpha" during design export, convert to JPEG (sips -s format jpeg input.png --out output.jpg), or flatten transparency before uploading.
  2. Simulator Window Chrome: Screenshots must depict only the running application interface. Never include macOS window borders or background wallpaper.
  3. Status Bar Glitches: Status bars showing 2% battery or search bars with placeholder text signal unfinished software. Use simctl status_bar to standardize status indicators.
  4. Hardware Frame Mismatches: If embedding screenshots in device mockup frames, the frame hardware must match the display type (e.g., do not place an iPhone frame inside an APP_IPAD_PRO_3GEN_129 upload).
  5. Nonfunctional Features: Depicting features that do not exist in the submitted binary violates Guideline 2.3.

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store