AppScreenDesign

App Store screenshots

How to Order App Store Screenshots

Screenshot order is the part of a store listing you can fix in an afternoon and measure for as long as the build is live. The panels are not a gallery: on iOS, search results show the first three portrait screenshots side by side before anyone taps through, so the sequence has to survive being read at thumbnail size, in order, without the description.

By Keymaker Technologies LLC · Published

The first three panels are the listing

Apple renders the leading portrait screenshots beneath the app header in iOS search results, and the rest only appear after a tap. Landscape phone and tablet sets surface a single wide frame instead. That asymmetry decides the order: whatever must be understood before the tap belongs in panels one to three, and panels four to ten are for the visitor who already opened the product page.

The practical test is the same one the store applies. Shrink the set to thumbnail width, cover the app description, and read only the headlines in sequence. If the three lines do not describe one product doing one job, the order is wrong even when every individual panel looks good at full resolution. The iOS preview simulator renders that exact truncation without uploading anything.

Panel one states the job, not the brand

A first panel that shows only a logo and a tagline asks the viewer to already know what the app does. Put the product on screen instead: one device, one screen of real UI, one headline of five words or fewer. The headline names the outcome, and the capture shows the interface that delivers it.

Keep the composition simple enough to read at 200 pixels wide. Two type sizes are enough — a headline and a short supporting line — and the device should occupy most of the canvas. The iPhone 6.9-inch slot is 1320 × 2868 px, so a capture placed at 70–80% of the frame width still leaves room for a headline that stays legible in the search rail. Exact per-device numbers live in the iPhone 6.9-inch screenshot sizes reference.

Panel two shows the work, panel three shows the result

The second panel should answer "how", and the third should answer "and then what". That is a sequence rule, not a template rule: a notes app can pair a capture of the editor with a capture of a shared, finished document; a fitness app can pair a live workout with the weekly summary it produces. The pair works because the second panel is unfinished business and the third one resolves it.

Resist the urge to spend panel three on a feature grid. Feature lists are read after the decision, not before it. If the product has a genuinely unusual mechanic — a 3D hardware view, a connected panorama, a live collaboration cursor — that is the "how" panel, because it is the part a competitor screenshot cannot imitate. Connected panoramic templates exist for exactly that case: one idea spread across seams instead of six unrelated screens.

Proof belongs in the middle, and only if it is real

Awards, press quotes, ratings and "featured by" badges are proof, and proof works best once the viewer already understands the product — usually panels four and five. They work badly as an opening because a badge says nothing about the job the app does.

Only ship proof you can point to. App Store ratings change and press quotes age; a badge rendered into a screenshot cannot be corrected without a new export, while a rating shown by the store itself updates on its own. If there is no third-party proof yet, use the slot for a second workflow instead. A screenshot that claims an award the app does not hold is a review risk, not a conversion tactic.

Panels four to ten carry depth, in release order

App Store Connect accepts up to ten screenshots per device size, and the tail of the set is where you cover the workflows a specialist buyer checks: settings, export formats, integrations, accessibility. Order that tail by how often the feature decides a purchase, not by how proud the team is of it.

The tail is also where localization diverges. The value story can keep the same order in every locale, but headline length cannot: German expands a short English line by roughly a fifth to a third, while Japanese often contracts it. Re-check each locale at thumbnail width rather than assuming the English layout survives translation. The size and format guide covers the export side of the same workflow, including why a 32-bit RGBA PNG is rejected even when it looks opaque.

Order lives in the upload sequence

There is no separate ordering field. The sequence you upload is the sequence the store displays, and you can drag panels into a new order in App Store Connect afterwards — the listing updates on the next review-free metadata save. Build the set in the order you intend to ship, then reorder only when a specific panel underperforms.

One consequence: never export panels one at a time in a different order from the one you planned. A set assembled from separate exports drifts the moment someone re-exports a single panel. Keep the whole sequence in one editable project, export it together, and the order stays reproducible. The 3D browser studio keeps every panel of a project in one document for that reason.

Questions

Common questions.

Does screenshot order matter in App Store search?

Yes. iOS search results render the first three portrait screenshots side by side before a tap, while landscape phone and tablet sets surface one wide frame. Panels four to ten are seen only on the product page.

Can I reorder screenshots after the app is live?

Yes. Drag the screenshots into a new order in App Store Connect and save the listing. Reordering screenshots is a metadata change and does not require a new binary, though localizations are re-checked per storefront.

How many screenshots should I upload?

Apple accepts one to ten screenshots per device size. Three to six is usually enough to state the job, show the workflow and prove the result; the rest should earn their place with a workflow a buyer actually checks.

Should every localization use the same screenshot order?

Keep the same order of ideas, but re-check each translated headline at thumbnail width. German expansion and Japanese contraction change how much of a five-word English line fits, and the panel that reads cleanly in English can clip in another locale.

Where to go next

Build the sequence once.
Export it at every store size.

Compose every panel in one editable project, then export the exact presets App Store Connect expects.

Open the editor