Google Play Store Listing Graphics: Every Size, Format, and Rule (2026)

Google Play asks for fewer graphics than the App Store, but its rules are stricter in odd places. The listing icon is exactly 512 × 512 as a 32-bit PNG under 1024 KB. The feature graphic is exactly 1024 × 500 and must have no alpha channel. Phone screenshots can be anywhere from 320 to 3840 px per side, but the long side can’t be more than twice the short side, which rules out a raw screenshot from most modern phones. This post covers every asset in one table, then the details that cause upload errors or quietly cost you featuring.

Everything here comes from Google’s preview assets help page, the store listing page, the metadata policy, and the Play icon design specifications, checked on October 21, 2026. If you’re shipping on iOS too, the Apple side lives in our App Store header and search image guide and the app icon sizes guide.

The full asset table

Asset	Size	Format	Count	Required?
App icon	512 × 512 px	32-bit PNG (with alpha), sRGB, max 1024 KB	1	Yes
Feature graphic	1024 × 500 px	JPEG or 24-bit PNG, no alpha	1	Yes
Phone screenshots	320–3840 px per side, long side ≤ 2× short side	JPEG or 24-bit PNG, no alpha	Up to 8	At least 2 across device types
Tablet screenshots (7” and 10”)	1,080–7,680 px, 16:9 or 9:16	JPEG or 24-bit PNG, no alpha	Min 4 recommended, up to 8	Optional
Chromebook screenshots	Same as tablets	Same	Min 4 recommended, up to 8	Optional
Android XR screenshots	8:5, 1920 × 1200 min, 3840 × 2400 recommended	PNG or JPEG, max 8 MB each	4–8	XR apps only
Wear OS screenshots	1:1, at least 384 × 384	No transparency, no device frames	At least 1	Wear apps only
Android TV banner	1280 × 720 px	JPEG or 24-bit PNG, no alpha	1	TV apps only (plus at least 1 TV screenshot)
Android Automotive	800 × 1280 portrait, 1024 × 768 landscape	Not stated	At least 2 of each if you provide any	Required outside parked categories
Preview video	Landscape or portrait	One YouTube URL	1	Optional
App name	30 characters	Text	Per language	Yes
Short description	80 characters	Text	Per language	Yes
Full description	4000 characters	Text	Per language	Yes

Missing on purpose: file-size caps for the feature graphic and phone screenshots. Many guides say “15 MB” and “8 MB,” but Google’s asset page only lists caps for the icon (1024 KB) and XR screenshots (8 MB). A 1024 × 500 JPEG is far smaller than either, so this rarely matters. If an upload is refused for size, use an image compressor.

The app icon: 512 × 512, and not your launcher icon

The Play listing icon is a separate file from the icon inside your app. Google says it “does not replace your app’s launcher icon.” It appears on your store listing, in search results, and in top charts.

The spec from the icon design page:

512 × 512 px, 32-bit PNG, sRGB, max 1024 KB.
Full square. Don’t round the corners yourself. Google Play masks the icon dynamically with a corner radius equal to 30% of the icon size.
No drop shadow. Play adds one after upload. Shadows and lighting inside the artwork are fine.
Fill the canvas with artwork when you can, and use Google’s keyline grid as a guide for logos rather than stretching them edge to edge.
No badges or text that suggest ranking, price, or a Play category. The metadata policy also bans emojis and misleading symbols, such as a download arrow on an app that has nothing to do with downloading.

The launcher icon in your APK or AAB is a different thing entirely: an adaptive icon made of foreground, background, and monochrome layers on a 108dp canvas, plus legacy PNGs for each density. The app icon sizes guide covers that side.

The App Icon Generator produces both from one square image. Its Android output includes play-store-512.png (the Play Console listing icon, written as a full square for Play to mask) alongside the res/ folder: ic_launcher.xml and ic_launcher_round.xml for API 26+, and legacy, round, foreground, background, and monochrome PNGs for mdpi through xxxhdpi. Upload the 512 file to Play Console; the res/ folder goes in your project.

The feature graphic: 1024 × 500, no alpha

The feature graphic is the one asset with no flexibility. It must be exactly 1024 × 500 px, saved as JPEG or 24-bit PNG with no alpha channel.

The alpha rule catches a lot of people. Most design tools and browsers save PNGs as 32-bit RGBA even when every pixel is opaque, and that file is not 24-bit. If Play Console rejects a PNG that looks fine, export it as JPEG or as a true RGB PNG.

Where Google uses it: as the cover image for your preview video, in collections of apps (including ad placements), and in recommended game groups. When a preview video is attached, Google says users tap “the play button that overlays on your feature graphic.” It doesn’t say where or how big, but assume roughly the center, so anything you place dead center can end up under that button.

Google’s design guidance, in short:

Keep important content near the center and off the edges. Logos, the app name, slogans, and key UI belong away from the cutoff zones, because “some formats may use additional UI overlays.” Put background elements at the edges.
Skip fine detail. It “will not be visible on many phone screens.”
Use vibrant color. Pure white, black, or dark gray blends into the Play Store background.
Extend your icon’s branding rather than copying the icon.
Avoid device imagery, third-party trademarks, and store badges.
Add alt text of 140 characters or less, and don’t start it with “photo of” or “image of.”

There’s a tension between “keep things centered” and “the play button covers the center.” If you plan to add a video, a side layout works better: headline on one side, artwork on the other, nothing critical in the middle.

