App Store iPad Pro Screenshot Wrong Dimensions — Fix

Q: What size do I actually need for iPad in 2026?

`2064 x 2752` (portrait) or `2752 x 2064` (landscape) — the 13-inch display slot. Supply that one set and Apple scales it down for 12.9-inch and 11-inch automatically. You only need the legacy `2048 x 2732` if you specifically target the 2nd-gen 12.9-inch iPad Pro with distinct artwork.

App Store Connect rejects iPad Pro screenshots with Invalid Screenshot Dimensions. As of 2026 the 13-inch 2064x2752 slot is required. Reference matrix, sips fixes, FAQ.

Published: May 24, 2026 Updated: Jun 21, 2026 Author: AI Productivity Guide Team 🌐 查看中文版本

You upload a polished set of screenshots to App Store Connect, drop them into the iPad slot, and get the red banner: “Invalid Screenshot Dimensions. Please make sure the screenshots are 2064 x 2752, 2752 x 2064, 2048 x 2732, or 2732 x 2048 pixels.” You exported from Figma at the “iPad Pro” preset and it looked right; you tried capturing from the Xcode simulator and it still rejects.

Fastest fix (as of June 2026): the iPad screenshot requirement is now the 13-inch display at exactly 2064 x 2752 (portrait) or 2752 x 2064 (landscape). Capture from an iPad Pro 13-inch (M4) simulator, confirm with sips -g pixelWidth -g pixelHeight shot.png, and re-upload. The old 2048 x 2732 (12.9-inch) size is now legacy — still accepted, but no longer the required slot, and the two differ by 16 / 20 pixels and are not interchangeable.

iPad screenshots are the most-rejected dimension class on App Store Connect because Apple changed the required size in 2024-2025, the “12.9-inch” naming covers several generations of hardware, design tools ship a wrong “iPad Pro” preset, and App Store Connect enforces exact pixels with zero off-by-one tolerance.

What changed in 2026

This is the part that trips up most teams who last shipped screenshots a year ago:

The required iPad slot is now 13-inch (2064 x 2752), covering iPad Pro (M5, M4) and iPad Air (M4/M3/M2). It supersedes the old 12.9-inch slot.
12.9-inch (2048 x 2732) is now a legacy size: still accepted for apps that target the 2nd-gen iPad Pro, but if you only supply 13-inch, Apple auto-scales it down for everything smaller. You usually do not need 12.9-inch at all anymore.
If you provide nothing for 11-inch, Apple uses scaled 13-inch screenshots. You almost never need a dedicated 11-inch upload.

So in 2026 the simplest correct answer is: ship one set at 2064 x 2752/2752 x 2064 and let Apple scale the rest. The sections below cover every way a file ends up the wrong size anyway.

Common causes

Ordered by frequency.

1. Used the legacy 12.9-inch size (2048 x 2732) for the 13-inch slot

This is now the #1 cause. Your screenshot is 2048 x 2732 (the size every tutorial used before 2025), but the current required slot expects 2064 x 2752. They differ by 16 px wide and 20 px tall.

How to spot it: sips reports 2048 x 2732 but the slot is labeled “iPad 13-inch Display” (or “iPad Pro (3rd generation) 12.9-inch Display” mapped to the 13-inch requirement in App Store Connect).

2. Exported at the “iPad Pro” preset in Figma without checking actual pixels

Figma, Sketch, and Adobe XD ship “iPad Pro” presets at point dimensions (e.g. 1024 x 1366 points), not pixels. Export at 1x and you get a half-resolution image; export at 2x of a 1024-point frame and you get 2048 x 2732, which is now the legacy size, not the required 2064 x 2752.

How to spot it: the image inspector shows 1024 x 1366, 2048 x 2732, or some non-2064 width.

3. Outdated fastlane / deliver that rejects the valid size

If you upload through fastlane deliver / upload_to_app_store, older versions validate screenshots against a stale device table and reject the correct file with Invalid screen size (Actual size is 2064x2752...) even though App Store Connect itself accepts it. fastlane’s bundled device table lags Apple’s by a release or two; an out-of-date copy can falsely reject 2064 x 2752.

How to spot it: the web UI accepts the file but your CI/fastlane run fails on the same image. Fix: bundle update fastlane (or gem update fastlane) to the latest release and re-run.

4. Status bar or device chrome accidentally included

The simulator’s screenshot tool can capture its own chrome (rounded corners, the home-indicator hint bar). App Store Connect rejects screenshots that include a device frame.

How to spot it: the screenshot has rounded corners or a black bezel ring at the edges.

5. Wrong aspect ratio after a crop

You captured a full screen, then cropped to “remove” the status bar. The remaining image is something like 2064 x 2700 — not a required size — and App Store Connect rejects it.

