Generator/Alternatives/Google Authenticator

Google Authenticator in a browser, when the phone is not the answer

Google Authenticator and this page compute the same six digits from the same secret, because both implement RFC 6238. The difference is not the algorithm — it is where the key lives and what happens when the phone is not in your hand.

Compared with Google AuthenticatorBy GoogleRuns on iOS and Android only
or drop an image here

Advanced
Digits
Period
Algorithm
Your code appears herepaste a key above, upload its QR image, or scan one

Where Google Authenticator is the better tool

  • It is a real vault. Keys persist across reboots and app updates, and since 2023 they sync to your Google account, so a lost phone no longer means lost codes.
  • Keys never touch a browser, which removes an entire class of risk: no extension can read them, and clearing site data cannot destroy them.
  • Transferring accounts to a new phone is built in, through an export QR code that carries several accounts at once.
Worth saying plainly

Gen2FA is not a replacement for Google Authenticator. It holds nothing you have not pasted in, it lives in one browser, and anything you save here is stored in readable form. Keep an authenticator app enrolled and keep your recovery codes. This is the route in when the app is out of reach.

Where it leaves you stuck

  • There is no desktop version. On a laptop you reach for your phone every time, which is the single most common reason people look for something else.
  • A dead battery, a phone left at home, or a device in for repair means no codes at all until you get it back.
  • Cloud sync is tied to your Google account — and if that account is itself protected by the codes in the app, a lockout becomes circular.

When a browser is the right call

  • You are already at a keyboard and do not want to pick up a phone for every login.
  • The phone is lost, broken, flat or elsewhere, and you still have the original setup key or its QR image.
  • You are on a work machine where installing an app is not permitted.
  • You want to check that a key you wrote down is correct before trusting it.

Moving a key across

  1. Find the original setup key. On the service’s 2FA screen, choose to add an authenticator app and look for the link that reveals the text key behind the QR code.
  2. Paste that key into the field at the top of this page. The code appears immediately.
  3. Compare it against the code Google Authenticator is showing for the same account. If the two match, the key is correct.
  4. Keep the app enrolled. Use this as the route in when the phone is not available, not as the place your keys live.

Questions

Will the codes match what Google Authenticator shows?
Yes, provided both hold the same secret and both devices have an accurate clock. TOTP is a function of the shared key and the current 30-second time step, so any correct implementation produces the same digits. If they disagree, the usual cause is clock drift on one device, not a bad key.
Can I import my Google Authenticator export QR code?
No. The export QR is a Google-specific format holding several accounts at once, not a standard otpauth:// link, and this site does not decode it. Take the individual setup key from the service instead.
Is this safe to use instead of the app?
It is not a replacement for the app and should not be your only copy of a key. A browser tab is easier to lose than a phone, and anything you save here is stored in readable form. Keep the app enrolled and keep your recovery codes.

Related