Screenshots sell your app better than any sentence you write. Most visitors decide from the first two frames without scrolling and without reading a word of your description. Yet screenshots are usually an afterthought — a few raw captures with no caption, in whatever order the export tool spat them out. Fixing that is one of the highest-return things you can do to a listing.
Let us get the specs out of the way first, then talk about the part that actually moves conversion: order and message.
The specs (2026)
| Spec | App Store | Google Play |
|---|---|---|
| Max screenshots | 10 per device | 8 per type |
| Phone reference size | 6.7″ = 1290×2796 | Min 1080px on short side |
| Feature graphic | — | 1024×500 (required) |
| Icon | 1024×1024 (in build) | 512×512 |
| Localization | Per language | Per language |
A few things people trip on. The App Store 6.7″ size at 1290×2796 is the current iPhone reference — upload at exactly that resolution to avoid resampling artifacts. Google Play's feature graphic is mandatory and has no App Store equivalent, so it is easy to forget; it appears at the top of your listing, so a blank or ugly one is very visible. Both stores accept fewer than the maximum, but giving them only two or three when competitors show eight looks thin.
The first two frames are the ad
Assume the majority of viewers see only your first two screenshots — the ones visible without scrolling in the search results and at the top of your page. Everything after frame two is for the minority who are already interested. So your two strongest ideas go first, not your onboarding flow and not your settings screen.
Frame one should answer “what is this and why should I care?” in a single glance: your core value, shown in the app, with a short caption. Frame two builds on it with the next most compelling thing. Everything else is supporting evidence.
Caption every frame
A bare screenshot makes the viewer do the work of figuring out what they are looking at. A short caption does it for them. Keep captions to a few words — a benefit, not a UI label. “See your strength trend over months” beats a raw chart with no context; “Analytics Screen” is worse than nothing.
| Weak caption | Strong caption |
|---|---|
| Home screen | Log a workout in two taps |
| Statistics | Watch your PRs climb over time |
| Settings | Your data stays on your device |
Order tells a story
Think of the sequence as a short pitch, not a gallery. A reliable order:
- The core value — the one thing your app is best at.
- The second hook — the next reason to care.
- Depth — a feature that shows the app is serious.
- Proof or trust — social proof, privacy, an integration people recognize.
- The ask — a clean final frame that invites the tap.
You do not need all ten slots. Five or six strong, ordered frames beat ten random ones. Every extra frame that does not earn its place just dilutes the story.
Show the real app
Heavily stylized frames that hide the actual interface are both a conversion risk and a rejection risk. If your screenshots look nothing like the app, install-to-retention suffers because expectations were set wrong — and both stores can reject screenshots that misrepresent the product. Frame the real UI attractively: a device bezel, a clean background, a caption. Do not fake a UI that does not exist.
Localize the images, not just the store text
If your captions are baked into the images — and they usually are — every localized listing needs its own screenshot set with translated captions. Upload English captions to your Japanese listing and that is exactly what Japanese users see. Managing separate screenshot sets per language and per device is tedious enough that it gets skipped; a grid that shows every set against each store's size requirements (which is one of the things AppBoard organizes) keeps it from slipping.
Do not forget the preview video
Both stores support a short video above your screenshots, and it plays a different role than a static frame. The App Store allows up to three app preview videos (15–30 seconds) that autoplay, muted, right in search results — so the first few seconds have to make sense without sound. Google Play takes a promo video via a YouTube link that sits with your feature graphic. A video is not mandatory and a weak one hurts more than no video, so only ship one if it genuinely shows the app in motion doing something a screenshot cannot. If your app is mostly static screens, spend the effort on stronger frames instead.
Whatever you ship, treat visuals as an experiment, not a one-time task. Change the first frame, wait a couple of weeks, and watch whether your install rate moves. Screenshots are the highest-leverage thing to test because they carry most of the conversion — a better frame one can lift installs more than any keyword change you make that quarter.
A test you can run today
Show a friend who has never seen your app just the first two screenshots, for three seconds, then hide them. Ask what the app does and who it is for. If they can answer, your frames are working. If they hesitate, your first two frames are not pulling their weight — and that is where nearly all of your conversion is won or lost.
Try this workflow in AppBoard
See how AppBoard handles listings, versioning, keywords, and reviews for both stores — no signup required.
Open the live demo