Every app published on Google Play must ship a feature graphic — a 1024×500 banner that Play Console demands before you can publish anything. Yet since Google's 2018 Play Store redesign, the asset effectively vanished from the listing page: unless you attach a promo video, the feature graphic almost never renders where developers can actually see it, and the one place it does appear prominently — as the video's cover image — gets a play button stamped over its center.

That combination — mandatory to publish, invisible on the page, partially covered when visible — is why the feature graphic is the most botched asset in Google Play optimization. Developers resize their app icon, paste in a screenshot collage, or bolt on "FREE INSTALL NOW" text (a direct policy violation), then move on. The data says that's expensive: swapping the feature graphic alone moves install conversion rate by 7–18 percent, according to TMS Outsource's analysis — comparable to changing your first screenshot.

This guide collects what Play Console's official documentation requires, what ASO research firms have measured, and the geometry you need to keep the banner eligible for the promotional surfaces where Google actually uses it.

Why a banner you never see still matters

Google's Play Console Help states it plainly: the feature graphic is used "to highlight and promote your app on Google Play and other Google promotional channels." Concretely, that asset surfaces in more places than most developers realize:

  • As the cover image for your preview video on the listing page — with a play button overlaid dead center
  • In large-format app collections, including ads, for apps
  • In recommended game groups featuring videos and screenshots, for games
  • In expanded organic search results on some device configurations
  • In brand search placements and external sharing contexts (link previews on social and messaging apps)

Google's research cited by Phiture — an ASO consultancy that analyzed 3,300 feature graphics across 33 Play Store categories and whose findings TMS Outsource summarizes — found that store visitors make download decisions in roughly seven seconds. The feature graphic, sitting above your screenshots whenever a video is present, carries a disproportionate share of that first impression.

There's also a featuring angle. Google Play's editorial and algorithmic surfaces rely on quality, relevance, and app-health signals, and AppTweak's featuring guide notes that Google's editors "look for clean visual design, cohesive storytelling, strong branding" — evaluating every app against four pillars: core value, user experience, technical quality, and privacy. A sloppy banner doesn't just look bad; it can quietly disqualify you from collections and recommendations built around your creative assets.

