Table of contents
- Quick nav
Wear OS, Android TV & Chromebook Screenshots on Google Play: Form Factor Requirements Explained
Your phone screenshots aren't enough anymore
Google Play shows different listing assets depending on the device a person is browsing from. Someone looking at your app on a Chromebook, a TV, or from the Play Store on their watch should see screenshots that match that device. If you ship on those form factors but only provide phone screenshots, your listing can look broken there, and in some cases the app may be less visible or not approved for that surface.
This guide covers the three form factors teams most often forget: Wear OS, Android TV (Google TV), and Chromebook. Exact limits change from time to time, so treat the numbers here as a starting point and confirm them in the Play Console help center ("Add preview assets to showcase your app") before exporting.
Step zero: opt in to the form factor
Screenshots for these devices don't do much on their own. In Play Console, form factors are typically managed in Advanced settings → Form factors (or a similar section, depending on the console version). The usual flow is:
- Make sure your release actually supports the device (manifest features, a Wear OS module, TV launcher intent, large-screen layouts).
- Opt in to the form factor in Play Console.
- Add the form-factor-specific screenshots and assets in your store listing.
- Pass any form-factor quality review Google applies.
Wear OS and Android TV apps are commonly reviewed against their own quality guidelines. If the screenshots are missing or don't follow the rules, that can be one reason an app isn't approved for that form factor.
Quick reference table
| Form factor | Shape | Key requirements (verify in Play Console) | Extra assets |
|---|---|---|---|
| Wear OS | Square (1:1) | UI only; no device frames, masks, or extra text; minimum size around 384×384 px | — |
| Android TV | Landscape 16:9 | TV UI screenshots; 1920×1080 is a safe target | TV banner, 1280×720 |
| Chromebook | 16:9 or 9:16 | Large-screen screenshots; each side within the allowed range (commonly 1080–7680 px) | — |
| All | — | JPEG or 24-bit PNG, no alpha | — |
Wear OS screenshots
Wear OS has the strictest creative rules of the three, because the Play Store on a watch shows screenshots in a round or square viewport and Google wants them to represent the actual watch experience.
What to do:
- Use square screenshots at 1:1. Capture them from a Wear OS emulator or device so the resolution is native.
- Show only the app's UI. Google's guidance asks for screenshots that show the interface as it appears on the watch.
- Keep backgrounds as the app renders them. Most Wear OS UIs are dark, which is expected.
- Cover the main surfaces: your main screen, a tile, and a complication if you offer them. Users often decide based on whether your tile looks useful.
What to avoid:
- Device frames or watch mockups. Leave the hardware out.
- Circular masks or transparent corners. Submit a square image; let the store handle presentation.
- Marketing captions, badges, or overlays on top of the UI.
- Phone screenshots in the watch slot.
This means you can't reuse your phone design system for watch screenshots. Your "marketing" here is choosing the right screens and filling them with realistic, readable data: a heart rate that looks plausible, a workout in progress, a weather tile with a real city name.
Capturing Wear OS screenshots
The Android Studio emulator includes Wear OS system images for round and square devices. Capture from a square device profile, or take the screenshot from a round one and confirm the exported file is the full square the store expects. Check the final file size and shape before uploading.
Android TV screenshots
TV listings are viewed from across a room, so readability matters more than detail.
Requirements to plan for:
- Landscape 16:9 screenshots of the TV UI. Exporting at 1920×1080 keeps you in a safe range.
- A TV banner (1280×720), which is the image used in the TV launcher and in parts of the TV Play Store. Without it, your app can look out of place on the TV home screen. The banner should include your app name or logo and remain readable at small sizes.
- Real TV UI. Don't place phone screenshots on a TV-shaped background. If your TV app uses a leanback-style or Compose for TV layout, show that.
Design tips for TV:
| Tip | Why |
|---|---|
| Show focus states | TV navigation is D-pad based; a highlighted card signals "this works with a remote" |
| Use large, readable titles | Viewers sit far from the screen |
| Fill content rows with plausible content | Empty rows look like a broken app |
| Avoid licensed artwork you don't own | Movie posters and channel logos can create policy issues |
If your app is a media app, the last point is important. Use original or properly licensed artwork, or neutral placeholders, rather than famous film posters.
Chromebook screenshots
Chromebooks are large-screen, keyboard-and-trackpad devices, and Play can show dedicated screenshots for them.
Requirements to plan for:
- 16:9 landscape or 9:16 portrait, with each side inside the allowed pixel range. Landscape is the natural choice for most apps on a laptop.
- Several screenshots. Google has recommended providing multiple Chromebook screenshots (commonly at least four) to qualify for better visibility on large-screen surfaces.
- Large-screen layouts. Show your app taking advantage of the space: multi-pane views, side panels, resizable windows.
Common mistakes:
- A phone layout stretched across a laptop screen with huge empty margins.
- Touch-only UI hints ("swipe here") when the device is used with a trackpad.
- Screenshots that show Android phone status bars inside a laptop window.
If your app supports keyboard shortcuts or mouse hover states, a Chromebook screenshot is a good place to show them.
How these relate to tablet screenshots
Chromebook and tablet screenshots are separate slots, though both live in the large-screen world. Tablet screenshots (7-inch and 10-inch) are shown on Android tablets, while Chromebook screenshots are for ChromeOS devices. You can often use the same large-screen layout for both, but export each to its own required aspect ratio and size, and check that the content suits how the device is used.
A production workflow that scales
- List your form factors and the assets each requires.
- Capture natively on emulators for each device type, using clean demo data.
- Keep Wear OS raw: no frames, no text, square export.
- Design TV and Chromebook with the same brand colors as your phone set, but in their own layouts.
- Create the TV banner once, test it at small sizes.
- Verify every file: dimensions, aspect ratio, no alpha, JPEG or 24-bit PNG.
- Localize where it matters. Text in TV and Chromebook screenshots should match the listing language.
For phone and tablet sets where frames and captions are appropriate, a mockup tool such as appshotmaker.com can speed things up. Just don't run Wear OS screenshots through the same framing pipeline.
Pre-upload checklist
- Form factor opted in and the release actually supports it
- Wear OS: square, UI-only, no frames, masks, or captions
- Android TV: 16:9 screenshots of real TV UI, plus a 1280×720 banner
- Chromebook: 16:9 or 9:16, within size range, several screenshots
- All files JPEG or 24-bit PNG, no transparency
- No licensed third-party artwork you don't have rights to
- Localized listings updated with matching screenshots
Summary
Google Play treats Wear OS, Android TV, and Chromebook as distinct surfaces with their own screenshot rules. Opt in to each form factor, capture native screenshots, keep Wear OS images raw and square, give TV a proper banner and readable 16:9 shots, and show Chromebook users a real large-screen layout. Doing this once makes your app look intentional on every device it supports.