If you just needed the number, it's above: 1024 × 500 px. There is no tolerance and no alternate aspect ratio — a single pixel off (1025 × 500, 1024 × 499) and Play Console rejects the asset at upload. The rest of this guide covers the format rules, the safe zone most developers get wrong, where the graphic actually shows up, and the specific reasons Google rejects it in review.
The feature graphic is a different asset from your Play Store screenshots: it's a single banner, not a 9:16 screen capture. Export at the exact size rather than scaling something close to it.
The Exact Specs
| Property | Requirement |
|---|---|
| Dimensions | Exactly 1024 × 500 px (2:1) — no other size accepted |
| File format | PNG (24-bit) or JPEG |
| Color mode | RGB — CMYK files are rejected |
| Transparency | Not allowed — no alpha channel |
| Required? | Yes — every Play Store listing must have one to publish |
Where the Feature Graphic Appears
This is the most-seen marketing surface for your app, which is why it matters more than its "it's just a banner" reputation suggests. Google Play uses it:
- At the top of your store listing, above your screenshots
- In editorial placements like Apps We Love and Editor’s Choice
- In promotional sections and search cards across Google Play
- On Android TV and Android Auto store surfaces, where it’s often the primary visual
In several of these placements, Google overlays a centered play button and shows your app icon and name alongside the graphic — which is exactly why the safe zone below matters.
The Safe Zone (the part most people get wrong)
Google can crop the outer edges of the feature graphic depending on the surface, and it overlays a centered play button on listings with a video. Two rules follow:
- • Keep critical content inside a centered ~924 × 400 px area — the outer ~50 px on each side can be cropped.
- • Don't put text or your logo directly behind the center, where the play-button overlay sits (~75 px wide, centered).
The graphics that perform best are simple: a brand logo (not the app name — that already shows below the graphic), one short value proposition of three to six words, and high contrast so it reads at thumbnail size. Resist cramming three screenshots and a paragraph in here — featured placements consistently test better with a single hero idea.
Why Feature Graphics Get Rejected
- 1Wrong dimensions. Anything other than 1024 × 500. This is the number-one cause — Play Console rejects the asset at upload.
- 2Transparency. A PNG with an alpha channel is rejected. Flatten it onto a solid or image background before export.
- 3CMYK color. Print-oriented files in CMYK fail. Convert to RGB before exporting.
- 4Off-brand or misleading content. The graphic must not imply features or content the app does not have.
- 5Text clipped by overlays. Technically accepted, but copy that runs under the centered play button or into the cropped edges looks broken in placement — a soft failure that hurts conversion even when review passes.
Feature Graphic Best Practices
- Export at exactly 1024 × 500 — never scale something "close" up or down to fit
- Keep critical content inside a centered ~924 × 400 px safe zone; the outer ~50 px each side can be cropped
- Avoid placing text or your logo directly behind the center, where the play-button overlay sits on listings with a video
- Use your brand logo, not the app name — the name already shows below the graphic
- One short value proposition (3–6 words) reads better than a cluttered banner
- High contrast so it stays legible at thumbnail size in search and featured placements
- Match the visual language of your screenshots so the listing feels cohesive top to bottom
How to Make One Fast
You have three realistic paths. Design from scratch in Figma, Canva, or Photoshop at exactly 1024 × 500 px for full control (slowest). Reuse your screenshot system so the banner shares the same background and type as your screens. Or use a generator that outputs the asset at the exact spec.
SnapMonk outputs the feature graphic at the exact 1024 × 500 spec alongside your full screenshot set from a single design, so the banner and the screenshots match and every asset is the right size on export — no manual resizing, no rejected uploads.
Frequently Asked Questions
What is the Google Play feature graphic size in 2026?
The feature graphic must be exactly 1024 × 500 pixels — a 2:1 banner. There is no tolerance and no alternate aspect ratio; anything else is rejected at upload.
Is the feature graphic required in 2026?
Yes. Play Console blocks publishing until you upload a 1024 × 500 feature graphic. Unlike screenshots beyond the minimum of two, the feature graphic is mandatory on every listing.
Can the Google Play feature graphic have transparency?
No. The feature graphic cannot have an alpha channel. Use a solid or image background and flatten it before export, or the upload is rejected.
What file format should the feature graphic be?
A 24-bit PNG or a JPEG, in RGB color. CMYK files are rejected. PNG is the safer choice for crisp logos and type.
Can I put text on the Google Play feature graphic?
Yes, but keep it minimal and inside the centered ~924 × 400 px safe zone. Avoid placing copy behind the center play-button overlay, and remember the outer ~50 px on each side can be cropped in some placements.
What is the difference between the feature graphic and a screenshot?
The feature graphic is a single 1024 × 500 banner used for featuring and the top of your listing. Screenshots are separate 9:16 images (typically 1080 × 1920) that show your actual app UI. They are different assets with different specs.