Google Wallet image & format requirements
Updated June 29, 2026
Google Wallet handles images in a way that catches people out, because it's the opposite of how Apple does it. Understanding it explains most "my logo is missing" reports on Google passes.
Google loads images by URL
Apple embeds images inside the pass file. Google does not. Instead, when a pass is saved, Google reaches out and fetches your images from a public URL. The two images that matter on a Google pass are:
- the logo, and
- the hero image (the wide banner across the top).
Passmint hosts both of these for you at public, secure URLs, so there's nothing to configure. But the consequences of the URL model are worth knowing.
A URL Google can't load means rejection
If Google tries to fetch an image and the URL doesn't return a valid image, it can reject the entire pass. This is why a Google pass occasionally appears with no logo, or fails to save right after issuing: the image wasn't ready yet when the pass was created.
Passmint guards against this by only referencing an image once the file actually exists. If you do see a missing image on a freshly issued Google pass, give it a moment for processing to finish and re-save, and the image will appear.
Upload your logo and hero image in the designer before issuing live Google passes, and confirm they show in the preview. Images must be reachable over HTTPS, which Passmint handles automatically for hosted images.
Practical guidance
- Use a transparent-background PNG for your logo so it sits cleanly on the card.
- The hero image is wide and short. Design artwork that still reads when cropped to a banner, and keep important content away from the edges.
- For sizes shared across both wallets, see adding images to a pass.