For the Play Console

Google Play screenshot generator for Android listings

Play does not hand you a list of device sizes. It hands you a pixel range, two aspect ratios and a set of content rules. This builds the whole listing to them — phone and tablet screenshots, the 1024×500 feature graphic, and a ZIP the Console takes without a resize round.

Start free Browse templates

What the Play Console checks

Google's spec is a range rather than a list of devices, which makes it easier to satisfy and easier to get subtly wrong. Four rules do most of the rejecting: Dimensions. Every side between 320px and 3840px, and the long side no more than twice the short side. That last clause quietly rules out tall, narrow "story" crops. Format. JPEG or 24-bit PNG, with no alpha channel. A transparent background that looks fine in your design tool is a rejection at upload. Count. At least two screenshots across different device types before you can publish, and up to eight per device type after that. Google recommends at least four per type at 1080px or better. Content. Screenshots have to show the actual in-app experience, taglines must not cover more than 20% of the image, and call-to-action copy — "Download now", "50% off" — is not allowed.

Then there is the asset most listings treat as an afterthought: the feature graphic . It is 1024×500, it is required for every listing, and it is the banner Play puts above your screenshot strip — and uses as your app's stand-in wherever it gets promoted. It is a full canvas here, in the same project as the screenshots, sharing the same type and palette.

Play Store asset sizes by surface

Phone screenshots and the feature graphic get you published. The rest unlock the listing for those device types.

AssetSize / aspectHow manyNeeded for
Phone screenshots9:16 from 1080 × 1920, or 16:9 from 1920 × 1080Up to 8Publishing — min. 2 overall
Feature graphic1024 × 5001Every listing
7" tablet screenshots9:16 or 16:9, 1080–7680 pxUp to 8, 4 recommendedTablet listing
10" tablet screenshots9:16 or 16:9, 1080–7680 pxUp to 8, 4 recommendedTablet listing
Chromebook screenshots16:9 or 9:16, 1080–7680 pxUp to 8, 4 recommendedChromebook listing
Wear OS screenshots1:1, from 384 × 384 — no device frames1 or moreWear OS listing
Android TV screenshots16:9, plus a separate TV banner1 or moreAndroid TV listing
Android XR screenshots8:5, 3840 × 2400 recommended4 to 8Android XR listing
Android Automotive screenshots800 × 1280 portrait and 1024 × 768 landscape2 portrait + 2 landscapeAutomotive listing

From Google Play's listing asset requirements, checked August 2026. Play accepts a pixel range rather than fixed device sizes — the minimums are shown here.

Everything an Android listing needs

Including the two assets most screenshot tools leave you to make somewhere else.

Phone and tablet canvases that already fit

1080×1920 for phones and 1848×2960 for tablets, portrait and landscape — inside Play's pixel range and inside the 2× rule, so nothing bounces at upload.

The feature graphic as a first-class canvas

The 1024×500 banner lives in the same project as your screenshots, sharing fonts, colours and artwork. One design language from the top of the listing to the bottom of it.

Pixel 10 Pro, Galaxy S26 and Tab S8 Ultra frames

Photoreal Android shells in five finishes each, tiltable up to 15° per axis — and switchable off per screen, which is what Wear OS requires.

Per-language screenshots for every Play locale

36 languages with per-locale headlines and per-locale captures, right-to-left included, exported into one folder per language.

Captions shaped to stay inside the rules

Play caps taglines at 20% of the image and bans call-to-action copy. The templates lean on a short headline over a real screen — the shape that stays comfortably inside both.

Both stores out of one project

Android canvases and iOS canvases sit side by side with linked headlines, so a copy change lands on both. The export splits them into per-store folders.

From app screens to a Play Console upload

Including the tablet set and the banner, which is where most listings stall.

Grab your Android screens

Capture at 1080×1920 or better on a phone, and at tablet resolution if you plan to list for tablets. Play takes up to eight per device type.

Drop them into a kit

Pick a multi-screen kit, replace the headlines, seat the captures in Pixel or Galaxy frames, and set your palette.

Add the tablet sizes and the banner

Switch on the tablet canvases and the 1024×500 feature graphic. The layout stamps across and you adjust for the wider canvas.

Export for the Console

One ZIP, a folder per size and language, ready for the store listing page in the Play Console.

Google Play screenshot questions

Play's asset requirements change without much announcement. These were checked against Google's documentation in August 2026.

What size should Google Play screenshots be?

Play accepts a range rather than fixed sizes: every side between 320px and 3840px, with the long side no more than twice the short side. In practice, aim at 1080×1920 for 9:16 portrait and 1920×1080 for 16:9 landscape — Google recommends at least four phone screenshots at 1080px or better.

What is the Google Play feature graphic size?

1024×500, JPEG or 24-bit PNG with no transparency. Every listing needs one. It sits above your screenshot strip on the store page and stands in for your app wherever Play promotes it, so it works better as a banner with a short line of copy than as an enlarged app icon.

How many screenshots does Google Play require?

At least two, across different device types, before you can publish — then up to eight per device type. If you want the app to present properly on tablets, Google asks for at least four tablet screenshots demonstrating the in-app experience.

Can I put text on Google Play screenshots?

Yes, within limits. Taglines must not exceed 20% of the image area, the screenshot has to show the real in-app experience, and call-to-action language like "Download now" or "Best app ever" is not allowed. A short descriptive caption over an actual screen is the safe shape.

Do Google Play screenshots need device frames?

For phones, tablets and Chromebooks framing is optional and very common. For Wear OS it is explicitly forbidden — submit the 1:1 watch screenshot with nothing around it. Framing is a per-screen switch here for exactly that case.

Do I need separate screenshots for tablets?

Only if you want a tablet listing — but without them your app can be flagged as not optimised for large screens, which affects how it surfaces on those devices. The same design carries onto the tablet canvases here, so it is a toggle rather than a second project.

Why was my Play Store screenshot rejected?

The usual causes, in rough order: an alpha channel in the PNG, an aspect ratio outside the 2× rule, a tagline covering more than a fifth of the image, call-to-action text, or a screenshot that shows marketing artwork instead of the app itself. Exporting from a canvas that is already inside the spec removes the first two entirely.

Can I make Play Store and App Store screenshots together?

Yes — one project holds both. Android phone and tablet canvases, iPhone and iPad canvases and the feature graphic all sit side by side, with headlines linked so a copy change lands everywhere, and the export splits them per store. Apple's rules differ enough to be worth reading separately: see the App Store screenshot generator .

Build your Play Store listing

Phone, tablet and the 1024×500 feature graphic, from one design. Free to start.

Start free Browse templates

App Store and Play Store screenshots. Design once, every device, every store.

Product

Templates Pricing Start free Sign in About Contact

Resources

Guide Changelog AppShot vs Screenshots Pro AppShot vs Applaunchpad AppShot vs Appscreens Google Play Screenshot Generator App Store Screenshot Generator Device Mockups

Legal

Privacy Terms Refunds