App Store Connect screenshot rejected? Fix it fast

Why does App Store Connect reject my correctly-sized screenshot, and how do I fix it?

Pixel dimensions are only the first of several checks Apple's validator runs. Even a file exported at the exact 1320x2868 spec can fail if it carries a hidden alpha channel, sits in a CMYK profile, or is uploaded to a shelf that expects a different aspect ratio. The four causes worth investigating before anything else are file metadata (color space, alpha), the device slot you picked in App Store Connect, batch upload race conditions, and the rare but real server-side parser outage on Apple's end.

Content rejection vs upload error: two different problems

Upload error signals: the file never attaches, you see IMAGE_TOOL_FAILURE, "Image dimensions are not valid", or a progress bar that snaps back to zero. These happen instantly, before a human has looked at anything.

Content rejection signals: the file uploads fine, the build submits, and then days later you get a Resolution Center message citing guideline 2.3 (accurate metadata), misleading copy, or showing UI that does not exist in the build. These are review decisions, not parser failures, and the fix is to re-shoot the screenshot — not to re-export it.

Map the error message to its real cause

Match the message you actually see to the row below before applying any fix. Most teams burn an afternoon on the wrong cause because two different errors look similar in the UI.

How to strip the alpha channel and fix the color space

Check for an alpha channel. In Preview on macOS, open the file and choose Tools → Show Inspector; if the "Has alpha" row says Yes, the PNG carries transparency Apple will reject. In Photoshop, look at the Channels panel — anything beyond R, G, B is an alpha. The fix is to flatten the file onto a solid background and re-export as 8-bit PNG with the alpha layer removed.

Convert CMYK or P3 to sRGB. A screenshot exported from a print-oriented document, or a designer mockup that inherited a Display P3 profile, can render correctly on screen but fail the upload. In Preview, choose Tools → Assign Profile → sRGB IEC61966-2.1. In Photoshop, Edit → Convert to Profile → sRGB. Re-upload the converted file; this alone resolves a large share of IMAGE_TOOL_FAILURE cases.

The ordered troubleshooting checklist

Steps 1–4: the file itself.

Steps 5–8: the upload path.

When nothing works: if every file check passes and you have cycled the browser, you are almost certainly looking at a server-side issue on Apple's end. Delete the half-uploaded asset, wait an hour or two, and re-upload one file at a time. Apple's developer forums document recurring server-side upload outages whose only resolution is patience.

App Store screenshot software that works on Windows without a Mac

Why Mac-only workflows fail Windows devs. The standard recommendation — Xcode simulator, Cmd+S — assumes you have a Mac sitting under your desk. Cross-platform indie developers who build on Windows are left with a choice between renting a Mac in the cloud, uploading raw captures to a browser-based generator, or wrestling with image editors that do not know Apple's latest spec.

What a local export tool handles for you. A native desktop app that ships current store presets exports each frame at the integer dimension Apple requires, flattens to 8-bit sRGB PNG with no alpha channel, and applies the correct file format — every export is upload-ready by default. The raw UI never leaves your machine, which also closes the pre-launch leak surface created by uploading screenshots of unreleased features to a third-party server.

For the full per-device pixel table referenced throughout this article, see the App Store screenshot sizes 2026 reference. Two companion articles — one on the privacy tradeoffs of uploading unreleased UI to a web tool, and one on a complete pre-submission QA checklist for every store — are coming soon.