Most visitors decide on your app before reading a word of the description. The screenshots do the selling — here is how to make them earn the install.

The first three do the work

On a product page, roughly the first three screenshots are visible without scrolling — and most visitors never scroll. Treat them as your pitch: the core promise on shot one, the "how" on shots two and three. Everything after that is for the already-convinced.

A useful test: cover the text of your listing and look at the first three images. If a stranger cannot say what the app does and why it is better, the set is not done.

Get the sizes right

Apple currently keys everything to the 6.9-inch iPhone display — 1320 × 2868 pixels portrait — and scales down for smaller devices if you do not upload separate sets. You can provide up to ten screenshots per device size. iPad needs its own 13-inch set if you support it.

Two practical rules: design at the largest required size, because downscaling is free while upscaling looks soft — and export lossless PNG, since the store re-compresses anyway.

Captions sell outcomes, frames sell polish

One benefit per shot, written as an outcome: "Never miss a deadline" beats "Calendar view". Put big type at the top — captions get read at thumbnail size in search results. Show real UI in a device frame: floating raw rectangles read as unfinished, a framed device reads as a product. And keep one consistent background system across the set, so the row looks designed instead of assembled.

A workflow that does not eat a day

You do not need a design-tool marathon: upload your screens to AppMockr, pick a device and scene, add captions, and export App Store-ready PNGs. Iterate on the caption wording — that is where conversion hides — instead of on pixel plumbing. When you update the UI, re-exporting the whole set takes minutes, so your listing never trails the product.