How to spot it: pixel dimensions are close but not exact (e.g. 2064 x 2700 instead of 2064 x 2752).

6. Off-by-one after a JPEG/EXIF round-trip

Some processing pipelines re-encode and the OS reports dimensions slightly off (e.g. 2065 x 2753). App Store Connect’s parser allows zero tolerance.

How to spot it: sips -g pixelWidth -g pixelHeight screenshot.jpg shows off-by-one or off-by-a-few.

7. Alpha channel or non-RGB color profile

App Store Connect requires flattened RGB images with no alpha channel. A PNG with transparency, or one tagged Display P3, can be rejected with a generic dimensions/format error even when sips reports the right pixel count.

How to spot it: sips shows correct dimensions, but the upload still fails. Re-exporting as flat sRGB PNG (alpha removed) resolves it.

Before you start

Open the canonical Apple table first: App Store Connect Help → Screenshot specifications. Apple updates it whenever new iPad hardware ships.
Identify exactly which slot in App Store Connect is rejecting; the slot label tells you which dimension row applies.
Decide whether you even need anything beyond the 13-inch set. In most cases you do not.

Information to collect

The exact pixel dimensions of the rejected file: sips -g pixelWidth -g pixelHeight myshot.png.
The orientation (portrait vs landscape) — App Store Connect treats them separately.
The source: simulator screenshot, Figma export, marketing render, etc.
The target slot’s name as displayed in App Store Connect (e.g. “iPad 13-inch Display”).
Color profile, format, and whether there is an alpha channel: sips -g all myshot.png | grep -E "format|profile|space|hasAlpha".
If uploading via CI: your fastlane version (fastlane --version).

Step-by-step fix

Step 1: Identify the right target dimensions for the slot

iPad screenshot reference matrix (as of June 2026, per Apple’s specification page):

Device class	Portrait	Landscape	Status
13-inch (iPad Pro M5/M4, iPad Air M4/M3/M2)	`2064 x 2752`	`2752 x 2064`	Required
12.9-inch (iPad Pro 2nd gen)	`2048 x 2732`	`2732 x 2048`	Legacy, optional
11-inch (iPad Pro M5/M4)	`1488 x 2266`	`2266 x 1488`	Optional (auto-scaled)
11-inch (iPad Pro 4th-1st gen)	`1668 x 2420`	`2420 x 1668`	Optional (auto-scaled)

Match the slot label to the row, then export at exactly those pixel counts. For almost everyone, that means the first row.

Step 2: Generate from the right simulator

Open Xcode → Window → Devices and Simulators → Simulators → + (Create New Simulator) → choose iPad Pro 13-inch (M4) for the current required slot. Run your app, navigate to the screen, then in the simulator menu bar:

Device → Trigger Screenshot

The simulator saves a PNG to Desktop at the exact required dimensions (no device chrome, no alpha). Verify:

sips -g pixelWidth -g pixelHeight ~/Desktop/Simulator\ Screenshot\ *.png

You want pixelWidth: 2064 and pixelHeight: 2752 for portrait.

Step 3: For Figma / design tool exports, set the frame size explicitly

In Figma, create a frame at exact pixel size and export at 1x:

Frame size: 2064 x 2752 px (not points)
Export at: 1x PNG

Common mistake: setting the frame to 1024 x 1366 points and exporting at 2x. That produces 2048 x 2732, which is the legacy 12.9-inch size, not the required 2064 x 2752. There is no point-based frame that scales cleanly to 2064 x 2752, so set the pixel dimensions directly.

Step 4: Strip device chrome / fix an off-by-a-few image with sips

If your shot includes status-bar artifacts, rounded corners, or is a few pixels off, crop to exact size. sips --cropToHeightWidth takes height then width:

sips --cropToHeightWidth 2752 2064 input.png --out output.png

For a precise crop offset (top-left origin):

sips --cropOffset 0 0 --cropToHeightWidth 2752 2064 input.png --out output.png

Verify the result:

sips -g pixelWidth -g pixelHeight output.png
# pixelWidth: 2064
# pixelHeight: 2752

Cropping (not scaling) keeps the UI pixel-accurate. If the source is genuinely a different aspect ratio, re-capture from the simulator instead of stretching.

Step 5: Flatten to sRGB and remove the alpha channel

App Store Connect needs flattened RGB with no transparency. Convert with sips:

sips --setProperty format png --setProperty profile sRGB \
  input.png --out output.png

To also flatten the alpha channel (the most common silent rejection), use ImageMagick:

magick input.png -background white -alpha remove -alpha off \
  -colorspace sRGB -depth 8 output.png

Confirm there is no alpha left:

sips -g hasAlpha output.png
# hasAlpha: no

