Report

Help us improve this tool

OTP URI Builder

Generate RFC 6238 compatible otpauth:// URIs for authenticator apps from secret, issuer, and account name locally.

O M T

Build otpauth:// URIs for authenticator apps

Authenticator apps import accounts through otpauth:// URIs defined by the de-facto Google Authenticator key format. A TOTP URI includes the Base32 secret, issuer, account label, HMAC algorithm, digit count, and time step. HOTP URIs add a counter instead of a period. This builder assembles a valid URI locally so you can test enrollment flows without sending secrets to a server.

How to use it

  1. Choose TOTP or HOTP.
  2. Paste the Base32 secret from your identity provider or hardware token provisioning step.
  3. Fill issuer and account labels (often Issuer:email in the path).
  4. Adjust algorithm, digits, and period if your provider documents non-default values.
  5. Copy the URI into QR generators or mobile test harnesses.

To generate live codes from a secret use OTP Code Generator or OAuth PKCE Generator when wiring modern OAuth login alongside MFA.

Frequently Asked Questions

Are secrets uploaded?

No. The URI is composed entirely in your browser. Treat secrets like passwords and clear the form after use.

Which algorithms are supported?

SHA1, SHA256, and SHA512 are common HMAC choices. Your authenticator must support the algorithm you select.

Why is issuer duplicated in the path and query?

Many apps read issuer from the query string while the path label helps humans recognize the account.