Runs locally in your browser. Nothing you enter is uploaded to our servers.
Result will appear here
Tips for 2FA QR codes
Scan QR codes only from trusted enrollment screens.
Do not screenshot and share otpauth QR codes casually.
Verify the issuer and account label before saving.
Keep a backup of the secret if the QR is your only copy.
Delete temporary QR images after setup.
Turn a TOTP secret into a scannable QR
Processing stays in your browser — your input is not uploaded to our servers.
Authenticator apps enroll via an otpauth QR. This helper encodes issuer, account, and secret into that QR so you can scan it instead of typing base32 by hand.
Generate the QR on a machine you trust. Anyone who photographs it can mint codes for that account.
Make a TOTP QR code
Fill issuer, account, and secret
Issuer is the service name; account is usually the login; secret is the base32 seed.
Show the QR
Scan it with the authenticator. Confirm a live code works before you delete the old factor.
Remove the QR from view
Do not print it on a wiki or leave it in screenshots.
TOTP QR FAQ
Does scanning upload the secret to this site?
No. The QR is drawn locally. The risk is someone else seeing the QR, not our servers.
Can I use this instead of the service’s own QR?
Yes, if you already have the same secret. The otpauth payload must match what the server expects.
What if the app will not scan it?
Check that the secret is valid base32 and that the QR is not cropped or too small on screen.