Home/Guides/Two-Factor Apps Compared: The Real Risk Is Losing the Phone

Two-Factor Apps Compared: The Real Risk Is Losing the Phone

Most comparisons of authenticator apps rank them by interface. The thing that actually costs people accounts is the recovery story, and almost nobody checks it before they need it.

Security & Privacy · Updated Oct 23, 2026

Every two-factor app generates the same six digits from the same standard. TOTP is TOTP. So when a comparison article tells you one app has a nicer list view than another, it is describing the least consequential difference between them.

The differences that matter are three: what happens when you lose the device, what happens when the app's vendor disappears, and whether the backup is something you can actually restore.

What TOTP protects against, and what it doesn't

A TOTP code stops the most common attack on your accounts: someone who has your password but not your phone. That is worth a lot, because password reuse and credential dumps are how most accounts fall over.

It does not stop real-time phishing. If you type your password and a code into a lookalike login page, the attacker relays both to the real site and is inside your account before the code expires. Codes are valid for thirty seconds and an automated relay takes about two.

That gap is why security teams push hardware keys for the accounts that matter most. A hardware key is bound to the domain in the browser, so it will not produce a signature for the wrong site. For email, banking, and your password manager itself, a hardware key is a materially different level of protection. For the other forty accounts, TOTP is a reasonable trade.

The failure mode nobody plans for

Ask people who have lost an account what happened. It is almost never "someone phished me." It is "my phone died, and the backup codes were in a drawer in another city."

This is where authenticator apps genuinely differ, and it has nothing to do with the interface.

There are three backup models in common use:

ModelHow it worksWhere it breaks
No backupCodes live on one device onlyDevice loss is total loss, unless you saved recovery codes
Vendor cloud syncCodes encrypted and synced through the vendor's serviceYou depend on the vendor staying alive and not locking you out
Self-managed encrypted exportYou export an encrypted file and store it yourselfYou depend on remembering where you put it and the password

None of these is strictly better. They trade different failures against each other. But you have to pick one deliberately, because the default is usually the first, and the first is the one that ends with a support ticket you cannot win.

What actually works

Whatever app you choose, do these three things this week:

  1. Generate the recovery codes for your ten most important accounts and store them somewhere that is not the phone. A printed sheet in a folder, or an encrypted note in a password manager you can reach from a second device.
  2. Add a second device to the same authenticator. Most apps support this now, whether through export or through sync. One phone is a single point of failure.
  3. Check the account recovery path. For Google, Microsoft, and Apple, this is the "I lost my phone" flow. Walk through it once while you still have the phone. It usually involves a backup email or a trusted device, and if that backup email is on the same account, you have a loop with no exit.

Hardware keys deserve a separate mention

If you are protecting a business, a shared account, or anything that would cost real money to lose, a hardware key beats every app on this list for the accounts that accept one. The two practical problems are that some services still do not support them, and that you should buy two and register both, because a single key is a single point of failure in exactly the same way a single phone is.

Hardware keys also remove the phishing problem entirely for the accounts that use them, which is the one thing no authenticator app can do.

SMS is worse, but not zero

The standard advice is to disable SMS two-factor because SIM swapping exists. That is true, and SIM swapping is a real, documented attack that has cost people their savings.

But the practical picture is more nuanced. SMS is better than a password alone, and for the majority of accounts where the alternative is nothing at all, turning it on is a clear improvement. The rule worth following is narrower: for your email, your bank, and your domain registrar, do not rely on SMS alone. For a loyalty account at a hardware store, it is fine.

What to look for in the app itself

Setting aside backup, the remaining criteria are modest:

  • Does it work offline? TOTP is a local computation. An app that needs a network round trip to show a code is broken by design.
  • Can you search and organise? At fifty accounts, a flat list becomes unusable. Folders, tags, or search are not luxuries.
  • Does it have a desktop client? Typing codes on a laptop from a phone screen gets old quickly.
  • Is the export format portable? If the only way out is a proprietary blob, you are renting your second factor.
  • Who runs it, and how would you know if they were breached? A small team is not automatically worse, but the disclosure track record matters more than the feature list.

The honest summary

The differences between the well-known authenticator apps are small enough that switching for features is rarely worth the migration risk. The differences between backup strategies are large enough that choosing one is worth an hour of your time.

So: pick an app that supports export or sync, register a second device, print the recovery codes, and then stop thinking about it. The account you save will be your own.

One last thing worth doing before you close this tab: check your main email address against a breach database. If it appears in a dump you do not remember, that is the account to fix first, and two-factor on an already-compromised address does less than you would hope.

Tools mentioned in this guide

← All guides