Feature Graphic Generator
Build a Google Play feature graphic at exactly 1024 x 500 and have it checked against Google's own preview asset rules before you upload: cutoff zones, banned wording, background colour, type size and contrast. Free, no account, no watermark, no export limit.
Last updated 8 October 2026
Optional. Paste a listing and the icon, name and short description are pulled in and the colours are matched to your icon. Or skip it and build from scratch below. Free, no account, no watermark, no export limit.
App icon
Imported from your listing, or upload your own.
The PNG is written as colour type 2, so the file has no alpha channel at all rather than an alpha channel full of 255. That is the difference between the 24-bit PNG Play Console asks for and the 32-bit RGBA one a browser canvas normally produces.
Optional, and separate from the image. Play Console has a field for it next to the asset, and Google asks for one on every graphic you upload.
Describe the important part. Do not start with “image of”.
What the app does, not what it is called. Play prints your app name under this already.
Icon, headline and subhead stacked in the middle, well inside the crop.
Checked against Google's preview asset rules
All clear.
Pass: Exactly 1024 x 500 px
The canvas is fixed at the required size, so the export cannot be a pixel out. Play Console rejects anything else.
Pass: 24-bit, no alpha channel
The background fills the whole canvas before anything is drawn on it, so there is no transparency to strip. A transparent PNG is the other upload rejection.
Pass: No ranking, price or award claims
Your copy is clear of the wording Google names: Best, #1, Top, New, Free, Discount, Sale, Million Downloads.
Pass: Background stands off the Play Store page
Far enough from white, black and dark grey that the graphic keeps its edges in both light and dark theme.
Pass: Text reads against the background
Contrast is 6.3:1 at the worst point of the gradient.
Pass: Everything is inside the safe area
Icon, headline and subhead all sit within the central 860 x 400, so they survive the crops Google applies on different surfaces.
Pass: Type survives the phone screen
The graphic is displayed a few centimetres wide on a phone. Nothing here is below the size that stays readable at that scale.
Pass: Not a repeat of the icon
Play already shows your icon and name under the graphic. This adds something rather than saying it twice.
Rules taken from Play Console Help, Add preview assets to showcase your app. Only the size and the alpha channel are enforced at upload. The rest is Google telling you what keeps an asset eligible for the placements that crop it.
What is a Google Play feature graphic?
A feature graphic is the 1024 x 500 banner that sits at the top of a Google Play listing, above the screenshots. It is required for every app and game, so a listing cannot be published without one. Google also uses it in editorial and recommendation placements, and as the cover image for your preview video if you have one.
It is the only store asset where you control a full-width canvas, and it is the first thing a visitor sees before they have read a word of your description. It is also the asset most often treated as a formality: a logo on a gradient, uploaded once, never revisited.
Google Play feature graphic requirements
| Requirement | Value | Why it matters |
|---|---|---|
| Dimensions | 1024 x 500 px | Exact. Play Console rejects 1023 or 1025. |
| Format | JPEG or 24-bit PNG | Colour type 2. A 32-bit RGBA PNG is not the same thing. |
| Transparency | No alpha channel | The second of the two upload rejections. |
| Required | Yes, for every app and game | You cannot publish a store listing without one. |
| Alt text | 140 characters or fewer | Asked for on every graphic asset. Do not open with "image of". |
| Also used as | The cover for your preview video | A play button is overlaid on the middle when the video does not autoplay. |
Source: Play Console Help, Add preview assets to showcase your app.
Every generator gets the size right. The size is the easy half.
There are a dozen free Play Store feature graphic generators and they all do the same thing: a 1024 x 500 canvas, a gradient, a logo, a headline, a download button. That is enough to clear Play Console, because Play Console only checks two things at upload. It is the correct pixel size and the PNG has no alpha channel. Pass those and your asset is accepted.
Accepted is not the same as eligible. The rest of what Google publishes about the feature graphic is a list of things that decide where the asset is allowed to appear, and Google is explicit that an asset which ignores the focal point and cutoff zone rules is ineligible for the formats that crop it. Nothing tells you. There is no warning in Play Console, no email, no line in the dashboard. The graphic is live on your listing and quietly absent from the placements you would have wanted it in.
So the default output of a template generator is a trap with good manners. The template puts your icon large in the middle, which is the one thing Google asks you not to do, because Play prints your icon and app name directly underneath. The headline field invites “#1 Free App”, which is two entries from Google's own list of wording to avoid. The default background is white, which Google singles out because it is the Play Store's own background colour and your graphic dissolves into the page.
| Rule | Enforced at upload? | What it costs you if you miss it |
|---|---|---|
| Exactly 1024 x 500 | Yes | The upload is rejected outright. |
| No alpha channel | Yes | The upload is rejected outright. |
| Key elements out of the cutoff zones | No | Google states the asset is ineligible for the formats that crop. |
| No ranking, price or award wording | No | A policy issue you find out about later, if at all. |
| Not a repeat of your icon | No | Half your banner spent saying what is already printed below it. |
| Not white, black or dark grey | No | The graphic blends into the Play Store page. |
| No device imagery or store badges | No | Ages quickly, and store badges are explicitly out. |
| Alt text under 140 characters | No | Inaccessible to screen readers, and a discoverability signal left on the table. |
The generator above checks every row of that table as you type. That is the only real difference between it and the others, and it is the whole reason it exists.
How to make a Google Play feature graphic
- 1
Paste your store listing, or skip it
A Google Play or App Store URL pulls in your icon, app name and short description, and sets the background from the colours in your icon. Building from scratch works the same way, you just pick the colours yourself.
- 2
Write a headline that is not your app name
Play prints your icon and app name under the graphic already. Use the headline for what the app does. Keep it to about four or five words so it survives being a few centimetres wide on a phone.
- 3
Keep everything inside the safe area
Turn on the safe area overlay and check nothing crosses it. Google crops the edges differently on different surfaces, and an asset with key elements in the cutoff zones is ineligible for the formats that crop.
- 4
Clear the warnings
The checks below the canvas run against Google’s published preview asset rules: banned wording, background colours that blend into the Play Store, contrast, type size and the safe area. None of them block an upload. All of them affect where your graphic is allowed to appear. Alt text sits outside the checks, next to the download, because it is typed into Play Console rather than drawn into the file.
- 5
Export and upload
Download the 24-bit PNG or the JPEG, then upload it in Play Console under Grow, Store presence, Main store listing. Paste the alt text into the field next to it.
Why a PNG with no transparency still gets rejected
Google asks for a 24-bit PNG with no alpha. People read that as “no transparent background”, paint the canvas opaque, export, and get bounced anyway. The two are not the same claim.
A PNG stores a colour type in its header. Type 2 is truecolour: three bytes per pixel, red, green and blue, and no alpha channel in the file. Type 6 is truecolour with alpha: four bytes per pixel, and the fourth one exists whether or not you used it. Painting your background opaque sets every alpha value to 255. It does not remove the channel. The file is still 32-bit, and it is still not what Google asked for.
This is not a niche edge case, it is the default behaviour of the tools people reach for. A browser canvas is RGBA and toDataURL('image/png') always writes colour type 6, so every generator that draws on a canvas and calls it is handing you a 32-bit file. Most design tools do the same unless you go and find the setting.
Two ways out
Export a JPEG, which has no concept of an alpha channel and cannot carry one. It is the usual advice and it works, at the cost of compression artefacts around type, and type on a flat gradient is close to the worst case for JPEG.
Or write the PNG as colour type 2. The PNG button above does that: it reads the pixels off the canvas, drops the alpha channel rather than filling it, and assembles the file by hand. What you download has three bytes per pixel and no alpha channel to strip, which is the 24-bit PNG in Google's sentence, with the type still sharp.
The safe area, and why nobody agrees on the number
Google does not publish a safe zone measurement for the feature graphic. The guidance shows an example image with red bands along the edges labelled as cutoff zones and asks you to keep the focal point and key elements, meaning your brand logo, app name, primary slogan and main UI, towards the centre. That is the whole specification: a picture and a direction.
Which is why the guides that quote a figure do not agree with each other. One measures the diagram at 860 x 480, another at 924 x 400. Both are somebody holding a ruler up to the same PNG. This tool draws a centred 860 x 400 box, which is the intersection of those two readings and therefore survives either crop. It is an inference, and it is labelled as one on the canvas rather than presented as a spec.
There is a second exclusion zone that does have a fixed location, and it is in the worst possible place. If you attach a preview video, Google uses the feature graphic as its cover and overlays a play button whenever the video does not autoplay. That button lands in the middle, directly on top of the centre Google just told you to design towards. The two pieces of guidance are in tension and Google does not reconcile them.
The resolution is that “centred” means centred as a composition, not centred as a pile of text on the middle axis. If you have a preview video, weight the artwork centrally and move the words off to one side. Ticking “I have a preview video” above draws the button where it will land, so you can see whether your headline is behind it.
What Google asks you to keep off it
The wording rules are unusually specific for Google, which names the examples rather than gesturing at a category. These are all from the same preview assets page.
Ranking and performance claims
Google gives Best, #1 and Top as examples. Anything that reflects or suggests your Play Store performance or ranking is out, including Million Downloads.
Price and promotional wording
Free, Discount and Sale are named. So is promotional information generally, which covers limited-time offers and percentages off.
Awards and testimonials
Accolades, awards and user testimonials are all on the avoid list. That includes star ratings and review quotes, however genuine they are.
Store badges
The Google Play badge, or any other store’s badge or icon, should not appear on the graphic. Neither should third-party trademarked characters or logos you do not have permission for.
Device imagery
Phone and tablet mockups are on the avoid list because hardware dates quickly and alienates people using something else. A bare screenshot crop carries the same information.
Anything time-sensitive
Google flags content that becomes outdated, and names New alongside the promotional wording. Seasonal graphics are fine if you actually swap them back.
One more that is easy to miss, because it reads like design advice rather than a rule: avoid pure white, black and dark grey. Those are the Play Store's own background colours in light and dark theme, so a graphic painted in them loses its edges and reads as part of the page furniture rather than as your app. It is the single most common thing wrong with the feature graphics currently on the store.
Questions
What size is a Google Play feature graphic?+
Exactly 1024 x 500 pixels, as a JPEG or a 24-bit PNG with no alpha channel. There is no tolerance and no alternative aspect ratio: Play Console rejects the upload if the file is a single pixel out or if the PNG carries transparency. Those two things are the only part of the spec enforced at upload time. Everything else Google publishes about the feature graphic is guidance that decides which placements your asset is eligible for, not whether it uploads.
Is this feature graphic generator free?+
Yes. No account, no email, no watermark, no daily export cap and no trial that ends. The composition happens on a canvas in your browser, so the image never reaches a server and there is nothing for us to meter. The paid product is an AppPage smart link, which is a separate thing that solves a separate problem: routing people to the right store once they click something.
Why does my feature graphic get rejected by Play Console?+
Almost always one of two things. Either the file is not exactly 1024 x 500, usually because a design was exported at a scale factor, or the PNG has an alpha channel. The second one catches people out because a fully opaque PNG can still carry an alpha channel: browser and design tool exports are commonly 32-bit RGBA with every alpha value set to 255, which is not the 24-bit PNG Google asks for. Exporting a JPEG sidesteps it, and so does the PNG from this page, which is written as colour type 2 with no alpha channel in the file at all.
What is the safe zone for a Play Store feature graphic?+
Google does not publish one as a number. The guidance shows an example image with red "cutoff zones" along the edges and asks you to keep the focal point and key elements, meaning your logo, app name, primary slogan and main UI, towards the centre. Third-party guides infer figures between 860 x 480 and 924 x 400. This tool draws a centred 860 x 400 box, which is the conservative reading that survives both crops, and tells you when something crosses it. That is an inference from Google’s diagram, not a published figure.
Can I put my app name and icon on the feature graphic?+
You can, but Google asks you not to. Play already prints your icon and app name directly beneath the feature graphic on the listing, and the guidance says not to use prominent branding similar to your icon because it duplicates what is already on screen, and to treat the graphic as an extension of the icon instead. The practical version: use the space to say what the app does. The name is covered.
What words are not allowed on a feature graphic?+
Google names the examples outright: Best, #1, Top, New, Free, Discount, Sale and Million Downloads. The categories behind them are wider than the examples, covering anything that reflects or suggests Play Store performance or ranking, user testimonials, accolades and awards, and price or promotional information. Store badges and third-party trademarked characters or logos are out too, as is device imagery, because hardware dates quickly. The generator on this page checks your headline and subhead against all of it as you type.
Does the feature graphic affect Play Store ranking or conversion?+
Not ranking directly. Its job is conversion and placement eligibility. It sits at the top of your listing, above the screenshots, and it is what Google uses in editorial and recommendation surfaces where your app appears in a large format. Google states that an asset which does not comply with the focal point and cutoff zone rules is ineligible to appear in those formats, so a graphic with the headline jammed against the left edge is not penalised so much as simply left out of the placements that would have shown it.
Should I use a phone mockup in my feature graphic?+
No. Google lists device imagery among the things to avoid on a feature graphic, on the grounds that it dates quickly and alienates people using other hardware. A bare screenshot crop or a simplified view of the UI carries the same information without the bezel, so if you bring your own artwork in, crop the bezel off it first.
Can I use the same feature graphic on the App Store?+
Not as it is. Since iOS 27 the App Store has a similar slot, the product page header, but it is a different shape: 3840 x 1646 at 21:9 rather than 1024 x 500, with a search results asset at 3:2 alongside it. Scaling a feature graphic up to fit loses most of its height and all of its sharpness. The App Store creative asset generator on this site makes the header, the search results asset and the universal asset from the same icon and colours.
Other free tools
App Store Creative Asset Generator
The App Store side: the iOS 27 product page header and search results asset, inside the safe areas from Apple's templates.
App Store QR Code Generator
A download QR code with your app icon in the middle, from an App Store or Google Play link. Static, so it never expires.
App Icon Generator
One 1024px image into every icon iOS, macOS, Android and Google Play ask for, with the alpha channel and safe zone checks they reject on.
App Link Shortener
One short link that sends iPhone users to the App Store and Android users to Google Play, with a web fallback on desktop.