Step 6: Re-upload and watch the slot-specific validation

In App Store Connect → your app → Distribution → the relevant locale → iPad screenshots, drop the corrected file into the exact slot. The drop zone validates dimensions client-side; if it accepts and a new thumbnail appears, the file is correct. If it rejects, the banner names the expected size — paste that into your sips check and re-export.

If you upload via CI, run fastlane --version first and update to the latest release so the local validator matches Apple’s current table.

Step 7: Automate the export pipeline

A small shell script saves you the next ten times. This one normalizes to the current required size and verifies each output:

#!/bin/bash
# export-screenshots.sh — normalize iPad shots to the 2026 required size
TARGET_W=2064
TARGET_H=2752
mkdir -p export
for src in raw/*.png; do
  out="export/$(basename "$src")"
  # crop to exact size (assumes source >= target); use --resampleHeightWidth to scale instead
  sips --cropToHeightWidth "$TARGET_H" "$TARGET_W" \
       --setProperty format png --setProperty profile sRGB \
       "$src" --out "$out" >/dev/null
  echo "$out -> $(sips -g pixelWidth -g pixelHeight "$out" | tail -2 | tr '\n' ' ')"
done

Run it after every screenshot session; the output is App Store Connect-ready.

How to confirm it’s fixed

sips -g pixelWidth -g pixelHeight reports 2064 x 2752 (or 2752 x 2064) for every uploaded file.
sips -g hasAlpha reports hasAlpha: no.
App Store Connect accepts the file without the red dimension banner, and a new thumbnail appears in the slot.
If you use fastlane, fastlane deliver completes without Invalid screen size.
Preview the listing (App Store Connect → “View on App Store” once live, or the in-page preview); screenshots render crisply without letterboxing.

Long-term prevention

Treat Xcode simulator screenshots as the source of truth — they are guaranteed correct dimensions and chrome-free.
Hardcode the current Apple matrix in your export script; update it once per Apple hardware launch.
Never trust a design tool’s “iPad Pro” preset — always create frames at exact pixel dimensions and export at 1x.
Keep raw captures in source control so you can re-crop when Apple adds or retires a device class.
Store screenshots per build as <version>-<locale>-<device-class>/ so audits are trivial.
When Apple announces new iPad hardware at WWDC, expect the required slot to move within a few months — update the pipeline (and your fastlane version) before your next submission. See App Store Screenshot Metadata Issue for related metadata problems.

Common pitfalls

Assuming the old 2048 x 2732 is still the required size — as of 2026 the required slot is 2064 x 2752.
Uploading a 1920 x 2560 (or any “close enough”) image and expecting a warning — App Store Connect rejects outright.
A stale fastlane rejecting a file the web UI happily accepts; update to the latest release.
Leaving an alpha channel in the PNG — flatten it.
Letting a design tool export at 1.5x or 2.5x; only 1x of a correctly sized frame yields exact pixels.
Re-uploading the wrong file after the fix — confirm the new thumbnail actually appears, since App Store Connect caches.

FAQ

Q: What size do I actually need for iPad in 2026?

2064 x 2752 (portrait) or 2752 x 2064 (landscape) — the 13-inch display slot. Supply that one set and Apple scales it down for 12.9-inch and 11-inch automatically. You only need the legacy 2048 x 2732 if you specifically target the 2nd-gen 12.9-inch iPad Pro with distinct artwork.

Q: The web UI accepts my screenshot but fastlane rejects it with “Invalid screen size.” Why?

Your fastlane version predates the current iPad table — its bundled device list still rejects 2064 x 2752. Run bundle update fastlane (or gem update fastlane) to the latest release and re-run deliver.

Q: My app is portrait-only. Do I need landscape screenshots?

No. Only ship screenshots for the orientations your app supports. Shipping landscape for a portrait-only app can get flagged as inconsistent during review.

Q: Can I use a marketing render instead of a real app screenshot?

You may add marketing copy overlays, but device frames are not allowed and the underlying UI must be honest — the reviewer compares it to actual app behavior. Stylized renders showing features the app does not have draw Guideline 2.3 / 4.3 rejections.

Q: Does App Store Connect accept WebP or HEIC?

No — PNG and JPEG only, RGB, no alpha channel, 1 to 10 screenshots per device type. Use JPEG for photo-heavy screenshots and PNG for UI-heavy ones.

Q: Why does Apple require exact pixels instead of just downscaling everything?

Apple does downscale from the 13-inch master, but the source must be pixel-exact so the scaled result stays crisp on Retina displays. A source that is even one pixel off, or upscaled from a smaller capture, looks soft on device.

Tags: #Troubleshooting #App Store #Screenshots #ipad-pro #Metadata