The Google Play feature graphic is exactly 1024×500 pixels (a 2:1 banner), saved as a PNG or JPEG in 24-bit color with no transparency. It's required — Play Console blocks you from publishing until you upload one. Keep your key visual and any text well inside the center, because Google overlays your app icon and name on it in some placements and crops the edges on others. Design it as a clean brand banner, not a screenshot dump.
What is the exact feature graphic size and format?
| Spec | Requirement | |------|-------------| | Dimensions | 1024×500 px (exact, 2:1) | | Format | PNG or JPEG | | Color | 24-bit, no transparency (no alpha channel) | | Required? | Yes — you can't publish without it |
There's no "minimum" or "recommended" version of this one. It's 1024×500 pixels, exactly, full stop. No aspect-ratio variants, no scaling tolerance. Upload anything else and Play Console rejects it.
The format choice is simple: PNG if your graphic is flat color, a logo, or text — it stays crisp. JPEG if it's photo-heavy, because it'll produce a smaller file. Either way, no transparency — flatten the background to a solid color or full-bleed image.
And here's the part newcomers miss: this asset is required to publish. Screenshots beyond the first two are optional, but the feature graphic isn't. Play Console will literally block your release until you've uploaded a 1024×500 graphic. I found this out the hard way the night before a launch, scrambling to make one in twenty minutes because I'd assumed it was optional like the promo video. It is not.
Google keeps the spec on the Play Console graphic assets help page alongside the screenshot and icon requirements — same page, worth bookmarking.
Where does the feature graphic actually appear?
The feature graphic is the wide banner that sits at the top of your store listing, above your screenshots. But it travels further than that. Google pulls it into:
- Featured and promotional placements — if your app gets editorial featuring, this is the art that represents it. - Play Store search cards on large screens, including Android TV and Android Auto, where the graphic does most of the visual work. - Category and collection pages in some layouts.
Here's the critical bit: in several of these placements, Google overlays your app icon and name directly on top of the feature graphic, and in others it crops the edges to fit a different aspect ratio. So the corners and edges of your 1024×500 canvas are danger zones. Anything important out there can get covered by the icon overlay or sliced off by a crop.
That's why a feature graphic is fundamentally different from a screenshot. A screenshot is a self-contained sales pitch. A feature graphic is a *backdrop* that has to survive having other UI stamped on top of it and chunks taken off the sides. Design it like a billboard that might get a logo slapped in the corner — because that's exactly what happens.
I didn't understand this on my first app and put my tagline flush against the left edge. On the phone listing it looked fine. In a featured collection, the icon overlay landed right on the first three words. Lesson learned: center everything, leave generous margins.
How do you design a feature graphic that converts?
Lead with your brand, not your UI. The most common mistake is treating the feature graphic like a screenshot — cramming in tiny device frames and dense interface. At banner scale that all turns to noise. Use your logo, one strong key visual or illustration, and a short tagline. Big, simple, confident.
Keep text to a handful of words. "Track every workout." "Split bills, stay friends." Three to six words, large, high contrast. If someone has to lean in to read it, it's too small for the placements where this graphic shrinks.
Respect the safe zone. Keep your logo, tagline, and key visual inside the central area — leave at least 10-15% margin on every side. That's your insurance against the icon overlay and the edge crops. Treat the outer band as decorative background only.
Match it to the rest of your listing. Your feature graphic, your screenshot backgrounds, and your icon should share a palette and a mood. When all three line up, the listing reads as a real, considered product. When they clash, it reads as thrown together. The simplest way to keep them consistent is to design them together in one tool — I build the feature graphic and frame the screenshots in the same place so the colors and type stay locked across all of them. You can do that in the PlayMockUp studio, where the same background and palette carry across every asset you export.
Don't repeat your app name as the only text. Google already overlays your name in some placements, so if your tagline *is* just the app name, you're being redundant. Say something about the benefit instead.
One more practical note: because Google crops this graphic to different ratios in different spots, preview it cropped. Put a mental box around the center 60% and make sure the graphic still works if everything outside that box vanishes. Apple's listings work differently — there's no feature-graphic equivalent — but the broader cross-store thinking is in App Store vs Play Store screenshots if you're shipping to both.
Feature graphic vs screenshots — what's the difference?
Screenshots are your detailed sales pitch. There are up to eight of them, they live inside the listing, they each make a specific claim about a feature or benefit, and they're shown at a consistent portrait size that nobody overlays anything on. You design them to be read one by one as someone swipes through.
The feature graphic is a single wide banner that sets the tone before anyone reads a screenshot. It's the first impression, it can have your icon and name stamped on it, and it gets cropped to fit various placements. You design it to work as a backdrop, not as a standalone argument.
Here's the practical split:
- Screenshots → specific, captioned, detailed, portrait, never overlaid. - Feature graphic → broad, branded, minimal text, landscape 2:1, possibly overlaid and cropped.
The mistake is designing your feature graphic *as* a screenshot — shrinking a phone frame and your headline into the banner. At 1024×500, and especially when it crops down for a TV card or a featured slot, that detail collapses into mush. Go the other way: make the feature graphic bold and sparse, and let the screenshots carry the detailed selling.
If you want to nail both in one sitting, I keep a consistent device frame and background across the screenshots and echo the same palette in the feature graphic. Browse the device frame library to pick the frame your screenshots will use, then carry that color story into the banner so the whole listing feels like one piece. For the full breakdown of the screenshot side, the rules I follow are in how to make app screenshots that get downloads.
What feature graphic mistakes should you avoid?
Wrong dimensions. It's 1024×500, exactly. Not 1024×512, not 1280×720. Get one pixel off and Play Console rejects it. Set your canvas to the exact size before you start so you're never resizing a finished design.
Transparency. The feature graphic needs to be fully opaque, 24-bit, no alpha channel. A transparent PNG either gets rejected or fills with an unpredictable background. Flatten it.
Important content near the edges. Edges and corners get cropped and overlaid. Keep your logo, tagline, and key visual centered with a comfortable margin so nothing critical lands in the danger zone.
Too much text. This is a banner seen at a glance and often shrunk small. A paragraph of features is unreadable. Three to six big words, maximum.
Treating it like a screenshot. Tiny device frames and dense UI don't survive at banner scale. Lead with brand and one key visual instead.
Letting it clash with the listing. A neon feature graphic on top of pastel screenshots reads as two different apps. Keep the icon, feature graphic, and screenshots on one palette and one mood. The reliable way to enforce that is to build them in the same place with the same color settings — frame your screenshots and design the banner together in the PlayMockUp studio so the whole listing ships as one coherent set instead of three mismatched assets.
Frequently asked questions
What is the Google Play feature graphic size?
Exactly 1024×500 pixels, a 2:1 banner, with no scaling tolerance or aspect-ratio variants. Save it as a PNG or JPEG in 24-bit color with no transparency. Anything other than 1024×500 gets rejected by Play Console.
Is the feature graphic required to publish on Google Play?
Yes. Unlike screenshots beyond the minimum two, the feature graphic is mandatory — Play Console blocks your release until you upload a 1024×500 graphic. It appears at the top of your listing and in featured and promotional placements, so it's not optional and shouldn't be an afterthought.
What's the difference between a feature graphic and a screenshot?
A feature graphic is a single 1024×500 brand banner that sets the tone and can have your icon and name overlaid on it, while screenshots are up to eight detailed portrait images that each make a specific sales point. Design the feature graphic bold and minimal, and let the screenshots carry the detail. You can build both with a matching palette in the [PlayMockUp studio](/create).
Can I put text on my feature graphic?
Yes, but keep it to three to six large, high-contrast words and place them in the center, away from the edges. Google crops the graphic in some placements and overlays your app icon and name in others, so text near the edges can get cut off or covered. A short benefit-focused tagline works far better than a dense paragraph.
Should the feature graphic match my screenshots?
Definitely. Your icon, feature graphic, and screenshots should share one palette and one mood so the whole listing reads as a single considered product. When they clash, the page looks thrown together. Designing them in the same tool with the same background, like the [device frame library](/frames) and studio, keeps everything aligned as you iterate.
Can a feature graphic have a transparent background?
No. The feature graphic must be fully opaque, 24-bit, with no alpha channel. A transparent file either gets rejected by Play Console or fills with an unpredictable background color. Flatten your design onto a solid color or a full-bleed image before exporting.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.