Where Does Bitwarden Authenticator Store Codes?
Bitwarden Authenticator keeps TOTP codes device-local with JSON exports. Vault-synced codes export separately.
Last updated
Bitwarden Authenticator defaults to device-local TOTP with JSON exports as the exit. Vault-synced codes branch to separate exports through the password manager. Packages verify on both stores.
Raw database names come from security research rather than vendor pages. OS backups cover restores with biometric gates. Quote exports plus packages while marking internals carefully.
Where Bitwarden Authenticator stores this, by platform
/data/data/com.bitwarden.authenticator
Private sandbox for the verified package with OS backup coverage. JSON exports carry otpauth strings per entry. Vault codes export apart.
Frequently asked questions
How do I back up Bitwarden Authenticator?
Export JSON or CSV through Settings Export with otpauth strings per entry. Local codes travel in that file while vault-synced codes need vault exports. Import accepts multiple authenticator formats.
Local versus vault codes?
They split local device codes from vault-synced ones with separate exports each. Password Manager integration syncs copies while standalone stays local. Quote per-side flows without mixing.
What are the Authenticator app IDs?
Through verified packages on both stores with sandboxed storage and OS backups. Raw database names come from security reports rather than vendor docs. Keychain and keystore bridge per OS.
Notice an outdated path? Let us know.