Add a TOTP seed

TOTP support lets OTPBase host your rolling 2FA codes itself, alongside the codes forwarded from SMS. You add a seed once, and OTPBase generates the time-based code for you on /totp.

What TOTP means here

A TOTP seed is the secret behind an authenticator app's rolling 6-digit code. Hand OTPBase the seed and it becomes a self-hosted source: the code refreshes on a fixed period, and you read it on the same page as everything else.

Add a single seed

1. Open /totp/add.

2. Paste an otpauth:// URI, for example:

   otpauth://totp/Acme:you@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Acme
   

   The secret is the seed (Base32). The label and issuer become the name shown on /totp.

3. Save it. The rolling code appears on /totp immediately.

Bulk-import from Google Authenticator

Google Authenticator can export all of its accounts at once as a single migration string, which OTPBase imports in bulk.

1. In the Google Authenticator app, tap the menu and choose Transfer accounts → Export.
2. Select the accounts and continue. The app produces an otpauth-migration://offline?data=... string, shown as a QR code.
3. Capture that string (scan the QR with any reader to reveal the text) and paste it into /totp/add. OTPBase decodes every account in the export and adds them together.

Supported parameters

OTPBase handles the standard TOTP range:

Most seeds use SHA1, 6 digits, and a 30-second period — the defaults that come through in a typical otpauth:// URI.

Security

Seeds are encrypted at rest with AES-256-GCM. The secret never appears in plaintext on /totp; only the current rolling code does.

Viewing your codes

Open /totp to see every seed and its current code. The page updates every second so the code is always live, and you can click a code to copy it.