Google Play wants every screenshot as a JPEG or 24-bit PNG with no alpha channel. Each side has to land between 320 and 3,840 px, and the long side can’t be more than twice the short one (Google Play Console Help, 2026).
Tablets and Chromebooks work from a bigger range, 1,080 to 7,680 px. Wear OS, Android TV, Android Automotive OS and Android XR each add a spec of their own on top.
The 2:1 limit is the one that trips people up. A 1,080 x 2,400 px screenshot from a 20:9 phone comes out at 2.22:1 and fails, so tall captures get cropped to 1,080 x 1,920 px before upload.
Google Play screenshot sizes by device type
Phones take 320 to 3,840 px per side. Tablets and Chromebooks need 1,080 to 7,680 px. The remaining form factors each follow a fixed spec.
As of November 2026, Play Console Help lists eight upload slots: phone, 7-inch tablet, 10-inch tablet, Chromebook, Android TV, Wear OS, Android Automotive OS and Android XR. Each slot takes up to 8 screenshots.
| Device type | Dimensions | Aspect ratio | Count |
|---|---|---|---|
| Phone | 320 to 3,840 px per side | 9:16 or 16:9 for featuring | 2 minimum overall, 8 maximum |
| Tablet and Chromebook | 1,080 to 7,680 px per side | 16:9 or 9:16 | 4 minimum, 8 maximum |
| Wear OS | 384 x 384 px minimum | 1:1 | 1 minimum, 8 maximum |
| Android TV | Not stated on Google’s page | Not stated | 1 minimum, 8 maximum |
| Android Automotive OS | 800 x 1,280 px portrait, 1,024 x 768 px landscape | Portrait and landscape | 2 of each, if provided |
| Android XR | 1,920 x 1,200 px minimum, 3,840 x 2,400 px recommended | 8:5 | 4 to 8 |
One minimum applies to every listing, and it’s 2 screenshots across device types. The rest depends on where the app ships.
Wear OS apps need at least 1 screenshot of the current watch app. Android TV apps need at least 1 TV screenshot and a TV banner at 1,280 x 720 px. Automotive OS is the odd one, since screenshots are required outside the parked app categories and optional inside them.
What file rules apply to every Google Play screenshot?
Google Play wants a JPEG or 24-bit PNG with no alpha channel, 320 to 3,840 px per side, and a long side that stays within twice the short side.
The floor is 320 px and the ceiling is 3,840 px. The longest ratio allowed between long and short side is 2:1. Publishing takes 2 screenshots, counted across device types, and each device type tops out at 8.
Play Console Help’s preview assets page is the source for all of these, checked in November 2026.
Why does the same help page cap screenshots at 3,840 px and 7,680 px?
Google’s general requirements put the maximum dimension at 3,840 px, yet the large-screen line on the same page allows 1,080 to 7,680 px. The page never reconciles the two.
The narrower reading is the safer one. A 3,840 x 2,160 or 2,160 x 3,840 export works under both, since it’s 16:9, fits the tablet range and stays under the general cap.
Is the file size limit 8 MB?
Google’s page only states 8 MB for Android XR screenshots, while AppRadar (updated July 24, 2026) states 8 MB per image for every device type.
Treat 8 MB as the ceiling for all slots. A file under it breaks neither reading.
How many screenshots does a listing need for featuring?
Publishing takes 2 screenshots across device types. Recommendation formats built on screenshots take more.
- Apps need at least 4 screenshots at 1,080 px minimum, shaped 16:9 or 9:16.
- Games get by with at least 3, but they must be all 16:9 landscape (1,920 x 1,080 minimum) or all 9:16 portrait (1,080 x 1,920 minimum).
Play Console Help files these under “Highly recommended”, yet it calls them a requirement for recommendation formats that use screenshots.
AppRadar adds that apps need one 16:9 landscape image of at least 1,920 x 1,080 px. Google’s page does not say a landscape image is mandatory, so a portrait-only set at 1,080 x 1,920 px follows the wording as published.
Two screenshots gets a listing published. Featuring an app takes 4, and so does each tablet or Chromebook slot.
What size should phone screenshots be?
Export phone screenshots at 1,080 x 1,920 px in portrait or 1,920 x 1,080 px in landscape. That pair is the 9:16 and 16:9 shape Google names for featuring, with 1,080 px as the floor.
Anything from 320 px up to the 2:1 limit uploads, but 1,080 px on the short side is where recommendation eligibility starts. Pick the orientation the app is actually used in.
Why do raw captures from tall phones fail the 2:1 limit?
A phone with a 20:9 display captures 1,080 x 2,400 px, and 2,400 divided by 1,080 is 2.22.
That breaks the 2:1 rule, and AppRadar (July 2026) reports that Play Console rejects out-of-range files at upload.
- 1,080 x 1,920 is 1.78:1, so it passes.
- 1,080 x 2,160 is 2.00:1, which passes right at the limit.
- 1,080 x 2,400 is 2.22:1 and fails.
- 1,080 x 2,424 is 2.24:1 and fails too. That’s the example CatDoes uses.
Phones with taller screens drift further past the limit, so the check belongs in the export step, not at upload.
How do you fix a capture that is too tall?
Strip the status and navigation bars first, then bring the frame to 9:16. Cropping 2,400 px down to 1,920 px removes 480 px, so cut chrome and empty space, never content.
Never stretch the image to hit the ratio. Google’s help page lists stretched or compressed images among the quality faults to avoid.
- Crop the top and bottom of the capture to 1,080 x 1,920.
- Or place the capture on a 1,080 x 1,920 canvas and fill the margin with a flat brand color.
Keep the interface at native scale either way.
Tablet and Chromebook screenshot sizes
Tablet and Chromebook screenshots take 1,080 to 7,680 px per side in 16:9 landscape or 9:16 portrait, with a minimum of 4 per slot and a maximum of 8.
The rule is stricter than the phone one because Google ties large-screen recommendations to these slots. Phone assets stretched onto a tablet listing do not substitute for them.
Which export sizes match Google’s 16:9 rule?
| Export size | Ratio | Matches 16:9? |
|---|---|---|
| 1,920 x 1,080 | 1.78:1 | Yes |
| 2,560 x 1,440 | 1.78:1 | Yes |
| 3,840 x 2,160 | 1.78:1 | Yes, and under the 3,840 px general cap |
| 1,920 x 1,200 | 1.60:1 (16:10) | No |
| 2,560 x 1,600 | 1.60:1 (16:10) | No |
Some vendor guides recommend 1,200 x 1,920 px for tablets (AppLaunchFlow, 2026), and others list 1,600 x 2,560 px for 10-inch models. Both are 16:10 shapes (1,920 x 1,200 and 2,560 x 1,600 in landscape), which depart from the 16:9 ratio Google states for large screens.
The help page does not say whether the console accepts 16:10 files in these slots. Exporting at 16:9 removes the question.
How do the large-screen slots differ?
The 7-inch tablet slot has its own upload section and takes up to 8 screenshots. The 10-inch slot is a separate section with the same range and the same cap.
Chromebook got a dedicated slot in October 2022, when Google announced Chromebook-specific uploads of up to 8 screenshots (Android Developers Blog). Before that, Chromebook users saw phone or tablet images.
Three slots at 8 each means a listing can carry up to 24 large-screen screenshots. AppRadar recommends landscape for the Chromebook set.
What goes wrong on large screens?
- Stretched phone captures look distorted, and Google lists stretched images as a quality fault.
- Text outside the core app experience can get cut off on Play homepages at some screen sizes, per Play Console Help.
- A slot with fewer than 4 screenshots falls short of the stated minimum.
- 16:10 exports depart from the stated ratio.
Capture the responsive layout on a tablet or a tablet emulator profile instead of scaling a phone image up.
Wear OS, Android TV, Android Automotive OS and Android XR requirements
Each of these form factors has one rule that catches people out. Wear OS bans frames and masking. Android TV leaves the screenshot pixel size unstated. Automotive OS demands generic emulator captures, and Android XR is the only slot at 8:5.
These slots only matter if the app ships to that form factor. Skip the rest.
Wear OS
Show the app interface only, with no watch frame, added text, graphics or backgrounds. Masking is out too, and transparent backgrounds fail, so a circular crop with transparent corners does not pass. If the app ships a tile, add a tile screenshot, and when a watch face is customizable, show more than one permutation.
Google’s Wear OS app quality page records the transparency and masking clarification on November 21, 2023. It also states that missing these requirements can lead to rejection of the app submission.
Android Studio (Hedgehog onward) adds a Play Store Compatible option to the Take Screenshot dialog for Wear OS emulators. Use it instead of cropping by hand.
Android TV
Google’s page requires at least 1 TV screenshot before publishing and gives no pixel size for it. AppRadar (July 2026) lists 16:9 at 1,920 x 1,080 px as the minimum.
Export TV screenshots at 1,920 x 1,080 px. It’s 16:9 and stays inside the general size limits, which also happens to satisfy the vendor figure.
Google shows TV screenshots only on Android TV devices, so each one should show the actual TV interface.
Android Automotive OS
Screenshots are required for apps outside the parked categories. Inside them they are optional, though Google recommends them when the car experience differs from mobile.
Use the generic system image only, with no vehicle-model or manufacturer UI. The landscape set comes from the Automotive (1024p landscape) profile and the portrait set from the Automotive Portrait profile. OEM images exist (General Motors, Honda, Mazda, Polestar, Renault Group, Volvo), but they are for testing, not for listing captures.
The emulator page, last updated November 2, 2026, pairs the 1024p landscape profile with API 28 to 32 images that include the Play Store. It pairs the portrait profile with API 33 and higher images without it.
That split means the two required sets can come from two different system images. Plan two emulator setups, not one.
Android XR
Android XR is the only screenshot slot that takes 8:5.
That ratio equals 16:10, which departs from the 16:9 Google states for tablets. Here it’s the requirement.
A size of 3,840 x 2,400 px is also the largest 8:5 canvas that stays inside the general 3,840 px cap, so the recommended resolution and the cap agree.
The XR line names plain PNG or JPEG and does not repeat the no-alpha rule from the general block. Keep XR files opaque and both statements hold.
How to capture, export and upload screenshots in Play Console
Capture on the target form factor first, resize second, upload last. Scaling a capture from the wrong device does not fix it.
- List the device slots the app ships to. Each one has its own section under Graphics.
- Capture on matching hardware or an emulator. In the Android Emulator, the Take Screenshot button opens a dialog to recapture, edit or copy the image, then saves a timestamped PNG.
- Switch to the right mode for special slots: Play Store Compatible for Wear OS, generic images and the two bundled profiles for Android Automotive OS.
- Clean the frame. Google asks for full battery, Wi-Fi and cell icons, no notifications, and correct rotation.
- Export each slot from one master design at its own size.
- Check that the ratio stays at or under 2:1 and that the file has no alpha channel.
- Upload under Grow users > Store presence > Main store listing, then scroll to the device section in Graphics.
One master frame in a design tool such as Figma covers every export. AppScreens describes its generator as exporting all required Play sizes from a single responsive design.
Assets show on every test track as soon as they are added to the listing, per Play Console Help. A bad export is visible to testers right away.
AppRadar flags a common miss on localized listings. A swap applied only to the default language leaves old creative running in other markets.
Where screenshots get rejected and where they only lose reach
Google splits its screenshot rules into Requirements and Highly recommended items. Missing a requirement can mean removal from Google Play, while missing a recommended item only limits promotion.
| Tier | Consequence | Typical items |
|---|---|---|
| Requirements (Play Console Help) | Removal or suspension possible | Alpha channel, out-of-range size, missing mandatory TV or Wear OS shot |
| Highly recommended (Play Console Help) | Listing unaffected, promotion limited | Fewer than 4 featuring-size shots, taglines, award claims |
| Wear OS quality checklist | Can lead to rejection of the submission | Device frames, extra text, transparent backgrounds, masking |
Do device frames and badges get screenshots rejected?
AppRadar (July 2026) says Google Play rejects device frames and promotional badges. Google’s page tells a different story. It files device imagery under Highly recommended for phone and tablet screenshots, along with store badges and ranking or award claims, and treats frames as a hard rule only on Wear OS.
Whether a reviewer enforces the softer items under broader policy is not stated on the page. Leave frames and badges out and the question never comes up.
Which misses cost reach without blocking the upload?
- Taglines covering more than 20% of the image
- Call-to-action text such as “Download now” or “Try now”
- Words like “Best”, “#1”, “Top”, “New”, “Discount” or “Sale”
- Copy tied to a date, which goes stale
- Fingers tapping the device, unless the app is used off-device
- Screens that no longer match the latest version of the app
None of these blocks publishing. Each one narrows where Google is willing to promote the listing.
Google Play Screenshot Sizes FAQ
What size is the Google Play feature graphic?
Go with 1,024 x 500 px, saved as a JPEG or 24-bit PNG with no alpha channel. It doubles as the cover image for a preview video.
Keep logos and key text away from the edges, because some formats crop them. The 1,280 x 720 px TV banner is a separate asset.
Which size and format does the Google Play app icon need?
Upload the icon as a 32-bit PNG with alpha at 512 x 512 px, up to 1,024 KB. That’s the opposite of screenshots and the feature graphic, which both reject alpha.
It’s a higher-resolution listing version and does not replace the launcher icon.
Where do screenshots appear on Google Play, and in what order?
Screenshots show on the store listing and in search, and on Play homepages too. On the listing, they sit after the preview video, then run left to right with the ones best suited to the viewer’s device first.
Google advises putting UI in the first three frames, even when a stylized set spreads one design across several images.
Do Google Play screenshots need to be localized?
Yes for added text. Taglines and overlays should be localized for each market, while in-game UI does not need translating, per Play Console Help.
Google lists this under recommendations, so a missing translation limits promotion rather than blocking the upload.
Do Google Play screenshots need alt text?
Alt text is recommended for every screenshot, not required. Keep each description to 140 characters or less.
Skip phrases like “image of”, since screen readers already announce that. Describe the screen instead, such as “The transaction complete screen.”
Master Canvas Sizes That Cover Every Device Slot
Eight slots do not mean eight separate sets of artwork. One 16:9 master covers five of them, Wear OS takes a square, Android XR takes an 8:5 canvas, and Android Automotive OS needs native emulator captures. That makes four sources in total.
The 16:9 master, exported at 1,080 x 1,920 px and 1,920 x 1,080 px, serves phones, 7-inch tablets, 10-inch tablets, Chromebooks and Android TV. It sits inside the general limits and clears the 1,080 px tablet floor, and it matches the vendor TV figure too.
Build the 16:9 master first, since it clears five slots. The Wear OS and Android XR canvases come next, and the Automotive OS emulator captures go last.
The master fixes the canvas, not the content. Each slot still needs captures from its own form factor, so reuse saves layout work and not capture time.
This position was verified against Play Console Help in November 2026. A new device slot, as Android XR was recently, would add another canvas.
- Go Cheat Sheet - November 9, 2026
- Build or White-Label Software? How Software Teams Decide What to Resell in 2026 - November 9, 2026
- Notepad++ Column Mode: Edit 100 Lines at the Same Time - November 7, 2026
