Build an otpauth URI and QR code
Build a TOTP or HOTP enrollment URI and optional QR code from a Base32 secret, issuer and account. Keep the secret and generated QR private.
About otpauth URI
otpauth URI builds an otpauth:// enrollment link for authenticator apps like Google Authenticator, 1Password, Authy, and Bitwarden, and can render a scannable QR code right alongside it. Drop in a secret, issuer, and account name, and you get the URI plus a QR to point a phone at. It is generated in your browser, so the TOTP secret is never transmitted to a server.
- Category
- create
- Input
- Accepts: */*.
- Output
- Outputs: application/json (multiple).
- Cost
- Free, runs in your browser
- Memory
- low
Common uses
- Generate a 2FA enrollment QR for a new internal tool you are adding TOTP to
- Create an otpauth:// link to seed Authy or 1Password from a known shared secret
- Re-enroll an authenticator on a new phone using the original secret without a vendor portal
- Build a test 2FA setup for staging without standing up a live auth server
- Produce a scannable QR for onboarding docs that shows users how to add MFA
- Encode HOTP or TOTP parameters precisely when debugging a one-time-password flow
Frequently asked questions
Which authenticator apps does the URI work with?
Any app that supports the otpauth:// standard, including Google Authenticator, 1Password, Authy, and Bitwarden.
Does my TOTP secret get uploaded?
No. The URI and QR are built entirely in your browser, so the secret never touches a server.
Does it produce a QR code too?
Yes. It can render a scannable QR alongside the URI so you can enroll a phone directly.
Does it support both TOTP and HOTP?
Yes. You can encode the standard otpauth parameters for time-based or counter-based one-time passwords.
What does it return?
A JSON result containing the otpauth:// URI (and the QR where requested).
Keywords
- otpauth
- totp
- hotp
- 2fa
- mfa
- qr
- enrollment
- authenticator