App Store Screenshot Wrong Dimensions for iPad Pro — Fix

App Store Connect rejects screenshots with Invalid Screenshot Dimensions because iPad Pro requires exact pixel sizes per device class. The reference matrix and fix.

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

You upload a polished set of screenshots to App Store Connect → App Information → your locale → Screenshots, drop in the 12.9-inch iPad Pro slot, and get the red banner: “Invalid Screenshot Dimensions. Please make sure the screenshots are 2048 x 2732, 2732 x 2048, 2048 x 2752, or 2752 x 2048 pixels.” You exported from Figma at “iPad Pro” preset and it looked right; you tried capturing from the Xcode simulator and it still rejects. iPad Pro screenshots are the most rejected dimension class on App Store Connect because Apple maintains four required pixel sizes per orientation, the “12.9-inch” naming covers two generations of hardware, and design tools’ “iPad Pro” presets are often wrong.

Common causes

Ordered by frequency.

1. Used 12.9-inch dimensions for the new “13-inch” iPad Pro slot (M4, 2024+)

Apple split iPad Pro screenshot slots in 2024:

12.9-inch iPad Pro (6th gen): 2048 x 2732 (portrait) / 2732 x 2048 (landscape)
13-inch iPad Pro (M4, 7th gen): 2064 x 2752 / 2752 x 2064

These are different by 16 / 20 pixels and not interchangeable.

How to spot it: Screenshot is 2048 x 2732 but the rejected slot is the 13-inch iPad Pro M4 slot.

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

Figma, Sketch, and Adobe XD have “iPad Pro” presets that ship at 1366 x 1024 points (not pixels). Without exporting at 2x, you get 1366 x 1024 pixel images — half the required resolution.

How to spot it: Image inspector shows 1366 x 1024 or 1024 x 1366 instead of 2048 x 2732.

3. Status bar or device chrome accidentally included

The simulator’s screenshot tool sometimes captures the simulator’s own chrome (rounded corners, navigation hint bar). App Store Connect rejects screenshots that include the device frame.

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

4. Wrong aspect ratio after a crop

You captured a full screen, then cropped to “fit” the status bar out. The remaining image is 2048 x 2680 — not a multiple of any required size — and App Store Connect rejects.

How to spot it: Pixel dimensions are close but not exact (e.g., 2048 x 2680 instead of 2048 x 2732).

5. JPEG with metadata stripped reports different pixel count

Some processing pipelines strip the EXIF and the OS reports dimensions slightly off (e.g. 2049 x 2733). App Store Connect’s parser is strict.

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

6. Uploaded the 11-inch iPad Pro screenshot to the 12.9 slot

11-inch iPad Pro requires 1668 x 2388 / 2388 x 1668 (or 1640 x 2360 / 2360 x 1640 on newer models). These are NOT valid for the 12.9-inch slot.

How to spot it: Image is 1668 x 2388 but you dragged it into the 12.9-inch slot.

7. PNG color profile or alpha channel issues

PNG with transparency or in P3 color space sometimes confuses the dimension parser. The image is reported as having an invalid size when it is really a color profile issue.

How to spot it: sips shows correct dimensions, but App Store Connect rejects with a generic dimensions error. Re-exporting as flat sRGB PNG resolves it.

Before you start

Pull up the current Apple table of required dimensions; Apple updates it whenever new iPad Pro hardware ships. As of 2025 the canonical list is in App Store Connect Help → Screenshot specifications.
Identify exactly which slot in App Store Connect is rejecting; the slot label tells you which dimension matrix applies.
Decide whether you need to ship both 12.9 and 13-inch screenshots, or whether one with a fallback works.

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 Pro (3rd Generation) 12.9-inch Display”).
Color profile and format: sips -g all myshot.png | grep -E "format|profile|space".

Step-by-step fix

Step 1: Identify the right target dimensions for the slot

iPad Pro screenshot reference matrix (as of 2025):

Device class	Portrait	Landscape
12.9-inch (3rd–6th gen)	2048 x 2732	2732 x 2048
13-inch (M4, 7th gen)	2064 x 2752	2752 x 2064
11-inch (3rd–5th gen)	1668 x 2388	2388 x 1668
11-inch (M4, 5th gen)	1668 x 2420	2420 x 1668

Match the slot label to the row, then export at exactly those pixel counts.

Step 2: Generate from the right simulator

Open Xcode → Window → Devices and Simulators → Simulators → + Create New → choose iPad Pro 12.9-inch (6th generation) for the 12.9 slot, or iPad Pro 13-inch (M4) for the 13-inch slot. Run your app, navigate to the screen, and:

Device → Trigger Screenshot

The simulator saves a PNG to Desktop at the exact required dimensions. Verify with sips:

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

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

