Quick answer
Android TV needs at least one screenshot and a banner image. Android Automotive needs two portrait at 800 by 1,280 and two landscape at 1,024 by 768, taken on a generic system image. Android XR needs four to eight screenshots at an 8:5 ratio, up to 8 MB each.
The short answer
> Quick answer: Every device type gets its own screenshot section, its own count and its own sizes. TV, car and XR each have rules that phone screenshots do not.
Most developers never open these sections, which is fine until you ship on one of those surfaces. Then a missing asset blocks the release. I read Google's current requirements before writing this, because the XR section is new enough that older checklists don't mention it at all.
Most developers never open these sections, which is fine until you ship on one of those surfaces. Then a missing asset blocks the release. I read Google's current requirements before writing this, because the XR section is new enough that older checklists don't mention it at all.
Play has seven device types, not one
The Graphics section is not a single list. It splits by hardware.
Google supports phones, tablets at 7 and 10 inches, Chromebooks, Android TVs, Wear OS watches, Android Automotive OS cars and Android XR headsets.
You can add up to eight screenshots for each of those types. So a listing can carry a lot of images, and each group is only shown to people browsing on that kind of device. Each section sits under Graphics in Play Console, and an empty one is easy to miss until a release is blocked.
Google supports phones, tablets at 7 and 10 inches, Chromebooks, Android TVs, Wear OS watches, Android Automotive OS cars and Android XR headsets.
You can add up to eight screenshots for each of those types. So a listing can carry a lot of images, and each group is only shown to people browsing on that kind of device. Each section sits under Graphics in Play Console, and an empty one is easy to miss until a release is blocked.
Android TV needs a screenshot and a banner
If you distribute to Android TV, you need at least one Android TV screenshot before you can publish the app.
A separate Android TV banner image is also required.
So TV is two assets, not one. Both block the release. Plan them alongside the build, because discovering the requirement on release day is how a Friday deploy turns into a Monday deploy.
A separate Android TV banner image is also required.
So TV is two assets, not one. Both block the release. Plan them alongside the build, because discovering the requirement on release day is how a Friday deploy turns into a Monday deploy.
TV screenshots only appear on TVs
Here's a detail that changes what you put in them. TV screenshots are only displayed on Android TV devices.
Nobody browsing on a phone will ever see them. Not once.
That means you don't have to make them work as small thumbnails in a phone listing. Design them for a screen across the room instead. Big elements, high contrast, and no fine detail that dies at viewing distance. Google's own TV layout guidance is worth a read before you decide what to capture.
Nobody browsing on a phone will ever see them. Not once.
That means you don't have to make them work as small thumbnails in a phone listing. Design them for a screen across the room instead. Big elements, high contrast, and no fine detail that dies at viewing distance. Google's own TV layout guidance is worth a read before you decide what to capture.
Large screens want four, not one
Chromebooks and tablets share a section, and Google asks for a minimum of four screenshots to demonstrate the in app experience.
One stretched phone screenshot won't do.
A tablet layout that is genuinely different is the whole point of the section. Our post on tablet and foldable screenshots covers how to build them without redoing every image by hand. Four images also give you room to show a layout that uses the extra width rather than repeating the phone view.
One stretched phone screenshot won't do.
A tablet layout that is genuinely different is the whole point of the section. Our post on tablet and foldable screenshots covers how to build them without redoing every image by hand. Four images also give you room to show a layout that uses the extra width rather than repeating the phone view.
The large screen pixel range
Google asks for large screen screenshots between 1,080 and 7,680 pixels, at 16:9 for landscape or 9:16 for portrait.
That upper number is worth noting. The general screenshot requirement lists 3,840 pixels as the maximum dimension.
The two figures differ, so stay inside the device specific range and confirm the uploader accepts the file before you build the whole set. Exporting eight images at a size Play refuses is an avoidable afternoon.
That upper number is worth noting. The general screenshot requirement lists 3,840 pixels as the maximum dimension.
The two figures differ, so stay inside the device specific range and confirm the uploader accepts the file before you build the whole set. Exporting eight images at a size Play refuses is an avoidable afternoon.
Keep text off the large screen images
This rule is easy to miss and it costs you real estate. Google says to exclude additional text that is not part of your core app experience.
The reason is practical. That text can get cut off on Play homepages at certain screen sizes.
So the caption habit from phone listings works against you here. Let the interface carry the message, and keep any promotional wording inside the descriptions where it can't be cropped.
The reason is practical. That text can get cut off on Play homepages at certain screen sizes.
So the caption habit from phone listings works against you here. Let the interface carry the message, and keep any promotional wording inside the descriptions where it can't be cropped.
Android Automotive depends on your category
Cars are the one place where the requirement itself varies. Screenshots are required for apps that are not in a parked app category.
In a parked category they're optional.
Google still recommends them if your app has car specific functionality, or if the car experience differs significantly from mobile and tablet. That second condition covers most apps that bothered building for a car at all. Google's car documentation sets out the categories.
In a parked category they're optional.
Google still recommends them if your app has car specific functionality, or if the car experience differs significantly from mobile and tablet. That second condition covers most apps that bothered building for a car at all. Google's car documentation sets out the categories.
Generic system UI only
This is the strictest content rule in the whole set. Car screenshots must depict the generic system interface.
No individual vehicle model. No manufacturer branding.
So no photographs of your app running in a particular car, and no branded dashboard around it. Google tells you to take the screenshots using a generic system image, which removes the temptation entirely. The images also have to accurately depict how the app really looks.
No individual vehicle model. No manufacturer branding.
So no photographs of your app running in a particular car, and no branded dashboard around it. Google tells you to take the screenshots using a generic system image, which removes the temptation entirely. The images also have to accurately depict how the app really looks.
Use the emulator profiles Google names
You don't have to guess the car resolutions. Google names the hardware profiles to use.
The Android Automotive OS emulator ships with an Automotive 1024p landscape profile and an Automotive Portrait profile.
Capture from those two and you land on the required resolutions without measuring anything. I compared that route against cropping a desktop capture, and the emulator route was both faster and the only one that produced honest images. Save the emulator configuration once, then reuse it for every release rather than rebuilding it each time.
The Android Automotive OS emulator ships with an Automotive 1024p landscape profile and an Automotive Portrait profile.
Capture from those two and you land on the required resolutions without measuring anything. I compared that route against cropping a desktop capture, and the emulator route was both faster and the only one that produced honest images. Save the emulator configuration once, then reuse it for every release rather than rebuilding it each time.
Car screenshot counts and sizes
If you provide Android Automotive screenshots at all, you have to provide a minimum spread.
At least two portrait images at 800 by 1,280 pixels. At least two landscape images at 1,024 by 768 pixels.
Four images total as the floor, split evenly between the two orientations. That is the minimum. That pairing exists because cars mount screens both ways, and a listing that only covers one orientation looks broken to half the audience.
At least two portrait images at 800 by 1,280 pixels. At least two landscape images at 1,024 by 768 pixels.
Four images total as the floor, split evenly between the two orientations. That is the minimum. That pairing exists because cars mount screens both ways, and a listing that only covers one orientation looks broken to half the audience.
Android XR asks for four to eight
The XR section has the tightest count. You must upload between four and eight screenshots to showcase the app.
Not one. Not two. Four is the floor, and Google will not let you publish an XR listing with fewer than that however good the four are.
That makes sense for a headset, where a single image tells you almost nothing about how something feels to use. Google's XR documentation is the place to start if you're building for it.
Not one. Not two. Four is the floor, and Google will not let you publish an XR listing with fewer than that however good the four are.
That makes sense for a headset, where a single image tells you almost nothing about how something feels to use. Google's XR documentation is the place to start if you're building for it.
XR sizes and the file limit
XR screenshots must be PNG or JPEG, up to 8 MB each, at an 8:5 aspect ratio.
Aim for 3840 by 2400. The floor is 1920 by 1200.
That 8 MB ceiling is generous, but a 3840 pixel PNG can pass it if the scene is detailed. Export as JPEG at high quality when a screenshot is photographic, and keep PNG for interfaces with flat color and sharp edges. Check the exported files in a viewer, because some tools keep an alpha channel even when the image looks flat.
Aim for 3840 by 2400. The floor is 1920 by 1200.
That 8 MB ceiling is generous, but a 3840 pixel PNG can pass it if the scene is detailed. Export as JPEG at high quality when a screenshot is photographic, and keep PNG for interfaces with flat color and sharp edges. Check the exported files in a viewer, because some tools keep an alpha channel even when the image looks flat.
The general rules still apply
Underneath all the device sections, the base requirements do not go away.
Two screenshots minimum, across different device types, before you can publish at all. JPEG or 24 bit PNG with no alpha. Minimum dimension 320 pixels, maximum 3,840.
And one people forget. The longest side can't be more than twice the shortest, which quietly rules out very wide panoramas whatever section you upload them into.
Two screenshots minimum, across different device types, before you can publish at all. JPEG or 24 bit PNG with no alpha. Minimum dimension 320 pixels, maximum 3,840.
And one people forget. The longest side can't be more than twice the shortest, which quietly rules out very wide panoramas whatever section you upload them into.
Where these images actually show up
Screenshots aren't only on your listing page. Play may display them in search and on the homepage too.
On your listing, if you have a preview video, the video comes first and the screenshots follow it.
After that they run left to right, ordered by which ones suit the device the person is browsing on. So the first image in each device set is doing more work than the rest, exactly as it does on phones.
On your listing, if you have a preview video, the video comes first and the screenshots follow it.
After that they run left to right, ordered by which ones suit the device the person is browsing on. So the first image in each device set is doing more work than the rest, exactly as it does on phones.
The check before you upload
TV has at least one screenshot and a banner. Large screens have at least four, inside the stated pixel range, with no added text.
Car images come from a generic system image, two portrait and two landscape, at the sizes Google names.
XR has four to eight at 8:5, under 8 MB each. Everything exports flat with no alpha. Then build the phone and tablet sets in the mockup editor, where the usual frames and captions are still allowed. Our phone size guide covers that half.
Car images come from a generic system image, two portrait and two landscape, at the sizes Google names.
XR has four to eight at 8:5, under 8 MB each. Everything exports flat with no alpha. Then build the phone and tablet sets in the mockup editor, where the usual frames and captions are still allowed. Our phone size guide covers that half.
Frequently asked questions
Do I need Android TV screenshots to publish?
If you distribute the app to Android TV devices, yes. You need at least one Android TV screenshot and an Android TV banner image before the app can be published. Both are blockers rather than optional extras. Those TV images are only shown to people browsing on an Android TV, so design them for a screen viewed from across the room.
What size are Android Automotive screenshots?
If you provide them, you need at least two portrait images at 800 by 1,280 pixels and at least two landscape images at 1,024 by 768 pixels. The Automotive emulator's 1024p landscape and portrait hardware profiles produce those sizes directly.
How many Android XR screenshots does Play require?
Between four and eight. They must be PNG or JPEG at an 8:5 aspect ratio, up to 8 MB each. Google recommends 3840 by 2400 pixels and sets the minimum at 1920 by 1200.
Can I reuse phone screenshots for TV or car listings?
No, and it would look wrong even if the uploader allowed it. Each device type has its own aspect ratios and content rules, and car screenshots have to come from a generic system image rather than a real vehicle. Build each device set from a capture taken on that device type, then keep the folders separate so nothing gets uploaded twice.
Can I add captions to large screen screenshots?
Google asks you to exclude text that is not part of your core app experience, because it can get cut off on Play homepages at some screen sizes. Save the captions and [device frames](/frames) for your phone listing instead.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.