Google Play App Badge Download Guide
Official Google Play Badge Download
Get the google play app badge from Google’s Partner Marketing Hub. Open {site}, find the brand and marketing resources area, and select Google Play badges. Google identifies this hub as the official source for current, high-resolution, localized badge assets.
Choose the “Get it on Google Play” badge when the purpose is to send someone to an app’s published store listing. The separate pre-registration badge is only for a pre-registration campaign. Do not substitute the Google Play icon, wordmark, or a homemade google play app store badge. Google says the badge, rather than a Google Play lockup, should be used when directing people to content on Google Play.
Before using a google play badge download found elsewhere, check that the file came from the Partner Marketing Hub and matches the current artwork shown there. An image copied from another website, an old project, or an image-search result may be outdated or modified.
Choose the Right Badge Format
Download the asset package provided for the selected language. Use an official raster image, such as a PNG, when the badge will appear at a known size on a website, in an email, or in another digital layout. Select a file with enough pixels for the displayed size and for higher-density screens.
If the official package includes a scalable or vector asset, use that version for print, large-format work, or a layout that may be resized. A vector remains sharp at different dimensions. Keep the original proportions during export.
Do not recreate the badge by typing its wording or combining the Play icon with text. Do not convert a small screenshot into a larger file; its dimensions may increase, but its detail will not. Keep the downloaded master file so future exports can be made from an approved source.
Link the Badge to a Google Play App
The badge should lead directly to the correct app’s Google Play Store listing. Google’s linking guidance says a direct store-listing link is built with the app’s fully qualified package name. That package name is declared in the app manifest and is also visible in Play Console.
- Open the app’s published listing in Google Play.
- Confirm the app name, developer name, icon, and package name.
- Copy the direct listing destination supplied for that app.
- Apply that destination to the badge in the website or campaign editor.
- Test the badge on both a phone and a desktop browser.
A search-results page or general developer page is less precise and can send visitors toward the wrong app. Test again after publishing. The badge should open the intended listing without an error, an unexpected redirect, or a request for a file download.
Badge Size, Spacing, and Placement
Google’s current minimum digital height is 28 pixels. For print, the minimum height is 0.3 inches, or 7.6 millimeters. These are minimums, not target sizes for every layout. Make the badge large enough for its wording to remain easy to read on the actual screen or printed piece.
Leave clear space on every side equal to at least one-quarter of the badge’s height. Keep text, borders, logos, and other controls outside that area. When the badge appears beside other application-store badges, Google requires its badge to be the same size or larger.
Place it on a solid background or a simple image with enough contrast. Avoid a busy photograph behind it. Put it near the app-related message or action it supports, and make sure readers can recognize it as a tappable element. Do not crowd it into a footer or shrink it until the words become difficult to read.
Language and Regional Versions
Use the localized badge that matches the language of the page, advertisement, or other campaign. Google provides approved versions for a variety of languages through its badge resources. For a United States English page, select the English version intended for that market.
Do not translate the badge wording yourself, place translated words over the artwork, or mix a badge from one language with replacement text from another. If one campaign has several language versions, download the approved asset for each version and keep the app destination consistent where the same listing is intended.
Check the full locale, not only the language name, when regional choices are offered. Also review the localized file at its final size because scripts and phrase lengths differ. If the needed version is not available, consult Google’s current brand resources instead of creating an unofficial translation.
Common Badge Usage Problems
Altered artwork: Do not remove, rearrange, redraw, crop, or add elements. Use the complete official badge.
Incorrect colors: Do not recolor the badge to match a page theme. Use the approved colors in the downloaded asset.
Stretched image: Resize proportionally. If the icon or wording looks wider or taller than the original, restore the original aspect ratio.
Unofficial wording: Use the wording built into the approved localized file. Do not create a “download on the Google Play Store badge” or other variation from plain text.
Broken link: Recheck the app’s package name and published listing. Test the linked google play download badge after every page migration or campaign update.
Low resolution: Replace screenshots, thumbnails, and enlarged small files with a current high-resolution asset from Google.
A final review should confirm the source, language, proportions, minimum size, clear space, contrast, and destination. Re-download the google play store badge when Google updates its artwork rather than continuing to reuse an old saved copy.