Our Google Play Feature Graphic Generator is built for exactly this. It always exports at 1024 × 500 as JPEG or a true no-alpha PNG, draws an adjustable safe-area guide, and has a “my listing has a promo video” toggle that shows an approximate play button and keeps text out of that zone in the side layouts. Google doesn’t publish the button’s size or a margin number, so treat those overlays as estimates. A pre-flight panel also flags headline wording that runs into the metadata policy, like “#1” or “10% off.”

Phone screenshots: 2 to 8, and watch the 2:1 rule

The base rules:

At least 2 screenshots across your device types to publish, and up to 8 per device type.
JPEG or 24-bit PNG, no alpha.
Each side between 320 and 3840 px.
The long side can’t be more than twice the short side.

That last rule is where things break. Plenty of current Android phones have 20:9 displays (1080 × 2400 is common), so a raw screenshot is about 2.22:1 and too tall. Modern iPhone screenshots fail the same way: 1320 × 2868 and 1290 × 2796 both work out to about 2.17:1. Reusing your App Store set as-is won’t work. Crop or redesign to 9:16. Our guide to Google Play’s 2:1 screenshot rule walks through the fixes, and the App Store screenshot sizes guide covers the iOS side if you’re building both sets.

Meeting the minimum gets you published. Being eligible for promotion takes more. Google’s large-format placements need:

Apps: at least 4 screenshots at 1080 px or more, either 1080 × 1920 portrait (9:16) or 1920 × 1080 landscape (16:9).
Games: at least 3 landscape 16:9 (1920 × 1080 min) or 3 portrait 9:16 (1080 × 1920 min) screenshots showing actual gameplay.

Missing these “will not impact your store listing page,” per Google, but it can limit where Play shows your app. Since it costs nothing extra, plan on four 1080 × 1920 screenshots from the start.

Content guidance: show the real app, put the key UI in the first three screenshots, keep taglines to no more than 20% of the image, clean the status bar (no carrier or notifications; battery, Wi-Fi, and signal full), and don’t show fingers or device imagery.

Our Google Play Screenshot Generator is built around these rules. It starts you on a 1080 × 1920 canvas, fits tall phone captures (1080 × 2400 and the like) inside it instead of stretching or cropping them, defaults to no device frame since Google asks you to avoid device imagery, and flags sets that miss the featuring rule or the 2:1 limit.

Tablets and Chromebooks

The page lists device types as phones, tablets (7-inch and 10-inch), Chromebooks, and others, but gives one shared rule set for large screens rather than separate 7” and 10” numbers:

At least 4 screenshots.
1,080 to 7,680 px.
16:9 landscape or 9:16 portrait.
No text that isn’t part of the core app experience, because it “can get cut off on Play homepages on certain screen sizes.”

They’re optional for publishing, but without them your app has nothing tablet-shaped to show on large screens. A 1920 × 1080 or 2560 × 1440 landscape capture covers both tablets and Chromebooks.

Android XR, Wear OS, TV, and cars

These follow the table above. Two details worth knowing: Android XR can also take an optional spatial video (360°, 180°, or 3D) that shows only on headsets, and Wear OS screenshots must show the interface alone, with no device frames, masking, or transparent backgrounds.

The preview video: YouTube rules

Play doesn’t host video files. You paste one YouTube URL, and it has to meet all of these:

A single video URL, not a playlist or channel, with no extra parameters like timecodes.
Public or unlisted, not private.
Ads off. Turn off monetization, or use a different upload if a copyright claim monetizes it.
Not age-restricted and embeddable.

It autoplays muted, inline, for up to the first 30 seconds, depending on device and network, and plays before your screenshots. Google asks you to show the real experience within the first 10 seconds, keep at least 80% of the video on actual app footage, and not leave black bars beside a portrait video. On-screen copy for muted viewers should avoid calls to action and promotional wording.

Text limits and metadata policy traps

The character limits are 30 for the app name, 80 for the short description, and 4000 for the full description. Full-width and half-width characters count the same.

The metadata policy is where listings get rejected. The rules that catch people most:

Don’t	Applies to
Emojis, emoticons, or repeated special characters	Title, icon, developer name, and images
ALL CAPS, unless it’s part of your brand	Title, developer name
Ranking or performance claims (“#1”, “App of the year”, “Popular”, award icons)	Title, icon, developer name, and images
Price or promotions (“10% off”, “free for limited time only”)	Title, icon, developer name, and images
Google Play program references (“Editor’s choice”, “New”)	Title, icon, developer name, and images
Unattributed or anonymous user testimonials	Description
Repetitive or unrelated keywords, claims like “best game ever”	Description
Celebrity names or brand logos without permission	Everything

Note that “New” counts as a Play program reference, so “New!” in a title or feature graphic is a problem. And screenshots and videos must “reflect your app’s actual experience.”

Custom store listings

Play Console lets you create up to 50 custom store listings, each with its own name, icon, descriptions, and graphics, targeted by country, search keywords, ad traffic, pre-registration, user segments like churned users, or a unique listing URL parameter. Each country can belong to only one custom listing, and they aren’t translated automatically.

Putting it together

The minimum set for a phone app is one 512 icon, one 1024 × 500 feature graphic, two screenshots, and the three text fields. The set worth shipping is four 1080 × 1920 screenshots and four tablet screenshots on top of that. Make the feature graphic, export the icon set, and then work through the rest of the release (closed testing, Data safety, content rating) with the Google Play publishing checklist. Before the upload itself, check the target API 36 and 16 KB page size rules, since either one can block a release.