Every App Store screenshot size, exactly.

What you actually need

Two sets, at most. A 6.9-inch iPhone set, and a 13-inch iPad set if your app supports iPad. Apple derives the smaller display classes from the largest one you supply, so producing the full matrix by hand is work nobody is asking you to do.

The table below is the complete accepted list. Generate everything if it is free to do so — it removes a category of support question — but do not treat it as a checklist you have to fill in.

iPhone and iPad, portrait

Landscape

Every size above has a landscape counterpart with the axes swapped. Landscape screenshots are optional, and worth producing only if your app is genuinely used that way — a landscape set for a portrait app reads as padding.

The rules that actually cause rejections

• Exact pixels, not aspect ratio. The comparison is on the integer width and height. There is no tolerance band.
• Consistency within a class. All screenshots in one display class must be identical in size.
• Ten per class, per language. The limit is per localization, so a ten-language listing can carry a hundred iPhone files.
• No alpha channel. Flatten transparency before upload; a PNG with an alpha channel can be refused.

The status bar question

Apple does not require a specific status bar, and it does not require 9:41. What it does notice is a set where the time, battery and signal change between panels, because that reads as screenshots taken on a real phone over twenty minutes rather than as designed marketing material. Pick one state and hold it across the set. The dimensions guide covers the adjacent technical failures.

Where these numbers come from

This page is rendered from editor/schema/presets.ts, the versioned registry the export pipeline itself uses. When Apple adds a display class, the registry changes and this page changes with it. That is the whole reason it is worth reading: a hand-typed size table is correct on the day it is published and slowly wrong afterwards.