OTP URI Builder screenshot

OTP URI Builder

Build an otpauth:// URI for a TOTP authenticator: base32 secret, issuer, account, digits and period, with each value validated.

Privacy First
0 Runs
Updated 2026-11-17
Runs in your browser
No sign-up, no upload

What the OTP URI Builder does

The label is Issuer:account with both parts percent-encoded, and the issuer is repeated in the query because that is what most clients display. Digits are 6 or 8 and the period is 15 to 120 seconds, the range authenticators implement.

SHA-1 is written explicitly rather than omitted, so the URI states the algorithm the code will use.

This builds a URI; it does not generate or check a code. There is no QR image here, and the page cannot tell you whether the secret is the one the server holds — only an authenticator can.

How to use it

Set the Base32 secret, Issuer, Account, Digits and Period (s), or press Run with the defaults.

Read the otpauth URI below and import it into an authenticator, or turn it into a QR code with another tool.

Check the label — it is what the account list shows, and it is built from Issuer and Account.

Worked example

Input:


Output:

otpauth://totp/Example:ada%40example.com?secret=JBSWY3DPEHPK3PXP&algorithm=SHA1&digits=6&period=30&issuer=Example

Why it runs in your browser

The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.

An `otpauth://totp/…` URI an authenticator app can import: the label carries the issuer and account, and the query carries the secret and the parameters.

The secret is checked as base32 — A-Z and 2-7, the alphabet authenticators accept — because a secret with a `1` or an `8` in it is a transcription error, not a key.

What it does, and what it does not

The label is `Issuer:account` with both parts percent-encoded, and the issuer is repeated in the query because that is what most clients display. Digits are 6 or 8 and the period is 15 to 120 seconds, the range authenticators implement.

SHA-1 is written explicitly rather than omitted, so the URI states the algorithm the code will use.

This builds a URI; it does not generate or check a code. There is no QR image here, and the page cannot tell you whether the secret is the one the server holds — only an authenticator can.

How to use OTP URI Builder

Set the Base32 secret, Issuer, Account, Digits and Period (s), or press Run with the defaults.

Read the otpauth URI below and import it into an authenticator, or turn it into a QR code with another tool.

Check the label — it is what the account list shows, and it is built from Issuer and Account.

What to Expect

Best for

  • Importing an account into an authenticator by hand
  • Checking a base32 secret before enrolling it

Not ideal for

  • Generating a code, which needs the current time
  • Rendering a QR image, which this page does not do

What this tool keeps

  • The secret upper-cased as base32
  • Issuer repeated in the label and the query

What may need cleanup

  • A secret containing 1 or 8 is not base32 and must be corrected
  • An HTOP account needs a counter, which this page does not emit

Common errors

  • The page refuses it: secret must be base32

Example use cases

  • Adding a test account to an authenticator
  • Checking a secret before handing it to a user

Sample input

Authenticator settings:

Sample output

otpauth URI: otpauth://totp/Example:ada%40example.com?secret=JBSWY3DPEHPK3PXP&algorithm=SHA1&digits=6&period=30&issuer=Example …

Who this is for

  • Developers testing two-factor enrolment
  • Support staff reading a broken enrolment

Frequently asked questions

Why is SHA-1 written in the URI?

It is the algorithm essentially every authenticator implements, and writing it explicitly makes the URI say what the code will do rather than relying on a default.

What counts as a valid secret?

Base32: A-Z and 2-7, with optional padding. A digit 1 or 8, or a lowercase letter after normalisation, means the secret was mistyped.

Does it make a QR code?

No. It produces the URI; a QR encoder turns that into an image. Keeping the two separate means the page never draws a code you cannot read.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.