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.
What it photographs
Section titled “What it photographs”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.
The sizes it produces
Section titled “The sizes it produces”| Store | Frame | Output |
|---|---|---|
| App Store | iPhone 6.9” | 1290 × 2796 |
| App Store | iPad 13” | 2064 × 2752 |
| Google Play | Phone | 1080 × 1920 |
| Google Play | 7” tablet | 1200 × 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 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.
Which member they are taken as
Section titled “Which member they are taken as”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.
“Some screens look empty”
Section titled ““Some screens look empty””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.
Where they end up
Section titled “Where they end up”In the export bundle, numbered in order:
- App Store:
screenshots/en-US/01-….png—delivermatches them to devices by their dimensions, so no naming convention is needed beyond the ordering. - Play:
images/phoneScreenshots/andimages/sevenInchScreenshots/, split by the device each came from.
Generated screenshots are on Pro and above, and included during the trial. 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 — is on every plan.
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| “This app has no screens” | Nothing is placed in the bottom navigation | Place a feature in the builder |
| Screens show sample people | No preview user, or no site connected | Set one under Global Settings → Connections |
| “Some screens look empty” | A REST group is switched off at your site | Enable it, then retake |
| It takes several minutes | It drives a browser through every screen | Expected; the page updates when it finishes |
| The button says the plan does not include it | Free accounts do not have it | Everything else on the page still works |