App Store Screenshot Requirements Checklist: Verify Everything Before You Upload
Store Connect Studio ·
A rejected screenshot is rarely a design problem — it is usually a detail out of line: a few pixels off, a leftover transparency channel, a missing language. Run through this checklist before submitting and you save a lot of time re-queuing for review.
Quick answer
Before submitting, check four things: sizes and counts match current requirements, the format carries no leftover transparency, every published device and language is covered, and the content matches the build — pass all four and rejection is unlikely.
Sizes and counts: match the official requirements first
App Store Connect validates sizes to the exact pixel and does not accept proportionally scaled results. Each device class you ship to usually needs its own set, and each has its own minimum and maximum count; the exact numbers change with devices and policy, so always follow what App Store Connect currently states.
Rather than memorizing numbers that may already be outdated, read the size and count each field asks for right in the submission screen — that is the only reliable reference.
Format and technical details
The common formats are PNG and JPEG. The trickiest trap is a leftover alpha channel: a PNG exported from Figma, Sketch or a canvas can carry transparency data even when every pixel is opaque, and the upload is then flagged as an invalid format.
The fix is to flatten the image onto a solid background or export straight to JPEG; also make sure color and dimensions meet the requirements, and keep the status bar free of distracting real-carrier or full-signal details.
Device and language coverage
Every region you publish to is best served with screenshots in its own language; leaving only English screenshots in the English region and nothing elsewhere noticeably hurts conversion.
On the device side, if your app supports a given form factor (iPadOS, foldables and so on), you usually need to provide a matching set; device classes do not substitute for one another, so go by the current list in the submission screen.
Pre-submission self-check list
The list below is meant to be worked through directly; each item maps to one of the most common rejection reasons.
- Sizes match the current requirements exactly, with no proportional scaling.
- The count falls within the range that field allows.
- The image carries no leftover transparency (flatten or convert to JPEG if needed).
- Every region you publish to has screenshots in its language.
- Every supported device form factor has its own set.
- The screenshots match the build you are about to submit and show no unreleased features.
- The status bar is clean, with no real carrier or odd battery details to distract.
FAQ
What causes most screenshot rejections?
Mostly three: sizes off by a few pixels, a leftover transparency channel in the PNG, and missing languages. Checking these three before submitting heads off most problems.
Does every language need its own screenshots?
Ideally yes. Every region you publish to should have screenshots in its language; English-only weakens conversion elsewhere, so at minimum make sure each region has a usable set.
The size is right, so why does the upload still fail?
Usually a leftover alpha channel, or a color/format mismatch. Flatten the image onto a solid background or export as JPEG and retry — that normally clears it.
Do I need a set for every device?
Usually each form factor needs its own set, and they do not substitute for one another. Which devices are required depends on the current list in the App Store Connect submission screen.
Turn pre-submission checks into a single step
Store Connect Studio bundles device canvases and official sizes, so size, transparency and missing-language problems surface before export — edit on Mac or iPhone and sync to App Store Connect in one click.