Lorixen.
EN

App Store and Google Play screenshots that earn downloads

Short answer: On the App Store you need at least one screenshot for the medium iPhone with Dynamic Island size (and the 13-inch iPad if your app runs on iPad), with up to ten per size. On Google Play you need a 1024×500 feature graphic and screenshots, and at least four 1080px-plus phone screenshots if you want to appear in Play's large-format recommendations. Beyond the rules, treat the first few frames as an advert: one benefit per screenshot, a short caption, real app screens, and a test of two versions once you have steady traffic.

Your store listing is the last page a person sees before tapping "Get" or "Install". Most visitors won't read your description; they'll glance at the icon, swipe a few images and decide. That makes screenshots the part of app marketing a small team can improve in an afternoon and test properly over a month. Below are the current requirements from each store, a checklist per store, and a storyboard you can copy.

App Store checklist

Requirements below are from Apple's App Store Connect help, as of November 2026.

Screenshots

  • [ ] At least one, and up to ten, screenshots per device size, in .jpeg, .jpg or .png.
  • [ ] iPhone: at least one screenshot for iPhone with Dynamic Island (medium display). Accepted portrait sizes on that row are 1179 × 2556 or 1206 × 2622 pixels (landscape is the reverse).
  • [ ] iPad, if your app supports it: at least one for the 13-inch display, at 2064 × 2752 or 2048 × 2732 pixels portrait.
  • [ ] No alpha channels or transparency.
  • [ ] If your interface is the same across devices and languages, upload only the highest required resolution; App Store Connect scales it down for smaller sizes.
  • [ ] Screenshots must follow the App Store Review Guidelines.

Apple's page also lists a new foldable size and notes that, from April 2027, those screenshots will be required for apps built with a specific later SDK. If you're planning a 2027 update, check that row before you design.

App previews (video)

  • [ ] Up to three previews per supported device size and language.
  • [ ] Formats: .mov, .m4v or .mp4 (H.264), or .mov for ProRes 422 HQ.
  • [ ] Previews always appear before screenshots, even if you reorder them, so the preview's opening seconds and poster frame become your first impression.
  • [ ] Choose the poster frame deliberately; it's shown on the product page and during install.
  • [ ] Allow up to 24 hours for processing.
  • [ ] A preview in a different aspect ratio from your screenshots appears in a separate "A Closer Look" section instead.

Google Play checklist

From the Play Console help page on preview assets, as of November 2026.

Feature graphic (required)

  • [ ] JPEG or 24-bit PNG, no alpha, 1024 × 500 px.
  • [ ] It's used as the cover for your preview video and in large-format collections, so keep key content away from the edges and avoid fine detail.
  • [ ] Don't simply repeat your icon; Google suggests branding that extends the icon rather than duplicating it.

Screenshots

  • [ ] A minimum of two screenshots across device types to publish, up to eight per device type.
  • [ ] JPEG or 24-bit PNG, no alpha, between 320 and 3840 px, with the long side no more than twice the short side.
  • [ ] For recommendation formats: at least four app screenshots at 1080 px minimum (9:16 portrait at 1080 × 1920 or 16:9 landscape at 1920 × 1080).
  • [ ] Show the real in-app experience; Google's guidance asks screenshots to depict actual features and content.
  • [ ] Tablets and Chromebooks: at least four, 1,080 to 7,680 px, and avoid extra text that might be cut off on some screens.

Preview video

  • [ ] One video via a YouTube URL (not a playlist or channel link, no timecodes).
  • [ ] Localised versions for key markets if you can.

Text on images

Google's guidance warns against copy that suggests rankings, awards, testimonials, price or promotions, and against time-sensitive wording that dates quickly. "Number one app" or "50% off this week" on a screenshot is asking for a rejection or an out-of-date listing.

The six-screenshot storyboard

Use this for both stores. Each frame does one job.

Frame Job Caption pattern Screen to show
1 The promise "[Outcome] in [timeframe/steps]" The most satisfying screen: the finished result
2 How it works "Just [action]" The core action, mid-flow
3 The differentiator "Only [thing you do differently]" The feature competitors lack
4 Proof of depth "[Number] of [things] built in" (only if true) A list, library or settings view
5 Personal fit "Made for [audience/use case]" A screen tailored to that audience
6 Reassurance "Works offline / syncs across devices / private by design" (only if true) The relevant setting or sync state

Writing captions

  • Five to seven words. People swipe fast.
  • Benefits over features: "Never miss a dose" beats "Push notification scheduler".
  • Same phrasing as your app's actual buttons where possible, so the screenshot matches what they'll see.
  • Big enough to read on a phone thumbnail, which is far smaller than the image you design.

Why order matters

People decide in the first two or three images, before they've seen everything. Put your strongest frame first, and don't spend frame one on a logo or "Welcome to…" splash.

A hypothetical example

A small UK recipe-planning app might run: (1) "Your week's dinners, planned in a minute", (2) "Tick what's in the fridge", (3) "Shopping list sorted by aisle", (4) "Hundreds of family recipes", (5) "Made for busy weeknights", (6) "Syncs with your partner's phone". That's illustrative, not a real app.

Localisation

Both stores support localised assets. Apple's previews and screenshots can be uploaded per language, and if a localised preview is missing, the next best available language is shown. On Play, localised graphics also affect testing: people viewing a language with its own localised graphics are excluded from your default graphics experiments.

At minimum, translate captions, not just descriptions. Screenshots with English text in a German listing look like an afterthought.

Test, don't guess

  • App Store product page optimisation lets you test up to three alternative sets of icons, screenshots and previews against your current page; each is shown randomly to a share of visitors you define. Apple notes the app must be ready for distribution, and that releasing a version mid-test may affect results.
  • Google Play store listing experiments let you run one default graphics experiment or up to five localised experiments at once, testing the icon, feature graphic and screenshots. Results may say "More data needed" if traffic is low.

With modest traffic, test one big change at a time, such as a different first frame, and leave it running long enough to get a clear result.

FAQ

Can I use the same screenshots for iPhone and Android?

The ideas, yes; the files, usually not. Sizes differ, and Android users expect Android interface details. Re-export from the right devices or frames.

Should screenshots include device frames?

Optional on phone stores. Google says Wear OS screenshots must not use device frames, so check per platform.

Is a preview video worth making?

If your app's value is easier to show in motion (games, editing, fitness), yes. On the App Store it plays before screenshots, so a weak video hurts more than none.

How often should I update screenshots?

Whenever the interface changes noticeably, and after each test you win.

A sharp first screenshot is one of the cheapest wins in app marketing, and we'd be glad to storyboard and test yours with you.

Sources

WhatsAppLet’s talk