Skip to content

Store screenshots

Both stores refuse a submission without screenshots, at exact dimensions, and making them by hand means installing the app, taking shots on a device you own, and cropping each one to a size you have to look up.

Take screenshots on the Store submission page does it from the app itself.

The screens you placed in the bottom navigation, in the order they appear, best first — a feed or a directory before a settings screen, because a listing’s job is to show what the community does.

Two rules keep the results honest:

  • A screen only signed-out visitors can see is skipped. It renders a sign-in form, and a listing led by a login screen is the most common bad screenshot in this category.
  • Every shot is checked for content. A screen that comes back nearly empty is reported rather than kept quietly — see below.
StoreFrameOutput
App StoreiPhone 6.9”1290 × 2796
App StoreiPhone 6.3”1206 × 2622
App StoreiPad 13”2064 × 2752
Google PlayPhone1080 × 1920
Google Play7” tablet1200 × 1920

The App Store shots are the raw capture: Apple wants those exact pixels and nothing else, so nothing is drawn on top of them.

The iPhone 6.3” set fills App Store Connect’s 6.1” or 6.3” display slot, which accepts 1179 × 2556 or 1206 × 2622. Left empty, Apple shrinks your 6.9” shots into it; filled, the listing shows each phone a screen laid out at its own size.

The Play shots are placed in a device frame on a shorter canvas, and that is not decoration. Play rejects a screenshot whose long side is more than twice its short side. Your app’s screen is 2.17:1, so an uncropped capture is legal on the App Store and rejected by Google. Framing it keeps the whole screen and still fits.

Each store keeps a light set and a dark set side by side. The Light | Dark switch on the Screenshots card only changes which set you are looking at — it never takes anything. Take screenshots (or Retake) captures the set on show and leaves the other one alone, so retaking the light set never costs you the dark one.

Download all and the export bundle carry the set on show. A listing is one look, so they never mix the two.

Whichever member you chose as the preview user under Global Settings → Connections. Screenshots show what that member sees, so pick an account with a filled-in profile and some activity.

With no preview user set — or no site connected — the capture falls back to the built-in sample community. The screens are fully populated and look right; they are not yours.

The warning that matters most. Every Memberside REST endpoint is off by default, and a feature whose group is switched off at your site renders an empty state — which photographs exactly like a working product with nothing in it.

When a screen comes back with almost no content, it is flagged by name rather than silently included. Check the feature on your site, then retake.

In the export bundle, numbered in order:

  • App Store: screenshots/en-US/01-….png — deliver matches them to devices by their dimensions, so no naming convention is needed beyond the ordering.
  • Play: images/phoneScreenshots/ and images/sevenInchScreenshots/, split by the device each came from.

Download all on the Screenshots card gives you a zip of just the images — your-app-apple-screenshots.zip — with a folder per device:

iPhone 6.9/01-feed.png
iPhone 6.9/02-members.png
iPhone 6.3/01-feed.png
iPad 13/01-feed.png

Numbering restarts in each folder, because each folder is one device’s listing and both stores order a device’s screenshots by filename. Take them in that order and the product page reads the way the app does.

This is the one to use when you are filling in App Store Connect or Play Console by hand, or sending the shots to a designer. The export bundle is for running deliver or supply, and puts the same images in the folders those tools read.

Generated screenshots are on Pro and above. A capture holds a browser against your site for a few minutes, which is the same kind of cost a build is.

Everything else on the Store submission page — the listing, the review notes, the readiness checks, the export, and downloading screenshots you have already taken — is on every plan.

SymptomCauseFix
“This app has no screens”Nothing is placed in the bottom navigationPlace a feature in the builder
Screens show sample peopleNo preview user, or no site connectedSet one under Settings → Connection / API Keys
“Some screens look empty”A REST group is switched off at your siteEnable it, then retake
It takes several minutesIt drives a browser through every screenExpected; the page updates when it finishes
The other theme’s button is greyed outOne capture runs at a time per storeWait for the running set to finish
The button says the plan does not include itFree accounts do not have itEverything else on the page still works