Google Play Feature Graphic: Size, Specs & Design Tips
Every Google Play listing has one asset that Apple doesn't: the feature graphic. It's the wide banner that sits at the top of your store page, powers your app's appearance in search and category browsing, and becomes the backdrop for your promo video if you add one. Get it wrong and your listing looks half-finished; get it right and it does real work pulling installs.
The quick answer: a Google Play feature graphic must be exactly 1024 × 500 pixels, saved as a PNG or JPEG under 15 MB, with no transparency. That's the only accepted size. This guide covers the full spec, the safe zone that trips people up, and how to design one that actually converts.
Google Play feature graphic size and specs
| Spec |
Requirement |
| Dimensions |
1024 × 500 pixels (exact — only size accepted) |
| Aspect ratio |
2.048 : 1 (landscape) |
| File format |
PNG or JPEG (24-bit; no alpha / transparency) |
| Max file size |
15 MB |
| Color space |
RGB |
| Required? |
Yes — mandatory to publish |
| Where it appears |
Top of listing, search results, category pages, promo-video backdrop |
There is no "large" or "small" version — you upload one 1024 × 500 image and Google resizes it for each placement. Because it gets scaled down and cropped, design for legibility at small sizes, not just full width.
The safe zone (the mistake almost everyone makes)
Google does not display your full 1024 × 500 image everywhere. It crops the graphic for different surfaces, and when a user taps to watch your promo video, a play button is overlaid dead center on top of the graphic. On smaller layouts, the sides can get trimmed.
The rule: keep your logo, app name, and any critical text within the centered safe zone — roughly the middle 80% horizontally and clear of the exact center where the play button lands. Treat the outer edges as decorative bleed only. If your brand name sits in a bottom corner, expect it to disappear on some devices.
Format and content rules that get listings rejected
Google's Developer Program Policies apply to the feature graphic just like screenshots. Common rejection triggers:
- No transparency. A flat, fully opaque image only. Alpha channels cause upload errors or a broken-looking banner.
- No device frames or "screenshot-in-a-frame" imagery. Google specifically discourages using phone frames or making the feature graphic look like a screenshot. Use it as a brand banner, not a mockup.
- No store badges or ratings. Don't include "Editor's Choice," star ratings, "#1 app," or "Download on Google Play" — these imply endorsements you may not have.
- No misleading or borderline content. It must reflect the actual app, and the content rating rules apply.
- No excessive text. Google favors visual, brand-led graphics over text-heavy banners.
Design tips for a feature graphic that converts
The feature graphic isn't a screenshot — it's a billboard. Its job is to communicate what your app is and why it's worth a tap in under a second.
- Lead with your logo and a short value line. Your app icon or wordmark plus three to five words of promise ("Split bills with friends") is plenty. Centered.
- Use a strong background, not a busy one. A solid brand color or a simple gradient reads far better at thumbnail size than a detailed photo. High contrast between background and text is non-negotiable.
- Match your screenshots. The feature graphic should feel like the same family as your Google Play screenshots — same colors, same font, same tone. A cohesive listing looks more trustworthy.
- Design for the crop. Compose so the center holds up on its own, because that's the part guaranteed to show everywhere.
- Test it small. Shrink your export to a few hundred pixels wide and check that the text is still readable. If it isn't, simplify.
How to make a feature graphic without a designer
You don't need Photoshop or a design hire for a 1024 × 500 banner. The App Store screenshot generator in Adalo Studio is a free-form canvas — set the canvas to Google Play's feature-graphic size, drop in your icon, add a headline in any Google Font, apply a background or gradient, and export a flat PNG at exactly 1024 × 500 with no transparency. It handles both your feature graphic and your phone screenshots in one place, so the whole listing stays visually consistent.
For the full set of Play and iOS asset dimensions in one table, keep the app store screenshot sizes reference open. And if you're comparing tools before you commit, we break down the options in the best app store screenshot generators.
Feature graphic vs. the rest of your Play assets
It helps to see where the feature graphic fits among Google Play's required visuals:
| Asset |
Size |
Required? |
Purpose |
| App icon |
512 × 512 |
Yes |
Identity across the store and device |
| Feature graphic |
1024 × 500 |
Yes |
Banner at top of listing + video backdrop |
| Phone screenshots |
1080 × 1920 (min. 2) |
Yes |
Show the app in use |
| Promo video |
YouTube URL |
Optional |
Plays over the feature graphic |
| 7-inch / 10-inch tablet screenshots |
Varies |
Only if you target tablets |
Tablet listing quality |
The feature graphic and at least two phone screenshots are the visual assets you cannot publish without.
Feature graphic vs. iOS: what Apple makers should know
If you're publishing to both stores, note that the feature graphic is a Google-only asset — the App Store has no equivalent banner. Apple leans entirely on your app icon, screenshots, and optional app preview video for the top of your listing. That means you'll design one extra asset for Google Play that has no iOS counterpart, and you can't repurpose an iOS asset to fill it.
The practical upshot: budget for the feature graphic as its own deliverable when planning an Android launch, and don't try to crop a screenshot down to 1024 × 500. A cropped screenshot violates Google's "no screenshot-in-a-frame" guidance and almost always reads as an afterthought. Design it as a purpose-built banner from the start.
How Google uses your feature graphic
Understanding where the graphic actually appears helps you design it well:
- Top of your store listing — full-width on the listing page, above your short description.
- Promo video backdrop — if you add a YouTube promo video, the feature graphic becomes the thumbnail with a play button overlaid in the center.
- Search and browse surfaces — Google may surface a cropped version in featured placements, category pages, and collections.
- Editorial and promotional placements — if Google features your app, a clean, on-brand feature graphic gives you a better shot at looking the part.
Because the same 1024 × 500 file is reused across all of these at different crops and sizes, the safest design is one that's legible small, centered, and brand-led. That single image is doing more work across the store than any other visual you upload except the icon.
Quick checklist
- [ ] Exactly 1024 × 500 pixels
- [ ] PNG or JPEG, no transparency, under 15 MB
- [ ] Logo and text centered, inside the safe zone
- [ ] No device frames, store badges, or star ratings
- [ ] High contrast, readable at thumbnail size
- [ ] Visually matches your screenshots and brand
- [ ] Center holds up on its own (play-button overlay)
Frequently asked questions
What size is a Google Play feature graphic?
The Google Play feature graphic is exactly 1024 x 500 pixels. It must be a PNG or JPEG under 15 MB with no transparency and no alpha channel. There is only one accepted size — Google resizes it for different placements.
Is the feature graphic required to publish on Google Play?
Yes. Google Play requires a 1024 x 500 feature graphic before you can publish your app, in addition to an icon and at least two phone screenshots. Without it, your store listing stays incomplete and you cannot roll out to production.
Should I put text on my feature graphic?
Keep text minimal and centered. Google crops and overlays the graphic differently across placements — including behind a play button when you add a promo video — so keep your logo and any words in the middle and avoid important content near the edges.
Tools mentioned in this guide:
App Store Screenshot Generator,
App Privacy Policy Generator.