« The dimensions of one or more screenshots are wrong »

App Store Connect checks your file against a closed list of pixel sizes. One pixel off and the upload stops. Here is the list, and the three ways people land outside it.

Published: 5 September 2026

The check is exact, and that is the whole story

The error text is unhelpful because it describes a symptom, not a cause. What happens underneath is simple: every upload slot has a short list of accepted pixel dimensions, and your file either matches one of them exactly or it does not. There is no tolerance, no nearest match, no automatic crop.

So the fix is never to re-export « bigger » or « in better quality ». It is to find which number you are meant to hit and hit it exactly.

The list, for iPhone

Landscape is the same numbers reversed. Every value above was read from Apple's own screenshot specifications on 1 September 2026.

The three ways people land outside the list

The wrong slot. By far the most common. A file sized for the 6.5″ class — 1284 × 2778 — is dropped into the 6.9″ slot, which does not accept it. The file is perfectly valid; it is simply in the wrong place.

A size that looks right. 1080 × 1920 is a familiar number from video, and it is not on any iPhone list. 1290 × 2790 is six pixels short of a real size, which is what happens when a design tool rounds a frame.

An upscale. Enlarging a smaller capture to reach the target number technically passes the dimension check and fails everything else: the result is soft, and reviewers see it at full size.

What to do instead

Export at the device's native resolution rather than resizing afterwards. A screen that is 393 × 852 points at @3× is 1179 × 2556 pixels by multiplication, not by scaling — the file comes out of the render at the right size, and there is nothing to correct.

If you only intend to upload one iPhone set, make it a 6.9″ size: Apple scales it down for the smaller classes on its own.

Questions

Why does App Store Connect say my screenshot dimensions are wrong?

Because it compares your file against an exact allow-list of pixel sizes for the display class you are uploading into. It is not a range and there is no nearest match: the file matches one of the accepted sizes exactly, or the upload stops.

Can I just export at a higher resolution to fix it?

No. A bigger file is not a closer match — it is simply a different size that is also not on the list. The fix is to find the exact number for the slot you are uploading into and hit it.

Does the error mean my screenshot was rejected by review?

No. This one happens mechanically at upload, before a human sees anything. Editorial rejections come later and read differently.