Fix "The Dimensions of One or More Screenshots Are Wrong"

Quick answer: App Store Connect shows "The dimensions of one or more screenshots are wrong" when an image's pixel size doesn't exactly match a size accepted by the slot you dropped it into. Check the pixels with sips -g pixelWidth -g pixelHeight shot.png, compare them with the slot (the required iPhone 6.3″ slot takes 1206 × 2622 or 1179 × 2556), and re-export at that size.

Each display slot in App Store Connect accepts a short list of exact pixel sizes, in portrait or landscape. There's no tolerance: a file that's one pixel off, or a perfect file in the wrong slot, triggers the same message. App Store Connect won't crop or resize the image for you.

These are the iPhone slots most people upload to:

Landscape versions swap width and height. If your app runs on iPad, the iPad 13″ slot is required too (2064 × 2752 or 2048 × 2732 in portrait). The iPhone size guide and iPad size guide list every other slot.

Don't trust the file name or the size your design tool claims. Measure the file you're uploading:

• Mac Terminal: sips -g pixelWidth -g pixelHeight shot.png prints the exact width and height.
• Any Unix shell: file shot.png prints something like "PNG image data, 1290 x 2796, 8-bit/color RGBA". The RGBA part also warns you about an alpha channel.
• Preview on Mac: open the image and choose Tools > Show Inspector to see its pixel dimensions.
• In the browser: drop a whole folder into the free screenshot size checker. It shows which App Store or Google Play slot each image fits and flags alpha channels, and the files never leave your browser.

Once you know the real size, the cause is usually obvious.

1. The right image in the wrong slot

A 1320 × 2868 file is valid, but only in the 6.9″ slot. Dropping it into the 6.3″ slot fails. Make sure the slot selected in App Store Connect matches the set you're uploading, especially if you export several sizes into one folder.

2. Exported at the wrong scale from a design tool

Design tools often work in points. iPhone screens are 3× their point size, so frames must be exported at 3×:

A 430 × 932 frame exported at 1× or 2× produces 430 × 932 or 860 × 1864, and neither is accepted. In Figma, set the export scale to 3x, or build the frame at full pixel size. The Figma screenshot guide covers export settings.

3. Capturing the Simulator window instead of its screen

A macOS window capture (Shift-Command-4, then Space) includes the window frame and a transparent drop shadow, so the result has the wrong size and an alpha channel. Use the Simulator's File > Save Screen (Command-S) or xcrun simctl io booted screenshot shot.png, which save the device's native pixels. Pick a simulator in the display class you need; Xcode Simulator screenshots explains the options.

4. A real device from a different display class

Screenshots taken on your own phone only match a slot if the phone is in that class. A 1170 × 2532 screenshot, for example, belongs to an optional smaller iPhone slot and fits neither 6.3″ nor 6.9″. Either capture on a matching device or simulator, or place the screen inside a designed screenshot at the right canvas size.

5. An editor or compressor resized the file

Image optimizers, "export for web" presets, and some screenshot tools quietly scale images down. Artboards with bleed or margins (for example 1300 × 2900) also export at the wrong size. Check the final file after every processing step.

6. Off by a few pixels after cropping

Cropping out the status bar, adding a border, or trimming rounded corners changes the pixel count. Edit inside a fixed-size canvas instead of cropping the image itself.

1. Identify the slot you're uploading to and its accepted sizes.
2. Measure each file with sips -g pixelWidth -g pixelHeight *.png or the size checker.
3. Re-export from the source design at the exact size. This is the cleanest fix.
4. If you only have the image, resize it only when the aspect ratio matches. sips -z 2622 1206 shot.png --out shot-6.3.png forces 1206 × 2622 (sips takes height first). Use it for a same-ratio scale, such as 2× to 3×.
5. When ratios differ slightly, scale the width, then pad or crop the height. A 1290 × 2796 image becomes 1320 × 2861 with sips --resampleWidth 1320 in.png --out tmp.png, then 1320 × 2868 with sips -p 2868 1320 --padColor FFFFFF tmp.png --out out.png. Match the pad color to your background.
6. Check for alpha with sips -g hasAlpha out.png and flatten if it says yes. Keep the file in RGB, not a print-oriented CMYK profile.
7. Upload again into the correct slot.

Apple's screenshot specifications state that images can't include alpha channels or transparencies, and that the accepted formats are .jpeg, .jpg and .png.

Google Play doesn't use fixed slots, but its rules catch similar mistakes. Phone screenshots must be JPEG or 24-bit PNG with no alpha, each side 320 to 3,840 px, the long side no more than twice the short side, and up to 8 MB each.

The ratio rule surprises Android developers: a raw 1080 × 2400 screenshot is 2.22:1 and fails. Place it on a 1080 × 1920 or 1080 × 2160 canvas instead. The Google Play screenshot sizes guide and Google Play screenshot requirements cover the details.