Google Play Feature Graphic: Size, Placement, and How to Make One

The Google Play feature graphic is a 1024 x 500 banner, saved as JPEG or 24-bit PNG with no alpha channel, and Play Console won't publish a store listing without one. To make it, set up a 1024 x 500 canvas in a design tool, keep your logo, app name, and slogan near the middle, push decorative background to the edges, and export a flat file with no transparency.

That's the whole spec, and it fits in one line on our Google Play screenshot sizes page. The harder part is where to put things, because Google's preview assets help page marks "cutoff zones" in red on an example image but never gives them in pixels, and it notes that some placements lay their own interface over the graphic. A banner that looks finished on your monitor can lose the first letters of the app name in one placement and have a play button sitting on the slogan in another. The steps below work around that gap: what Google uses the graphic for, a layout that survives the crops, how to build it in Figma or Canva, and a two-command check of the export before upload.

Where Google shows it

Google lists three places on the help page. If your listing has a preview video, the feature graphic is the video's cover image, and people start the video by tapping a play button drawn on top of it. For apps, Google can show the graphic in large-format collections, which the page says include ads. For games, it appears in groups of recommended games. The page doesn't describe a placement on the listing itself when there's no video, so plan for the graphic to be seen mostly in collections and on the video cover, often at a fraction of its full size and next to other apps' banners.

That last point changes how much detail is worth adding. Google asks you to avoid fine detail because it won't be visible on many phone screens, and at collection size a paragraph of small type turns into texture. One large name and a short phrase is about as much text as the banner can carry. Google also asks for vibrant colors instead of pure white, black, or dark gray, which makes sense once you picture the banner sitting on a white or dark store background.

Keeping the focal point clear of the crop

Google's guidance has two parts that pull against each other. It wants the prominent visuals and focal point toward the center, with background elements restricted to the edges, and it says key elements (brand logo, app name, primary slogan, and main UI) shouldn't sit in the cutoff zones. But if you add a preview video, the center is also where a play button lands. So the usable area is a band through the middle of the banner, with a small circle in its center that you keep free of text.

Since Google gives no numbers, we use a working margin of 128 pixels on the left and right and 50 pixels on the top and bottom, which leaves a 768 x 400 box in the middle. Keep the logo, the app name, and any words inside that box, and let gradients, pattern, or illustration run out to the edges where a crop won't matter. Put the name and slogan above or beside the center rather than on it, because the play button will cover whatever sits at the exact middle. If you don't have a video today, it's still worth leaving that spot clear, since adding one later shouldn't mean redrawing the banner. None of this is an official spec, so when you upload, open the preview in Play Console and check that nothing important is clipped.

Some things don't belong anywhere on the canvas. Google asks you to leave out device imagery, Play badges and icons, third-party characters or logos you don't have permission for, and wording about ranking, awards, testimonials, price, or promotions, with "Best," "#1," and "Free" as its examples. Seasonal or dated text goes stale and is on the same list. Google's cutoff list names "main UI" as a key element, which we read as room for a cropped panel of your interface on the banner, as long as it isn't inside a phone frame.

Making one in Figma or Canva

In Figma, add a frame at 1024 x 500, fill the whole frame with a background color or image so no pixel is transparent, and build the layout on top. Drop a 768 x 400 rectangle centered in the frame and a circle about 140 pixels wide at its center as guides (the circle is our estimate of the play button, since Google doesn't size it), then hide both before export. Export the frame as PNG at 1x, which gives you exactly 1024 x 500. If you're also making the screenshots in Figma, the Figma App Store screenshot template post covers the frame and export setup, which carries over to this banner with a different canvas size.

In Canva, choose Create a design, then Custom size, and enter 1024 by 500 pixels. If you start from one of Canva's templates, resize it to these dimensions and replace the stock fonts and colors with your own. Download as PNG or JPG, and leave the transparent background option off. The Canva App Store screenshots post walks through the brand kit and download settings in more detail.

Whichever tool you use, build the feature graphic after the screenshots, not before. The banner and the first screenshots often appear close together, and a banner in a different palette or typeface reads like a different product. Reuse the screenshot set's background color, headline font, and one piece of its art, and the banner looks like part of the same listing.

Checking the export before you upload

Google requires exactly 1024 x 500 with no alpha channel, and a wrong size or a hidden alpha channel is invisible when you look at the image. Some design tools write an alpha channel into a PNG even when every pixel is opaque, so check the file itself. On a Mac, sips reads the header:

sips -g pixelWidth -g pixelHeight -g hasAlpha feature-graphic.png

You want pixelWidth: 1024, pixelHeight: 500, and hasAlpha: no. If hasAlpha comes back yes, flatten the file onto your background color with ImageMagick:

magick feature-graphic.png -background "#1E2A44" -alpha remove -alpha off feature-graphic-flat.png

Swap the hex value for the banner's own background color. Saving as JPEG also removes the alpha channel, though JPEG compression can blur thin type and leave halos around sharp edges, so use PNG when the banner has small lettering.

Uploading and translating it

The upload field is in Play Console under Grow users, Store presence, Main store listing, in the Graphics section next to the app icon, screenshots, and preview video link. Google's page asks for alt text of 140 characters or less, so describe what the banner shows in a plain sentence. A preview video goes in the same section as a YouTube URL, and Google requires ads to be turned off for it, the privacy setting to be public or unlisted, and embedding to be allowed.

If your listing has translations, Google asks you to localize the graphic and branding text for each market. Keep the layout and swap only the words, and check the longest translation against the same 768 x 400 box, because German and French phrases often run wider than the English one. The Google Play screenshots post covers the screenshot rules that sit beside the banner on each language's listing, including the 20% tagline limit and the status bar guidance. Store listing edits go through Google's review before they show on the store.

Screenies and the rest of the Play listing

Screenies doesn't make feature graphics, so the 1024 x 500 banner stays a design job, built with the steps above. It generates the Play screenshots that sit beside the banner, from your own Android captures, in portrait or landscape for phones and tablets. If you generate the phone screenshots first, the banner can borrow their background color and headline font. Uploading those screenshots from the dashboard needs a credit pack purchase and a Google Play service account key for the app's package, and the feature graphic still goes in by hand in Play Console.