Guide · 7 min read
Play Store Feature Graphic: The 1024×500 You Keep Getting Wrong
The Play Store feature graphic is mandatory for publishing, appears above your screenshots in every listing, and doubles as an editorial thumbnail when Google promotes your app. Most indie developers either ship a cropped portrait screenshot at the wrong proportions or treat it as a last-minute checkbox before hitting Publish. Both choices cost real impressions. Here is what the 1024×500 canvas actually demands — and the specific design and policy mistakes that make it invisible before a user ever sees your screenshots.
Play Store feature graphic size: exactly 1024×500 pixels
The Play Store feature graphic is 1024 pixels wide by 500 pixels tall. That is not a suggestion — Google Play Console blocks publishing until you upload an asset at exactly those dimensions. Submitting at any other size, even 1024×501 or a cleanly scaled 2048×1000, will fail the upload or silently reject at submission. File format must be PNG or JPEG, 24-bit color, no alpha channel, maximum 15 MB. A well-compressed JPEG at these dimensions comes in under 300 KB with no visible quality loss at Play Store rendering sizes.
The aspect ratio is 2.048:1, close to cinematic widescreen. This is fundamentally different from the 9:16 portrait of your screenshots and the 1:1 square of your app icon. Each of these three Play Store assets has completely different compositional logic, and the feature graphic's widescreen format demands landscape-native thinking. Designers who think in portrait instinctively try to center a phone mockup on the canvas — the result is a small device surrounded by dead horizontal space, technically valid dimensions but compositionally empty. See the screenshot sizes reference for the full table of Play Store asset dimensions, including phone, tablet, and Chromebook sizes.
The file is stored per locale in Play Console. You can upload a separate 1024×500 for each language your listing supports, and for high-volume non-English markets you should. A generic English asset in a Japanese or Brazilian listing is a visible signal of low effort. At minimum, translate any text in the graphic for your three largest non-English install markets.
Using a screenshot as your feature graphic always looks wrong
The most common shortcut is dropping a portrait screenshot into the 1024×500 canvas, either centered on a colored background or cropped to fit the wider frame. Both approaches fail for the same reason: a screenshot is a 9:16 asset built to communicate UI density, and the feature graphic is a 2:1 asset built to communicate brand and benefit. Cropping the portrait throws away whichever part of the screen mattered. Centering it on a background leaves a small phone surrounded by nothing — a composition that communicates no design decision was made here.
The gap goes beyond aspect ratio. Screenshots are the fourth or fifth thing a user looks at, after icon, name, ratings, and possibly the subtitle. The feature graphic sits above all of that. When Google promotes your app in an editorial row, the feature graphic is what users compare side by side with every other app in the carousel. At thumbnail width, a screenshot-as-banner reads as a missing asset while the apps beside it have clear visual identities. The correct fix is to design the feature graphic as a distinct problem: your app name or logo, a single benefit statement in large type, and a hero visual that is explicitly not a portrait phone screenshot.
Safe zone: keep critical elements inside a 924×400 centered rectangle
Google Play overlays a play button in the lower center of the feature graphic whenever your listing includes an app preview video. On smaller Android devices, the outer edges of the graphic can also be clipped depending on which layout template Play Store uses for that screen size. The practical safe zone is a 924×400 pixel rectangle centered on the canvas — 50 pixels of buffer on all four sides. Content inside this area survives both the play button overlay and edge crops on every device class. Content outside it may be partially hidden on a live listing even though Play Console's built-in preview renders it fine.
A common error is placing the app name or tagline near the right or left edge of the canvas, which looks correct in design tools and breaks on a real phone. The fix is mechanical: never place critical text within 60 pixels of any edge, and always preview the graphic at 400–500px rendered width before uploading. The play button position is also why you should avoid centering your primary visual — logo, character, or hero image — exactly in the middle of the frame. A play button rendered over your logo creates a visual conflict. Offset the primary focal point to the upper third or to one lateral half, and use the opposite half for the tagline.
Light and white backgrounds disappear into the Play Store interface
Google Play's store interface is predominantly white. A feature graphic with a white, off-white, or very light gray background has no visual boundary when it renders in the listing — it bleeds into the surrounding UI and effectively disappears as a design element. The lightest background that holds a visible edge maintains at least 8% saturation away from pure white in any direction. The practical rule is simpler: use your app's brand color as the background. The feature graphic occupies more visual area than your icon and is the first element rendered in the listing. Treating the background as a neutral container is a waste of the most prominent branding surface in the entire Play Store listing.
The one exception: apps whose entire visual identity is deliberately minimal — writing tools, note-taking apps, productivity utilities where white is the intentional brand. In these cases, use an extremely pale tint of your primary accent color rather than pure white. A 5–8% tinted background reads as a design choice; pure white reads as a missing asset. If your brand genuinely has no prominent color other than white, borrow a neutral from your icon and use it at 15–20% opacity over white. The goal is a visible boundary, not dramatic contrast.
Three elements maximum — and the hero visual must dominate
Once a feature graphic canvas exists, the instinct is to add: a subtitle beneath the tagline, a ratings badge, a "new" label, a short feature list. Each addition dilutes everything else. At the sizes Play Store renders the feature graphic — around 400px wide in search row results, smaller in editorial features — you have room for roughly three visual elements before the composition becomes noise. The three that work: logo or app name in brand typeface, a tagline of no more than eight words, and one hero visual. The hero should be the largest element, the logo the smallest, and the tagline between them in visual weight.
A useful calibration before uploading: screenshot the graphic, scale it to 400px wide, and view it from arm's length. You should know in two seconds what the app does and feel something about whether it fits your life. If you are squinting at the tagline or unsure what the hero image is, the composition needs work. The AppsTemple editor includes a 1024×500 Play Store canvas with a safe zone grid overlay — use it to verify layout at thumbnail preview width before uploading to Play Console.
Play Store feature graphic content rules: what Google bans
Google's content policy for feature graphics bans several things that catch developers off guard: pricing information ("Free", "50% off", "$0.99"), ranking and award claims ("#1 in Productivity", "App of the Year", "Best of Play"), time-sensitive promotional language ("New", "Limited Time"), and any UI chrome that mimics Play Store itself, including fake download buttons or fabricated star-rating displays positioned to look like Google's native UI. Violations are enforced at review and can block new submissions.
The award and ranking ban catches the most apps because rankings feel like legitimate social proof. Google's published reasoning is that claims like "#1 in Productivity" look like endorsements from Google itself, and they become actively false when the ranking changes. Press mentions with explicit attribution are allowed — "Featured in The Verge" or "Editor's Choice — Android Authority" — as long as the phrasing does not imply current Google endorsement. On the technical side, always export as JPEG rather than PNG if there is any chance of embedded alpha. A transparent feature graphic renders with an inconsistent background depending on context, and Play Console's preview will not always catch it. JPEG at 90% quality eliminates the risk entirely.
The feature graphic is your billboard, not your release blocker
Most developers encounter the feature graphic upload requirement at the final step of a Play Console submission and solve it in ten minutes with a cropped screenshot and a color picker. That is why most listings look indistinguishable — not actively bad, just invisible. The 1024×500 canvas is small enough to design well in a single session, and it sits at the top of every listing view, every Google-curated editorial row, and every app preview link shared outside the store.
The investment to get it right is one focused afternoon: brand color background, app logo, an eight-word tagline, one hero visual offset from center, everything inside the 924×400 safe zone. Export as JPEG, preview at 400px width, upload. That is the whole job.
Open the Play Store canvas in the editor →
Frequently asked questions
what size is the play store feature graphic?
The Play Store feature graphic is exactly 1024×500 pixels. Google Play Console does not accept any other dimensions — not scaled versions, not cropped variants, not the same aspect ratio at a different resolution. File format is PNG or JPEG, 24-bit color, no alpha channel, maximum 15 MB.
is the feature graphic required to publish on google play?
Yes. Google Play Console blocks publishing until a feature graphic is uploaded. It is mandatory for every new app listing and every submission that triggers a listing review. It is not optional the way screenshots beyond the minimum count are optional.
can i use a screenshot as my play store feature graphic?
Technically yes — the upload will accept any compliant 1024×500 JPEG or PNG. Strategically, no. A portrait screenshot cropped or padded to landscape always looks like no design decision was made. At the sizes Play Store renders the feature graphic in editorial rows and search results, a portrait-derived layout reads as a missing asset next to purpose-built feature graphics.
what text is not allowed on a play store feature graphic?
Google bans pricing information ("Free", "50% off"), ranking claims ("#1 in Productivity", "App of the Year", "Best of Play"), time-sensitive promotional language ("New", "Limited Time"), and fake UI elements that mimic the Play Store interface. Attributed press mentions are allowed as long as they do not imply current Google endorsement.
how do i a/b test my play store feature graphic?
Google Play's Store Listing Experiments (in Play Console under Grow → Store Listing Experiments) let you pit two feature graphic variants against each other and measure install rate. Run each experiment for a minimum of two weeks and 1,000 impressions per variant before reading results. The winning variant can be promoted to the primary listing directly within the tool.