In Figma, create a frame at exact pixel size:

Frame size: 2048 x 2732 px (not points)
Export at: 1x PNG

Common mistake: setting frame to 1024 x 1366 points and exporting at 2x. That works for retina assets in code, but the exported PNG’s pixel dimensions need to be exactly 2048 x 2732, no rounding.

Step 4: Strip device chrome with `sips` or ImageMagick

If your shot includes status bar artifacts or rounded corners:

sips --cropToHeightWidth 2732 2048 input.png --out output.png

Or for a precise crop offset:

sips --cropOffset 0 0 --cropToHeightWidth 2732 2048 input.png --out output.png

Verify the result:

sips -g pixelWidth -g pixelHeight output.png
# pixelWidth: 2048
# pixelHeight: 2732

Step 5: Flatten PNG color profile to sRGB

Some App Store Connect uploads fail on P3 or RGBA. Convert:

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

Or with ImageMagick to also flatten alpha:

magick input.png -background white -flatten \
  -colorspace sRGB -depth 8 output.png

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

In App Store Connect → App Information → screenshots → drop the corrected file into the exact slot. The drop zone validates dimensions client-side; if it accepts, the file is correct. If it rejects, the error text tells you the expected size — paste into the bash check and re-export.

Step 7: Automate the export pipeline

A small Makefile or shell script saves you the next ten times:

#!/bin/bash
# export-screenshots.sh
SLOTS=("ipad-pro-12.9:2048x2732" "ipad-pro-13:2064x2752" "ipad-pro-11:1668x2388")
for slot in "${SLOTS[@]}"; do
  name="${slot%%:*}"
  size="${slot#*:}"
  for src in raw/$name-*.png; do
    out="export/$(basename $src)"
    sips -z ${size#*x} ${size%x*} "$src" --out "$out"
    sips -g pixelWidth -g pixelHeight "$out"
  done
done

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

Verify

Every uploaded screenshot reports the exact dimension expected for its slot (use sips -g pixelWidth -g pixelHeight).
App Store Connect accepts the file without the red dimension banner.
Each language locale’s screenshots are uploaded for every required slot (Apple defaults to inheriting from English if missing, but explicit per-locale is required for translated marketing copy on screenshots).
Preview the app on App Store Connect → Browse on App Store; screenshots render correctly without letterboxing.

Long-term prevention

Build a screenshot export script that hardcodes the current Apple matrix; update it once per Apple hardware launch.
Use Xcode simulator screenshots as the source of truth — they are guaranteed correct dimensions.
Avoid Figma’s “iPad Pro” preset; always create frames at exact pixel dimensions.
Keep raw 2x exports in source control so you can re-crop when Apple adds a new device class.
For each app version, store screenshots in a folder named <version>-<locale>-<device-class>/ so you can audit easily.
When Apple announces a new iPad Pro at WWDC, expect a new screenshot slot within ~3 months; update the export pipeline before submission. See App Store Screenshot Metadata Issue for related metadata problems.

Common pitfalls

Uploading a 1920 x 2560 screenshot to the 2048 x 2732 slot and assuming “close enough” — App Store Connect rejects, not warns.
Mixing portrait and landscape in the same locale’s slot lineup; some slots require all portrait or all landscape per locale.
Embedding device frames (Apple’s old practice) — current guidelines disallow device chrome.
Forgetting that App Store Connect requires both portrait and landscape screenshots for some slots if your app supports both orientations.
Letting design tool export a “1.5x” or “2.5x” scale; only 1x of a correctly-sized frame produces the right pixel count.
Re-uploading the wrong file after fix — App Store Connect caches; always confirm the new thumbnail appears.

FAQ

Q: Do I have to ship both 12.9-inch and 13-inch screenshots?

Apple currently requires at least one iPad Pro size if you support iPad. Most teams ship 13-inch (newest hardware) and let Apple downscale for older iPads. If you have unique 12.9-inch UI, ship both.

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

No. Only ship screenshots for the orientations your app supports. If you ship landscape screenshots for a portrait-only app, reviewer may flag inconsistency.

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

You may include marketing copy overlays, device frames are not allowed, and the underlying app UI must be honest — reviewer compares to actual app behavior. Stylized renders with fake features are 4.3 rejections.

Q: Why does Apple require so many sizes? Cannot they downscale?

Apple downscales when no exact slot match exists, but the dedicated slots give you control over per-device crops and ensure crisp display. Slots with mismatched scaling look blurry on Retina iPads.

Q: Does App Store Connect support WebP or HEIC for screenshots?

No — PNG and JPEG only. Submit JPEG for photo-heavy screenshots and PNG for UI-heavy screenshots. The size cap is 8 MB per file.

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