Where Does Google Wallet Store Passes and Tickets?
Google Wallet passes are server records rendered by the app, not files. Manage them in the app; local data is a private cache.
Last updated
Google Wallet has no passes folder. Loyalty cards, tickets, boarding passes, and transit cards exist as records on Google servers. The app on your phone fetches and draws them on demand. Tapping Add to Google Wallet on an issuer site creates the server record, then the app shows it.
Local storage is only a private cache you cannot usefully browse, and some cards are pinned to a single device. Do your real management in the app: per-pass notification toggles, the Gmail auto-save setting, and removal from the pass details page. A new phone pulls everything back on sign-in except single-device cards.
Where Google Wallet stores this, by platform
/data/data/com.google.android.apps.walletnfcrel
Private cache, root only. Exact folder names may vary by version, so manage passes in the app instead of the filesystem. Single-device cards need a transfer flow rather than a file copy.
Frequently asked questions
Can I back up a Google Wallet pass as a file?
No. A pass is a row in Google servers that the Wallet app pulls each time it renders. Your issuer updates it with a PATCH and it changes on your phone by itself. There is no archive to copy, which surprises people coming from Apple pkpass files.
Why did a boarding pass stay after I deleted the email?
Open Wallet settings and look for the Gmail auto-save toggle. With it on, boarding passes and receipts from email stay in Wallet even after you delete the message. Turn it off if you prefer passes to vanish with the email.
Notice an outdated path? Let us know.