What is 2FA?
Two-factor authentication adds a one-time code to your password. This page generates those time-based codes (TOTP) just like Google Authenticator or Authy, right in your browser.
A fast, free and private alternative to authenticator apps.
One key or otpauth:// link per line. Spaces and dashes are ignored.
Values inside an otpauth:// link take precedence over these settings.
Your keys are processed entirely in your browser. Nothing is sent to our servers or stored; close the page and they are gone.
Use this tool only for accounts you own or are authorised to access.
Paste a secret key or scan a QR code to see your codes here.
Next: –
Lost your phone, or simply prefer working on your computer? Paste your secret key and this page creates your 6-digit login codes in real time. Everything is calculated inside your own browser: your keys are never sent, saved or shared. No sign-up, no tracking.
Two-factor authentication adds a one-time code to your password. This page generates those time-based codes (TOTP) just like Google Authenticator or Authy, right in your browser.
Codes are computed locally with your browser's Web Crypto API. We cannot see, store or log your secret keys, and the page sets no cookies.
Paste a key or scan a QR code and the code appears immediately. The page also checks your device clock against ours, so codes stay valid even if your clock is off.
Think of 2FA as a second lock on your account. A password alone can be guessed, leaked or phished; with 2FA, a login also needs a code that changes every 30 seconds.
Enter your username and password as usual.
The site asks for a second proof that it is really you.
Your secret key and the current time produce a 6-digit code.
Type or paste the code before it expires.
The site checks the code with the same key and time. You are in.
When you turn on 2FA, the website shares a secret key with you, usually as a QR code. Both sides then use that key and the current time to calculate the same code (TOTP, RFC 6238).
Because every code expires after a short window, a stolen code becomes useless within seconds. Without the secret key, nobody can predict the next one.
When you enable 2FA on a service, choose "authenticator app". Under the QR code you will usually find a "can't scan?" option that shows the text key.
Paste the base32 key or an otpauth:// link into the box above, or scan the QR code with your camera. Add one key per line to manage several accounts.
Your current code appears instantly. Copy it with one click and paste it into the login form before the timer runs out.
Authenticator apps tie your accounts to a single phone. If the phone is lost, broken or out of battery, you can be locked out at the worst moment.
With this generator you can use any device you trust: desktop, laptop or tablet, with nothing to install. Keep a backup of your keys in a secure place such as an encrypted password manager, and you will always have a way back in.
This generator follows the open TOTP standard (RFC 6238), so it works with any service that supports authenticator apps.
Yes. Your secret key is processed only in your browser with the Web Crypto API. It is never sent to a server, written to storage or put in a cookie, and it disappears when you close the page.
Once the page has loaded, code generation needs no connection: it only uses your key and your device clock. The page contacts our server once to check your clock, without sending anything secret.
TOTP codes depend on time. If your device clock is wrong by more than about 30 seconds, codes will not match. This page corrects for that automatically; also make sure you copied the right key and that the service uses the same settings (digits, period, algorithm).
Only if you still have the secret key or its QR code, for example in a backup or password manager. Without the key, use the recovery codes the service gave you when you turned on 2FA.
No. There is no account, no database of keys and no tracking. Even we cannot see the keys you paste.
Any service that uses standard TOTP codes, including Google, Microsoft, GitHub, Discord, Binance and most other sites that offer "authenticator app" sign-in.
A practical security checklist covering 2FA setup, password hygiene, and recovery options. Twelve concrete steps you can take today to harden your accounts against takeover.
Read moreHow two-factor authentication evolved from clip-on hardware tokens and SMS codes to today's phishing-resistant passkeys — and why each step happened.
Read moreA practical guide to securing exchange accounts, banking apps and crypto wallets with 2FA, covering authenticator apps, hardware keys and withdrawal protection.
Read more