Skip to content
webtoapkfree

What size is the Google Play feature graphic?

The Google Play feature graphic size is 1024 x 500 px, saved as a JPEG or 24-bit PNG with no alpha. It is required to publish a store listing.

GuidesNookesh Karri

Light cover card with the title 'What size is the Google Play feature graphic?' in dark text and a green accent bar

The Google Play feature graphic size is 1024 x 500 pixels. Google requires it as a JPEG or a 24-bit PNG with no alpha, so no transparency, and you can’t publish a store listing without one.

Everything else you read about feature graphics is either a Google recommendation or someone’s opinion, and most guides blur the two.

Google Play feature graphic size and format

The Google Play feature graphic must be exactly 1024 px wide and 500 px tall. The Play Console preview assets page lists the mandatory requirements:

Requirement Value
Dimensions 1024px by 500px
File type JPEG or 24-bit PNG
Transparency Not allowed (no alpha)
Required? Yes, to publish your store listing

“You must provide a feature graphic to publish your store listing,” the page says. That holds even if your app has no preview video.

If your design tool exports PNG with an alpha channel by default, flatten the image or save it as JPEG. Alpha belongs on the app icon, not here.

Is there a file size limit?

Google’s preview assets page doesn’t give a file size limit for the feature graphic. The only file size limit on that page is “Maximum file size: 1024KB,” and it belongs to the 512 x 512 app icon.

Some blogs quote a megabyte limit anyway. The Sonar guide agrees that Google doesn’t document one. A 1024 x 500 JPEG is small, so this rarely matters.

Where the feature graphic appears

Google’s page gives the feature graphic two main jobs:

  • Video cover. It is shown “As a cover image for your preview video, if present.”
  • Large collections. “For apps, we show a collection of apps in a large format with your feature graphic, including ads.” For games, it appears in large-format groups of recommended games.

Nothing on Google’s page says it shows up in keyword search results, and Sonar notes the same gap. Some guides claim it does. Don’t design for it.

How the preview video changes it

With a preview video, the feature graphic becomes the video’s poster. Google says the video “may autoplay inline with muted audio up to 30 seconds.” When it doesn’t autoplay, a play button is overlaid on your feature graphic.

Google doesn’t say where that button sits. One popular guide tells you to keep the bottom-right corner clear for it, but Google’s documentation says no such thing. Follow Google’s own advice instead: keep the focal point near the centre and don’t bet on any single corner.

The video itself has rules too: one YouTube URL (not a playlist or channel), ads turned off, public or unlisted rather than private, not age-restricted, and embeddable.

Safe area and cutoff zones

Google’s cutoff zones are the areas near the edges where the feature graphic may be cropped. Google says to keep “prominent visuals and the focal point towards the center of the graphic” and to keep your brand logo, app name, main slogan and main UI out of the cutoff zones, because the image “may be cut off depending on the UI format.”

Google shows those zones only as red areas in an example image. There are no pixel values. Sonar puts it bluntly: “Anyone quoting an exact ‘safe area’ in pixels is either measuring that diagram or guessing.”

This is a recommendation, but ignoring the focal point and cutoff zones “may result in ineligibility to appear in these formats.” Google also suggests you “Restrict background elements to the edges of the graphic.”

My take: put your app name and one short line in the middle third of the width and make the outer edges pure background. That layout survives any crop Google is likely to apply.

What to avoid on a feature graphic

Google’s recommendations list these things to leave out. None of them block the upload, but they can cost you placement:

  1. Promotional words. Avoid “Best,” “#1,” “Top,” “New,” “Free,” “Discount,” “Sale,” or “Million Downloads.”
  2. Time-sensitive art. Holiday themes are fine only if you swap them in and out on time.
  3. Other people’s brands. No third-party trademarked characters or logos without permission, and no Google Play or other store badges.
  4. Device frames. Google lists device imagery as something to avoid.
  5. A copy of your icon. Don’t repeat prominent branding that looks like your app icon.
  6. Fine detail. Google warns small details “will not be visible on many phone screens.”
  7. Plain backgrounds. Pure white, black or dark gray “can blend in with Google Play’s background.”

Google also recommends localizing any text in the graphic and adding alt text “using 140 characters or less.”

Feature graphic vs Android TV banner

The Android TV banner is a different asset at 1280 x 720 px. Google says “A banner asset is required to publish an Android TV-enabled app,” and that it is displayed only on Android TV devices.

Asset Size Who needs it
Feature graphic 1024 x 500 px Every store listing
Android TV banner 1280 x 720 px Android TV-enabled apps only
App icon 512 x 512 px Every store listing

Both the feature graphic and the TV banner use JPEG or 24-bit PNG with no alpha. For the icon’s own rules, see the Android app icon size guide.

A feature graphic checklist for a WebView app

A WebView app’s listing needs the same feature graphic as any other app. Before you upload, check that:

  • The file is exactly 1024 x 500 px.
  • It’s a JPEG, or a PNG saved without transparency.
  • The app name and main message sit near the centre.
  • No promotional words, store badges or phone frames.
  • The background isn’t plain white, black or dark gray.
  • Text is short enough to read on a phone.

Web2Apk builds the signed APK and the AAB, with your app name, icon and colour set in the editor. It doesn’t make store graphics or fill in your listing. A generated AAB isn’t Google Play approval either; the developer account, listing, testing and policy checks are separate steps covered in the guide to publishing a WebView app on Google Play.

One limitation: no feature graphic will save a weak app. If your app is a thin wrapper around a website, read why Google rejects WebView apps for minimum functionality before you spend time on artwork. Also plan for the closed testing rule for new accounts and what publishing costs.

FAQ

What size is the Google Play feature graphic?

1024 by 500 pixels. Google requires a JPEG or a 24-bit PNG with no alpha channel, so the image can’t have transparency.

Is the feature graphic required on Google Play?

Yes. Play Console Help says you must provide a feature graphic to publish your store listing, even if you never add a preview video.

What is the maximum file size for a feature graphic?

Google’s preview assets page doesn’t state one. The only file size limit on that page is 1024 KB for the 512 x 512 app icon, so treat any specific feature graphic limit you read elsewhere as unofficial.

Where does the play button sit on the feature graphic?

Google says a play button overlays the feature graphic when your preview video doesn’t autoplay, but it doesn’t give an exact position. Keeping your main message near the centre and away from the edges is the safe choice.

Is the feature graphic the same as the Android TV banner?

No. The Android TV banner is 1280 x 720 px, is required only for Android TV-enabled apps and is shown only on Android TV devices. Every listing needs the 1024 x 500 feature graphic.

Sources