Aegis vs Bitwarden vs Google Authenticator: Which 2FA App to Install
Four Android authenticator apps compared on how they store TOTP secrets, whether backups are encrypted, and what happens to your codes when the phone dies.

Every authenticator app for Android generates the same six digits from the same secret. What separates them is what happens the day your phone dies, gets stolen, or ends up in a river.
That's the whole decision. Aegis Authenticator, Bitwarden Authenticator, Google Authenticator and Ente Auth all produce valid TOTP codes for the same accounts. They differ in where the seeds live, whether a backup exists by default, and whether that backup is encrypted with something only you know.
Catalog
The four apps side by side
App | Price | Default backup | Encrypted backup | Sync |
|---|---|---|---|---|
Aegis Authenticator | Free, open source | Manual, plus scheduled local backups | Yes, password-protected export | No cloud sync |
Bitwarden Authenticator | Free | Device cloud backup | Encrypted by your Google or iCloud backup | Optional, with a Bitwarden vault |
Google Authenticator | Free | Google Account sync | Encrypted by Google, no user password | Yes, one Google Account |
Ente Auth | Free, open source | End-to-end encrypted cloud backup | Yes, your account password | Yes, across platforms |
What backup actually means for TOTP
A TOTP secret is a long string that both you and the service know. The six-digit code is just that string plus the current time, run through an algorithm. If you lose the string, you lose the proof of who owns the account, and most services won't restore it for you.
That makes the export file the most valuable thing on your phone. It's also the most dangerous. Every app here can export as a QR code or a file, and a QR code is a bearer token: whoever scans it gets working codes, with no password prompt.
So the useful question isn't "does this app support backup". It's "does it support a backup I can open in two years, on a different phone, without the original app". A plaintext JSON file fails that test in a different way than a forgotten password does.
How each app stores the seeds
Aegis keeps everything in one vault file encrypted with AES-256-GCM, unlocked by a password run through scrypt or by biometrics through the Android keystore. The file isn't synced anywhere. You export it, or you let the app write automatic backups to a folder you choose.
Bitwarden Authenticator is more surprising. Its documentation states that keys and metadata sit in a local unencrypted database on the device, and that the app relies on your phone's cloud backup (Google One or iCloud) to protect it. The OS backup is encrypted, but the app itself doesn't add a layer.
Google Authenticator keeps codes in your Google Account when sync is on. Google's help page says codes are encrypted in transit and at rest across its products, which is true and also not the same as a backup only you can open. There's no separate backup password.
Ente Auth encrypts before syncing, so the server holds ciphertext and your account password does the work. The project says its cryptography has been externally audited, and you can run it without an account if you prefer to keep everything local.
Google Authenticator's cloud sync, in Google's own words
Google added account sync in 2023, and the details matter more than the headline. Per Google's help page, sync requires version 6.0 or newer on Android and works by signing in to your Google Account. Sign in on a new device and the codes arrive automatically.
Sync is optional. If you tap Use without an account, Google's page says codes are removed from all your Google Accounts and stored on the device only, which also means they won't appear on your other devices. That's the setting to pick if you don't want your second factor living next to your first one.
Manual transfer still exists: Menu → Transfer codes → Export codes on the old phone creates a QR code, and Import codes on the new phone scans it. If you have many accounts, the old phone may generate more than one QR code, so the transfer takes a few passes.
Two smaller changes are worth knowing. Google Authenticator 7.0 removed the app's own time correction setting, so codes now depend entirely on your phone's clock. And the app requires Android 6.0 or newer, which rules out very old handsets.
Aegis Authenticator
The one for people who don't trust a cloud
Aegis is free, open source, and built around a single encrypted vault. It supports HOTP and TOTP, groups entries, searches by issuer, and blocks screenshots by default so a code can't be captured by another app.
Its import list is the widest here: 2FAS, Authenticator Plus, Authy, andOTP, FreeOTP, Google Authenticator, Microsoft Authenticator, plain text, Steam and WinAuth. Some of those need root access, which the project states openly rather than hiding in a wiki.
Export comes in two flavours, plaintext and encrypted, and automatic backups can write the encrypted vault to a folder you choose. If that folder is on a synced drive, you get cloud backup without giving any company the key.
A secure 2-step authenticator to manage your one-time passwords
Bitwarden Authenticator
Convenient if you already pay for Bitwarden
Bitwarden's standalone authenticator is free, requires Android 9 or newer, and generates 5 to 10 digit codes with SHA-1 by default on a 30-second rotation. It can sync codes with a Bitwarden vault if you use both apps, which is handy and also a single point of failure if that vault is the account you're protecting.
Bitwarden's own documentation recommends keeping the code for your Bitwarden account as a local code, not a synced one, for exactly that reason.
The storage detail is the one to read twice. The app keeps seeds in a local unencrypted database and leans on the device backup system for copies. You can also export the data yourself, and biometric login keeps casual snooping out. It's a reasonable design for a phone-only app, and a weaker one than Aegis if someone gets physical access to an unlocked device.
TOTP inside the main Bitwarden password manager is a Premium feature at $19.80 a year. The standalone authenticator app is free.
Google Authenticator
The default, and the easiest to inherit
Google Authenticator is the app most services assume you have, the one QR codes are tested against, and the one that syncs without you thinking about it. It's a 4.5 MB install, the smallest here, and it does one thing on screen: a list of codes with a countdown ring.
The trade is control. There's no password-protected export, no local vault file, and no way to keep an encrypted backup that Google can't read. If you want the codes off Google's servers, your option is to use the app without an account, which puts them on one device with no backup at all.
For a lot of people that's acceptable. For anyone who has been locked out of a Google account, it's the reason to look at the other three.
Google Authenticator is a two-step verification app for protecting account sign-ins.
Ente Auth
The cross-platform option with encryption on by default
Ente Auth is free, open source under AGPL-3.0, and syncs codes across Android, iOS, desktop and web with end-to-end encryption. The encryption happens before anything leaves the device, and the backup is only as openable as your account password.
It also runs offline and without an account, which is unusual for a sync-first app. You can import by scanning a QR code, entering a secret manually, or bulk importing from another authenticator, and the project says you can export your data, so there's no lock-in.
The Android download is served as a 54.7 MB XAPK, much larger than Google's 4.5 MB, because it bundles more than one architecture. That's a storage cost, not a reliability one.
Cross Platform, Private, Open Source Two Factor Authenticator App
Moving codes without locking yourself out
The order of operations matters more than the app you pick. Do it wrong and you find out at the login screen of your bank.
- Install the new authenticator and add one test account from a service you can afford to fix, not your email.
- Log in with the new app while the old one is still installed. Both generate the same codes, so nothing breaks yet.
- Export from the old app only after the test works. For Google Authenticator, that's Menu → Transfer codes → Export codes.
- Import into the new app, then check the countdown and code match before you close the export screen.
- Delete the old app's entries, then uninstall it.
- Store the encrypted export file and its password in two different places.
Two failure modes are common. The first is a plaintext export left in Downloads, which is a full account takeover waiting for any app with storage access. The second is an encrypted export whose password lives only in the head of the person who made it.
A third one catches people after a phone replacement: a clock that's off by more than 30 seconds produces invalid codes, and since Google Authenticator 7.0 there's no in-app time correction to fix it. Set the phone to automatic time before you blame the app.
Which one to install
If you want | Install |
|---|---|
The strongest local vault and encrypted exports | Aegis Authenticator |
Codes inside the password manager you already pay for | Bitwarden Authenticator |
Zero setup and sync that just happens | Google Authenticator |
Encrypted sync across phone, laptop and browser | Ente Auth |
No account, no cloud, no company | Aegis Authenticator |
The honest costs
Aegis Authenticator
- Encrypted vault and encrypted exports
- Widest import list of the four
- No cloud sync at all
- You have to remember to back it up
Bitwarden Authenticator
- Free and clean, with optional vault sync
- Biometric lock on the app
- Seeds sit in a local unencrypted database
- Ties convenience to your Bitwarden account
Google Authenticator
- Smallest install and the most familiar
- Sync across devices with one account
- No user-controlled backup password
- Removed its own time correction in 7.0
Ente Auth
- End-to-end encrypted cloud backup
- Works offline and without an account
- Largest download of the four
- Newer, with a smaller support footprint
FAQs
- Is a TOTP backup safe to store in cloud storage?
- Only if it's encrypted with a password you keep somewhere else. A plaintext JSON export in Google Drive is a full set of second factors for anyone who gets into that account.
- Does Google Authenticator back up to my Google Account automatically?
- Yes, once you sign in. Google's help page says codes sync to the account and are encrypted in transit and at rest, and you can switch to "Use without an account" to keep them on one device instead.
- Can I use two authenticator apps at once?
- Yes. Add the same secret to both and both will generate valid codes. Keep the old app installed until you've logged in once with the new one.
- What if I lose my phone and have no backup?
- You'll use each service's recovery codes or account recovery process, one service at a time. That's why the export step matters before the phone is lost, not after.
Pick the app whose failure mode you can live with. Aegis fails when you forget to back up. Google Authenticator fails when you lose access to the Google account. Ente fails when you forget its password. Bitwarden fails when the phone is unlocked in the wrong hands. None of those is hypothetical, and the one you choose should be the one you'd rather troubleshoot at 2am.