TOTP QR Code Builder (otpauth URI)
Builds the otpauth URI and a scannable QR code for two-factor setup, with the current code so you can check the app matches.
Use the tool
Why this tool exists
When you add two-factor login to an app, the user scans a QR code that carries the secret, issuer and account in an otpauth:// URI. This tool builds that URI for tests, demos and documentation.
Leave the secret blank to get a fresh random 160-bit Base32 secret, or paste your own. The page shows the current code from the same secret so you can compare it with the authenticator. Most apps ignore algorithm, digits and period and use SHA1, 6 digits and 30 seconds, so change them only if you know the app supports it.
How to use it
- Enter issuer and account.
- Leave the secret empty to generate one, or paste a Base32 secret.
- Scan the QR with an authenticator app.
- Compare the code shown here with the app.
Frequently asked questions
Is the secret stored?
No. It exists only in this page. Anyone with the QR image or secret can make valid codes, so do not share them.
Why do I need an issuer?
It labels the entry in the app. It is also placed in the URI label so older apps show it too.
Why do the codes not match?
Check the device clock. If the app does not support SHA256, SHA512, 8 digits or another period, use the defaults.
Is the QR code standard?
Yes. It is a normal QR code with the URI as text.