Table of contents
- Quick nav
Store Preview Images Explained: How to Design App Store & Google Play Preview Screenshots
What “preview image” means in store listing work
Developers searching for preview images are rarely asking for a single file type. In practice the phrase covers the static visuals shoppers see on a store product page:
| Phrase people use | Usually means | Not the same as |
|---|---|---|
| App Store preview images | iPhone/iPad screenshots | App Preview videos |
| Store listing previews | Phone screenshots / intro images on Android stores | Icon or splash only |
| Google Play “preview” assets | Phone/Tablet screenshots + Feature Graphic | Promo video alone |
| Filing / copyright “screenshots” | Raw UI captures for paperwork | Marketed five-frame sets |
This guide is about static store preview images (screenshots and banners). It does not re-litigate preview video vs screenshots for conversion — that is a separate topic. If you need video specs, use a preview-video guide. Here the job is: how many static frames, which sizes, and how to design a shelf that sells.
How this differs from videos and pure size charts
- Preview images (this article): static, scannable, drive the first impression;
- Preview videos: motion and task flow; higher production and review cost;
- Size-only references: pixels without narrative — necessary, but not enough to ship.
For most indie apps the order is: ship valid preview images first, then decide whether a video belongs above the fold. A weak static set will not be rescued by a video.
Spec cheat sheet (verify live consoles)
Hardware classes change yearly — treat Connect / Play Console labels as source of truth.
Apple App Store (screenshots = preview images)
| Item | Typical expectation |
|---|---|
| Primary fight | iPhone Dynamic Island display classes (e.g. Medium Display ~6.7") |
| Common pixel example | Portrait 1290 × 2796 (confirm in Connect) |
| Count | Up to 10 per device class; plan 3–5 to tell the core story |
| Formats | JPEG or PNG |
| iPad / Mac | Add when the binary supports those devices |
In App Store Connect, App Previews (video) and Screenshots are separate. Empty screenshot slots block submit whether or not you have a video.
Google Play
| Asset | Role | Common spec |
|---|---|---|
| Phone screenshots | Detail-page story | At least 2; edges usually 320–3840 px — ship sharp verticals |
| Tablet screenshots | Large-screen listing | Provide if you optimize for tablets |
| Feature Graphic | Search / browse banner | 1024 × 500 |
| TV / other | Device-specific pages | As needed |
In casual speech, “Play preview images” often lumps screenshots and the Feature Graphic together: screenshots narrate features; the banner pulls attention in lists.
Other Android stores
OEM stores (Huawei, Xiaomi, OPPO, vivo, and regional stores) differ on frame count, max file size (some want under 1MB per image), and framing rules. Shared baseline:
- Prepare 4–5 vertical UI previews;
- Avoid absolute claims and unverifiable rankings in caption text;
- Treat login / permission screens carefully for privacy review norms.
For multi-store shipping, maintain one master artboard plus a per-store export checklist instead of redesigning from scratch each time.
A five-frame preview narrative
The same story spine works on Apple and Google (trim or extend as needed):
| Frame | Job | Copy direction |
|---|---|---|
| 1 | Value proposition | Who it is for and what pain it removes — in one line |
| 2 | Core job-to-be-done | The screen users open every day |
| 3 | Differentiator | The capability competitors lack |
| 4 | Proof or context | Real ratings, metrics, or a credible scenario |
| 5 | Soft call to action | Start free / try now — within ad and store policies |
Design rules that keep previews converting:
- Frame one must read at thumbnail size — headline weight beats decoration;
- On-screen UI must be real — fake prototype marketing burns trust and review risk;
- Keep margin tokens identical across the set so the gallery feels like one campaign;
- Localize copy before layout — longer English/German lines should shrink type, not steal safe padding.
Production pipeline: capture → compose → upload
- Pick target slots first — e.g. App Store Dynamic Island Medium Display + Play phone screenshots + Play Feature Graphic.
- Capture clean UI from Simulator or device; strip noisy notifications, test accounts, and unmasked personal data.
- Compose on locked artboards — fixed canvas, headline band, device scale.
- Preflight exports — resolution, file weight, no unintended transparency (Play can reject transparent screenshots), no clipped type.
- Upload per localization — clear the default language, then sync others.
- Swipe-test on a real phone in the live store UI, not only in the console thumbnail strip.
When you need framed multi-size exports quickly, write the caption script first, then batch through one template so every channel inherits the same rhythm.
Frequent preview-image failures
| Failure | Symptom | Fix |
|---|---|---|
| Wrong size slot | Console blocks save/submit | Re-export to the listed pixels |
| Feature pile-up, no promise | Five settings screens | Rewrite frame one as a benefit |
| Policy-risky copy | Absolute claims, medical promises, fake ranks | Edit to store and advertising rules |
| Feature Graphic used as a screenshot | Odd Play browsing presence | Banner = brand; screenshots = product story |
| One pixel set, untranslated overflow | English clipped on a Chinese layout | Per-language line checks |
Paperwork screenshots for filings or software copyright often require unadorned UI without marketing captions — keep a separate “compliance plain” export set from your store preview set.
How this fits related guides
- Stuck on a specific Connect error (Dynamic Island Medium Display, etc.) → use the matching fix article;
- Gallery feels sparse or cramped → read screenshot gap / spacing design;
- You only need pixel matrices → size guides;
- You need motion → preview video guides.
Treat preview images as a shelf visual system: screenshot narrative + (on Play) banner reach + per-store count and weight constraints — planned once, exported many times.
Takeaway
Store “preview images” are your static shelf: correct slots, a clear five-frame story, and honest UI. Separate them from preview videos and from filing plain-shots, satisfy App Store / Google Play / regional Android rules on count and size, and lock margins on a master template. When you are ready to batch framed previews at store resolutions, AppShot Maker can generate the sized exports so you spend time on the story instead of re-layout.