By the Numbers

  • 1024 × 500 px, exact — required feature graphic dimensions; Play Console rejects the file even one pixel off, with no auto-resize (Google Play Console Help)
  • JPEG or 24-bit PNG only, no alpha channel — transparency fails the upload even with correct dimensions (Google Play Console Help)
  • 1 MB maximum file size for the feature graphic per TMS Outsource's practical guide
  • 7 seconds — approximate time Play visitors take to make a download decision, from Phiture's analysis of 3,300 feature graphics across 33 categories (cited by TMS Outsource)
  • 7–18% install conversion movement attributed to swapping the feature graphic — comparable to changing the first screenshot (TMS Outsource)
  • ~96 × 96 px play button rendered dead-center when a promo video is attached — TMS Outsource's practical guidance; keep the center clear
  • 924 × 400 px recommended safe zone (50 px buffer on each edge of the canvas) before promotional-surface cropping bites — TMS Outsource guidance
  • 8.56% vs 16.15% — 2025 average US page-view-to-install conversion on the App Store vs Google Play respectively (AppTweak benchmark data)
  • +15–25% conversion lift associated with having a preview video, which turns the feature graphic into your video cover (Adapty's benchmark roundup)
  • 4 screenshots at 1080px+ (one 16:9 at 1920×1080) for apps, 3 landscape 16:9 screenshots for games — featuring-eligibility thresholds verified against Play Console Help by App Radar in July 2026

The exact spec, and where uploads die

Google's official requirements are short but unforgiving:

  1. Dimensions: exactly 1024 × 500 px. Not "up to," not proportional. A single-pixel deviation triggers rejection in Play Console.
  2. Format: JPEG or 24-bit PNG. The 24-bit part matters — 32-bit PNGs carry an alpha channel, and alpha fails the upload even when the dimensions are perfect. Flatten every layer and export with an opaque background.
  3. File size: 1 MB cap per TMS Outsource's guide; most 80–90% quality JPEGs land comfortably under it. If a PNG is flirting with the limit, recompress — TinyPNG or Squoosh will hold visual quality at this canvas size.

Two practical traps account for most rejected uploads: exporting from a design tool with "transparent background" left on, and designing on a different canvas size and rescaling at the end, which introduces sub-pixel artifacts. Set the canvas to 1024 × 500 before you place a single element — 72 DPI, RGB color mode.

One more spec quirk: the aspect ratio works out to about 2.048:1 — wider than 16:9, closer to a cinematic 2:1 banner. Designs ported from YouTube thumbnails or app screenshots almost always need recomposition, not just cropping.

Where the graphic actually appears — and what it has to do there

After the 2018 redesign, the feature graphic's primary display role is the cover for your promo video. Per Play Console Help, it's only shown on the listing page before your screenshots when a video is attached; with no video, it generally won't appear on your listing at all — but Google still requires it for editorial and promotional placements.

That gives the asset a doubled job when you do have a video, as Apptamin's analysis puts it: it must compel visitors to press play and simultaneously convey your value proposition to the visitors who won't. If your listing's most prominent visual is effectively a video billboard, treat the feature graphic like a poster, not like a fourth screenshot.

Which leads to the most common design failure. TMS Outsource and AppScreens both flag "tiny UI collage" as the killer mistake: pasting three miniature phone screens into a 1024×500 canvas produces a graphic that is unreadable at actual phone size. Google's own guidance says fine details "will not be visible on many phone screens."

Safe zones: 924 × 400 px and the play-button blind spot

Google crops and rescales the feature graphic per surface. The full canvas is only guaranteed on your listing; editorial and featured placements crop to aspect ratios ranging from 16:9 down to 4:3, slicing the unpredictable left and right edges.

The working geometry from TMS Outsource's guide:

  • Keep all critical content — logo, headline, focal visual — inside a centered 924 × 400 px box, leaving ~50 px of buffer on every edge. ("Centered" means centered on the full 1024 × 500 frame, not on the visible crop — a subtlety that has burned more than one shipped banner.)
  • With a promo video attached, treat the center ~96 × 96 px as off-limits for your logo or tagline; the play button renders there. Roblox's banner — logo placed clear of center, per Apptamin's example teardown — is a good model; Lords Mobile's, where the logo hides under the button, is the cautionary version.
  • Push background texture and decorative elements toward the edges; keep the focal point central. Google's Console Help warns that failure to respect focal-point and cutoff zones "may result in ineligibility to appear in these formats."

The content rules that double as policy

Play Console's content guidelines are where most developers trip, not the pixels. These are banned outright on feature graphics (and Google flags policy violations as capable of delaying review or triggering removal):

  • Performance and promotional language: "Best," "#1," "Top," "New," "Free," "Discount," "Sale," "Million Downloads"
  • Call-to-action text: "Download now," "Install now," "Try now"
  • Simulated ratings, fake notifications, or misleading performance claims
  • Google Play badges, the Android robot, other stores' assets, and third-party trademarked characters or logos without written permission
  • Time-bound content left past its window — the "Holiday Sale" banner still live in January is explicitly called out by Google as a review trigger

Design guidance worth following even though it's phrased as "highly recommended" rather than required:

  • Don't duplicate your app icon. The icon frequently appears beside the graphic; build brand elements that extend it instead of restating it.
  • Avoid pure white, pure black, and dark gray — they blend into Play Store surfaces.
  • Match your color theme across the graphic, the icon, and the app itself so users instantly associate them.
  • Localize visible text for important markets, checking text length and reading direction.
  • Write alt text, 140 characters or fewer, describing the important content — and skip "image of," per Console Help. Google explicitly ties alt text to visibility for assistive-technology users.

The featuring math: what actually gates promotion

The feature graphic is table stakes; the featuring thresholds sit one level up, and they're more quantitative than most developers assume. App Radar — which verified the specs against Play Console Help in July 2026 — reports that featuring eligibility is now tied to screenshot count and resolution, not just content quality:

  • Apps: at least 4 screenshots at 1080 px or higher, including one 16:9 landscape screenshot of at least 1920 × 1080 px
  • Games: at least 3 landscape 16:9 screenshots at 1920 × 1080 px or higher

Two screenshots publish an app; they do not feature it. And because Play's editors curate collections around visual quality — AppTweak documents that poor visuals "can disqualify an otherwise great app" — your banner and screenshots are evaluated as one system. On the conversion side, the same system compounds: Adapty's data associates preview videos with a 15–25% conversion lift, which makes your feature graphic (the video's face) a first-order lever, and AppTweak's 2025 benchmarks put average Play page-view conversion at 16.15% in the US — meaning a banner that stalls tap-through costs you downloads against a measurable baseline.

Test it, localize it, refresh it

Treat the feature graphic as a tested asset, not a formality:

  1. Run it through Store Listing Experiments. Google's built-in experiments accept graphic-asset variants, and Apptamin recommends testing the banner with Google Experiments or third-party platforms like SplitMetrics. Given the 7–18% swing TMS Outsource associates with banner swaps, this is among the highest-yield tests on a Play listing.
  2. Localize the headline, not just the screenshots. Google recommends localizing the graphic "as appropriate for different markets and languages" — re-verify text fit per language, since German and Japanese headlines rarely match English widths.
  3. Refresh on a cadence. Adapty's benchmark data shows top apps update screenshots 2–4 times per year, with games on Google Play updating visuals up to 8 times annually — and 57% of top games ran screenshot A/B tests at least twice in 2024. Extend that discipline to the banner, swapping seasonal variants before they go stale.

A practical build order

Set a 1024 × 500 canvas → place the focal visual and one short promise line → mask the 924 × 400 safe zone and (if applicable) the center play-button zone → check it at 50% zoom for legibility → confirm icon-complementarity and background color → strip the alpha channel, export under 1 MB, add alt text, upload.

If you'd rather not hand-build that geometry, ScreenCraft ships a dedicated Google Play feature graphic canvas at exactly 1024 × 500 alongside its screenshot editor, so the banner and screenshots share one styling system — and the localizing workflow covers 35+ locales if your experiments need market-specific variants. The point isn't the tool; it's that banner, video cover, and first screenshot should read as one designed system, because Google's editors and its seven-second skimmers both evaluate them that way.

Sources

  • Google Play Console Help — "Add preview assets to showcase your app" (requirements, usage, content guidelines)
  • TMS Outsource — "Google Play Feature Graphic Size & Requirements" (safe-zone geometry, file-size cap, Phiture data, conversion-swap stat)
  • AppTweak — "Average App Conversion Rate per Category [2025]" and "How to get your app featured" (CVR benchmarks, editorial criteria)
  • Adapty — "App Store & Google Play conversion rate benchmarks" (video lift, update cadence, testing rates)
  • App Radar — "Google Play screenshot sizes 2026" (featuring thresholds verified against Console Help, July 2026)
  • Apptamin — "Google Play Feature Graphic Examples and Best Practices" (placement behavior, example teardowns)

A note on the data: specs quoted from Play Console Help are official as of October 2026; conversion percentages and safe-zone figures come from third-party ASO research and represent their published analyses, not Google guarantees. Nothing here is legal advice for policy interpretation — when in doubt, the Console documentation and Google's Developer Program Policies are the authority.