Choosing an authenticator app: phone, desktop or security key
Where the secrets behind your one-time codes live decides how safe they are. What to ask before you pick an authenticator, and where a desktop app fits.
An authenticator app shows a six-digit code that changes every 30 seconds. The code is computed from a secret that you and the website share when you scan the QR code, plus the current time. Everything that matters about an authenticator comes down to one question: where does that secret live, and who can read it?
Four places the secret can live
| Option | Where the secrets are | If you lose the device | Worth knowing |
|---|---|---|---|
| Phone app, local only | On the phone, encrypted | Codes are gone unless you made a backup | Private, but the backup is up to you |
| Phone app with cloud sync | On the phone and on the provider's servers | You get them back from the account | Convenient; your account and the provider become part of your security |
| Desktop app | In an encrypted file on the computer | Gone unless you made a backup | Handy when you work at the computer; not with you on the street |
| Hardware security key (FIDO2) | Inside the key, which cannot be copied out | Use a spare key; many sites allow two | Resists phishing, which a typed code cannot |
What to ask before you choose
- Can I get my codes out? A format you can export means you are never locked in. Test an export before you rely on the app.
- Who holds the key to the backup? A backup encrypted with a password only you know is different from one the provider can read.
- Does it work offline? Codes are computed from the clock, so they should not need the internet.
- Can I look inside? Open source, source-available with reviews, or a closed product: each asks for a different amount of trust.
- What happens when I lose the device? Answer this before it happens. Keep recovery codes somewhere offline.
The limit of any one-time code
A code typed into a page can be typed into a fake page too. If a site offers a passkey or a security key, prefer it: the device checks the site's address, so a look-alike page gets nothing. See Passkeys: the beginning of the end of passwords. Keep one-time codes for the places that offer nothing better, and for a second factor as a fallback.
Where MasterSafe Authenticator fits
MasterSafe Authenticator is my desktop app for Windows and Linux. The secrets and passwords sit in an encrypted file on your computer, protected by a master password, Windows Hello or a FIDO2 key. There is no account and no cloud; it talks to the network only for the optional features you turn on. It reads exports from KeePass, Bitwarden, 1Password, Proton Pass, Aegis, 2FAS and Google Authenticator, and makes encrypted backups. Releases are signed, with post-quantum signatures.
It has limits you should know before using it:
- It is a desktop app. There is no phone app and no macOS version, so it complements a phone authenticator and does not replace it.
- It is source-available, not open source: you can read and build it, with the limits of its licence (opens in a new tab).
- It is a young project by one person, written with an AI assistant. Do not take my word for its safety: look at the signed releases, the tests and the review notes in the repository.
Download it from the releases page (opens in a new tab) and check the signature as the article above explains.
To see MasterSafe in use, follow the guided tour, with pictures of every step.