Google Play Feature Graphic
Design a Google Play Feature Graphic at the required 1024 × 500 px size. Pick a template, add your app name, screenshot, and colors, then export a PNG for Google Play Console.
A Google Play Feature Graphic is the wide banner at the top of your store listing. This page is the editor: files stay in the browser, the canvas stays locked to spec, and you leave with artwork you can attach in Play Console today.
How to make a Google Play Feature Graphic
Choose a 1024×500 template
Open a Gaming, Media, Productivity, or Social layout. Every template loads on a locked 1024 × 500 px canvas, so the export matches Play Console instead of a freeform artboard you later crop.
Edit text, color, and screenshots
Click type to rewrite the headline. Change fonts, fills, and shadows in the side panel. Swap the background, drop in a logo, or place an app screenshot inside a phone or tablet frame so the banner shows a real product, not a blank gradient.
Download the PNG for Play Console
Export a lossless 1024 × 500 PNG to your device. In Google Play Console, attach it as the feature graphic on the store listing. Keep a copy of the project in the editor if you need a seasonal variant later.
Templates, canvas, and PNG export for Play Console
24 layouts built for Play Store width
Start from Gaming, Media, Productivity, Social, or generic compositions. Each layout already respects the short, wide 1024 × 500 frame instead of stretching a square icon across the banner.
Drag-and-drop canvas
Select a layer, then drag it. Nudge position and size with pixel fields when a headline sits on a screenshot edge. The work stays on this page — you do not bounce to a separate design app to finish the banner.
Type, color, and contrast controls
Fourteen Google Fonts, custom fills, gradients, shadows, and outlines. Store thumbnails shrink your banner; high-contrast type is what still reads in search results and featured rows.
Phone and tablet frames
Draw device chrome in the browser and drop a screenshot into the screen. A feature graphic with a real UI beats a logo-only strip when shoppers compare Android apps.
Local image layers
Use JPG, PNG, or WebP as a background or a layer. A dark overlay keeps white text readable on photos. Nothing is uploaded to Pixwit servers while you build the banner.
Spec-locked PNG export
One click writes a 1024 × 500 lossless PNG. That is the size Google Play expects for the feature graphic field, so you skip a second pass in an image resizer.
Google Play Feature Graphic size, safe area, and export
The Google Play Feature Graphic is a required 1024 × 500 pixel banner for Android listings. Shoppers see it first on the store page, and the same file can appear in featured placements. Treat it as store packaging, not a second app icon: the canvas is short and wide, text must survive thumbnail size, and the file you upload has to match Console exactly. This editor locks those pixels in the browser so you design once and export a PNG that fits.
Exact pixels and why crop-after fails
Google asks for a banner that is exactly 1024 pixels wide and 500 pixels tall. A 16:9 YouTube thumbnail, an iOS promo, or a square social post will stretch or letterbox when you force it into that slot. Play Console rejects the wrong dimensions or quietly scales a file until edges vanish. Building on a locked 1024 × 500 board is faster than designing at an arbitrary size and discovering the headline sits in a crop. If you already have a larger key art file, place it as a background here and reposition until the important UI and type sit inside the live area — then export. Do not add a second resize step that introduces compression before Console.
What belongs on the banner
A strong banner usually carries three things: the app name or a short promise, a readable screenshot or character, and enough empty space that the layout still works when Google slightly crops the edges. Put the logo in a corner, not as a giant watermark. Avoid paragraphs, store-star screenshots, and legal lines — those belong in the listing body. Category cues help: a game can show a hero and a verb; a utility app can show a clean UI and one benefit. If two products in your niche use the same purple gradient, change color and type so the feature graphic is recognizable in a grid of similar Android listings.
Safe area, localization, and seasonal swaps
UI chrome and featured carousels can clip the outer margin. Keep faces, badges, and the last word of a headline away from the extreme left and right. If you ship in more than one language, duplicate the layout and replace only the text layer instead of redrawing art. Seasonal Play Store campaigns are the same banner with a new line and color — export a dated PNG and archive the previous file so you can revert after the campaign. The editor is local, so those variants stay on your machine unless you save them elsewhere.
Screenshots inside device frames
Empty gradients look like stock templates. Dropping a current screenshot into a phone or tablet frame makes the banner feel like the product. Use a light UI on a dark background (or the reverse) so the device does not melt into the art. Crop the screenshot to the first screen a new user sees, not a dense settings page. If the app is a game, a key art character can replace the device, but keep the silhouette simple at small sizes. Replace the screenshot whenever onboarding changes; a stale phone frame looks unmaintained next to competitors who update with each release.
Export, file type, and Console upload
Download PNG. JPEG is allowed in some Play asset slots, but type and logos stay sharper as lossless PNG. In Play Console, open the store listing, find graphic assets, and replace the feature graphic. Changes can take hours to appear publicly. Keep the source composition for the next screenshot. If Console shows a preview crop, confirm the PNG is truly 1024 × 500 pixels before you file a support ticket.
Mistakes that waste a listing
Do not paste the Play Store icon into the banner and call it done. Do not cover the art with a QR code, a fake rating, or “#1 app” claims you cannot support. Do not use tiny type that vanishes on a phone. Do not design at 2048 × 1000 and then upload a muddy JPEG. Stay on this page when you need a spec-correct still with templates and local images. Use a screenshot mockup tool for taller listing screenshots, and a video thumbnail maker for YouTube stills — those are different aspect ratios and review rules.
Official size rules: Google Play graphic assets (Play Console Help)
When you need a Google Play Feature Graphic
First-time Play Console listings
You cannot skip this asset when you publish an Android app. Build the banner here at 1024 × 500 before you fill the rest of the store listing, so review is not blocked on a missing graphic.
Updates, rebrands, and seasonal art
A version bump or a new icon should be mirrored on the feature graphic. Duplicate last quarter’s layout, swap the screenshot and headline, and export a fresh PNG instead of leaving last year’s campaign on the listing.
Indie games and studio catalogs
Each title needs its own banner. Reuse a house layout, change character art and the game name, and keep type sizes consistent so a publisher page still feels like one studio.
Agencies shipping client Android apps
Hand clients a PNG that already matches Console. Edit copy on the canvas in a review call, export, and avoid a round trip through a full design suite for a single store banner.
Google Play Feature Graphic questions
Related tools
Build your Google Play Feature Graphic
Open the 1024 × 500 editor on this page, place your screenshot, and download a PNG for Play Console.