Google Play Console
How to make and upload Google Play Store screenshots
Verified against the primary sources below on
Steps
Decide how many you need, per device type
Play Console Help sets a floor and a ceiling:
- Floor: "You must provide a minimum of two screenshots across different device types to publish your store listing."
- Ceiling: "You can add up to 8 screenshots for each supported device type." Device types are phones, 7-inch and 10-inch tablets, Chromebooks, Android TV, Wear OS, Android Automotive OS and Android XR.
Two is enough to publish, not enough to be featured. To be eligible for the large-format recommendation surfaces, Google asks apps for "at least four screenshots with minimum 1080px resolution", at 9:16 portrait (minimum 1080 x 1920) or 16:9 landscape (minimum 1920 x 1080). For tablets and Chromebooks the same page says "you can add a minimum of 4 screenshots".
Make files the Play Console will take
The format rules, quoted from Play Console Help:
- "JPEG or 24-bit PNG (no alpha)"
- "Minimum dimension: 320px"
- "Maximum dimension: 3840px"
- "The maximum dimension of your screenshot can't be more than twice as long as the minimum dimension."
That last rule is the one to read carefully. Most current Android phones are taller than 2:1, so a raw capture from one breaks it on paper. A 1080 x 2340 file and a 1080 x 2160 file both uploaded to a live Play Console listing without an error when we checked in August 2026, so it does not appear to be enforced as a hard gate. That was one check on one listing. If you want no risk at all, 1080 x 1920 meets every rule on the page.
Check a file before you upload it:
# Pixel size and whether the file carries an alpha channel magick identify -format "%wx%h %[channels]\n" screenshot.pngShow the app, then compose around it
Google's guidance is that screenshots "must demonstrate the actual in-app or in-game experience". Stylized frames are allowed, including a design that runs across several images, but Google asks you to "prioritize UI in the first three screenshots as much as possible", and to avoid small text over busy backgrounds because it "will not be visible on many phone screens".
So start from real captures of the screens you want to sell, then add the device frame and a short headline on top. That second part is what the Play Store screenshot generator does: describe the app and a set comes back at the Android sizes we render, read from our device specs:
- Android phone: 1080 x 2340
- Google Pixel 11 Pro: 1280 x 2856
- Samsung Galaxy S26 Ultra: 1440 x 3120
- Android tablet 7": 1200 x 1920
- Android tablet 10": 1600 x 2560
The phone sizes are native panel resolutions, so they sit above 2:1 for the reason covered in the previous step.
Upload them in Play Console
Google puts preview assets on one page:
- Open your app in Play Console.
- Go to Grow users > Store presence > Main store listing.
- Scroll to the Graphics section and find the block for the device type you are filling (phone, tablet, Chromebook and so on).
- Upload the files in the order you want them shown, and add alt text to each one. Google recommends it for screen-reader users, kept to 140 characters or less.
- Save.
Assets added here show on your store listing "across all test tracks", so testers see the new set too.
Send the change for review
Saving the listing does not publish it. A store listing edit lands in Publishing overview under "Changes not yet sent for review", and Google is explicit that "Items are not sent for review until you click Send for review."
This is also how you change screenshots on an app that is already live. A store listing change is its own item on Publishing overview, separate from a release, so a new set does not need a new app bundle.
When this is worth doing
The most common reason new screenshots "do not show up" is that the change was saved but never sent. Play Console collects every edit that needs review into one list on Publishing overview and holds it there until you send it, which is easy to miss when the listing page itself says the change was saved.
After it is sent, it still has to pass review. Google says updates are published "as soon as possible", that "certain apps may be subject to extended reviews" of up to seven days or longer in exceptional cases, and that if managed publishing is turned on, an approved change waits until you publish it yourself. Store listing changes are one of the things managed publishing holds back.
The other surprise is where the screenshots appear. Google uses them beyond your listing, "for instance in search or on the homepage", and shows them after the preview video when there is one. That is why the first three frames carry more weight than the rest.
Sources
- Add preview assets to showcase your app | Google, Play Console Help (primary)
- Control when app changes are reviewed and published | Google, Play Console Help (primary)
- Publish your app | Google, Play Console Help (primary)
Go deeper
Related guides
- How to make App Store screenshots for an Expo appEAS builds and submits your binary, and EAS Metadata pushes your store listing, but Expo documents screenshot upload as unsupported in EAS Metadata. Screenshots stay a separate step you handle in App Store Connect or a third-party tool, and an Expo project needs two sets because it ships to both stores.
- How to fix "The dimensions of one or more screenshots are wrong" in App Store ConnectApp Store Connect accepts a fixed list of pixel sizes per display slot, not a range or an aspect ratio. Read the file's real pixel dimensions, find the exact pair on Apple's list for the slot you are uploading to, and re-export at that size. Scaling an existing file to fit almost always lands one pixel off.