Google Play Screenshot Requirements 2026: Phone, Tablet & Feature Graphic

What Google Play actually requires to publish

Google Play is more flexible than the App Store on exact pixel pairs—but stricter on feature graphics, content policy, and large-format eligibility. Per Google’s Play Console Help (“Add preview assets to showcase your app”), you cannot publish without the right mix of screenshots and a feature graphic.

This guide covers 2026 phone and tablet screenshot rules, the mandatory 1024 × 500 feature graphic, highly recommended large-format sizes, and the content mistakes that block promotion placements.

Quick requirements table

Phone screenshots: dimensions that always work

Google does not force a single iPhone-style pixel pair. The hard rules are:

• Minimum side: 320 px
• Maximum side: 3840 px
• Aspect: the longest side must not be more than twice the shortest
• Format: JPEG or 24-bit PNG without transparency
• Count: 2–8 per device type (you need at least two screenshots somewhere on the listing to publish)

Default that satisfies publishing + large format: 1080 × 1920 (9:16 portrait). It sits comfortably inside every limit and qualifies for large-format recommendation surfaces when you upload at least four of them for apps (three for games at 9:16 or 16:9).

Avoid relying on ultra-tall 18:9 or 19.5:9 captures alone if you care about large-format placements—Google’s highly recommended guideline specifically calls for 9:16 or 16:9 at those minimum resolutions.

Content guidelines that affect ranking surfaces

Google’s “highly recommended” rules determine whether screenshots can appear in large promotional formats:

• Show real in-app UI in the first three screenshots when possible.
• Taglines should stay under roughly 20% of the image area.
• No ranking claims (“#1”, “Best”), price/promo language (“Free”, “Sale”), or CTAs (“Download now”).
• No fingers tapping devices unless off-device interaction is the product.
• Clean the status bar: no carrier names or notifications; battery/Wi‑Fi/cellular full.
• Avoid device frames / device imagery in creatives meant for Play promotion—Google explicitly discourages device imagery that ages poorly or alienates users.
• Localize overlay text; in-app UI localization is separate.
• Add alt text (≤140 characters) for accessibility and assistive-tech surfaces.

Stylized multi-panel screenshots are allowed, but prioritize recognizable UI early in the carousel.

Tablet and Chromebook screenshots

Under Large screens in Play Console Graphics:

• Provide a minimum of 4 screenshots that show the large-screen experience.
• Resolution between 1080 and 7680 px on a side.
• Use 16:9 landscape or 9:16 portrait.
• Keep extra marketing text out of the crop-risk zones—Play homepages can crop large-screen shots.

Practical picks: 1440 × 2560 portrait or 2560 × 1440 landscape for crisp tablets. Show split-screen, keyboard, or expanded navigation when those are real differentiators—not a stretched phone UI.

Feature graphic: 1024 × 500 done right

The feature graphic is mandatory and appears as:

• Cover image for your preview video (non-XR cases)
• Large-format collections and ads placements for apps
• Game recommendation groupings alongside video/screenshots

Hard specs: exactly 1024 × 500, JPEG or 24-bit PNG, no transparency.

Design rules that matter:

1. Keep logo, title, and primary UI in the center safe zone—edge “cutoff zones” are cropped in some Play formats.
2. Do not duplicate your app icon branding so heavily that icon + feature graphic look redundant side by side.
3. Avoid pure white, black, or dark gray full backgrounds that blend into Play chrome.
4. Skip store badges, device photos, trademarked third-party characters, and time-sensitive holiday art unless you plan rapid swaps.
5. No performance/ranking/promo claims in the art or text.
6. Localize text for major markets.
7. Write alt text for the graphic.

The most common technical rejection: exporting a PNG with alpha. Flatten before upload.

Preview video (optional but high leverage)

Add one YouTube URL—not a playlist. Requirements that trip people up:

• Public or unlisted (not private)
• Ads / monetization off
• Embeddable, not age-restricted
• No extra URL parameters (timestamps, etc.)

Google recommends showing real gameplay/UI in the first 10 seconds, keeping ≥80% of the runtime representative of the product, and designing for muted autoplay (captions/on-screen copy). Only the first ~30 seconds may autoplay inline.

Wear OS, TV, Automotive, XR (if you ship them)

If you distribute to additional form factors, Play adds stricter rules—for example:

• Wear OS: ≥1 accurate Wear screenshot, 1:1, min 384 × 384, no device frames, no extra graphics/text outside the UI, no transparency/masking.
• Android TV: ≥1 TV screenshot plus a 1280 × 720 banner.
• Automotive: category-dependent; when required, provide generic system UI shots (not OEM-specific), typically including portrait and landscape pairs at specified sizes.
• Android XR: 4–8 screenshots at 8:5 aspect (recommended 3840 × 2400).

Skip these sections if you do not target those devices—but do not leave Wear/TV blank if those tracks are enabled.

Indie export checklist

1. Export 8 phone screenshots at 1080 × 1920 (or 1920 × 1080 for landscape-first apps).
2. Ensure the first three teach value → core loop → proof (ratings UI, sample result, social feature).
3. Design a 1024 × 500 feature graphic with center-weighted branding.
4. Flatten all PNGs (except the 512 icon, which needs alpha).
5. Add four large-screen shots if tablets matter to your audience.
6. Paste a clean YouTube preview URL with ads disabled.
7. Fill alt text for every graphic.
8. Re-read Play’s metadata policy before seasonal campaigns—promo language in graphics is a frequent policy miss.

Phone vs Play vs App Store: don’t mix pipelines

Treat Play and App Store as two export presets, not one stretched canvas.

Bottom line

To ship on Google Play in 2026: upload at least two compliant screenshots, a perfect 1024 × 500 feature graphic, and a 512 icon. To compete for large-format placements, add four sharp 9:16 (or 16:9) phone screenshots that show real UI, keep copy sparse, and keep the feature graphic’s focal point centered. Nail the specs once, then iterate on messaging—not on rejected uploads.