Where Does BlueWallet Store Wallets?
BlueWallet keeps wallets in encrypted app storage with per-wallet export. No user folder, backup flow inside.
Last updated
BlueWallet keeps wallets in private app storage on the phone. The store is encrypted on device with platform keychain integration, and no folder on shared storage holds anything spendable. Root browsing finds implementation details, not a supported backup route.
Recovery runs per wallet, not per app. Each on-chain wallet exports its seed words, multisig setups export coordination files, and Lightning wallets export pairing data. There is no single global backup file, so every wallet needs its own export. History CSVs record spending without restoring funds.
Where BlueWallet stores this, by platform
App-private storage (per-wallet export)
React Native encrypted storage, no user folder. Back up each wallet: seed words for on-chain, coordination files for multisig, lndhub pairing for Lightning. Optional app password encrypts storage with an unrecoverable password.
App sandbox (per-wallet export)
Same per-wallet model with Keychain-backed encryption. Private keys never leave the device except through your explicit export. Reinstalls start empty until each wallet imports.
Frequently asked questions
How do I back up BlueWallet properly?
Open each wallet and use its Export or Backup action: seed words for singlesig, coordination files for multisig, pairing QR for Lightning. One export per wallet, stored offline separately. No global file covers them all.
Can I copy BlueWallet data to a new phone?
Only through exports and re-imports per wallet. Private storage does not transfer and should not be copied by hand. Multisig needs every cosigner file; Lightning needs its pairing restored against a live hub.
Does the BlueWallet backup include history?
CSV exports include history without recovery power. Fund recovery comes from seeds and coordination files alone. Keep both kinds: seeds for money, CSVs for accounting.
Notice an outdated path? Let us know.