No account. No upload. No tracking.

Your 2FA code stays yours.

A clean, privacy-first TOTP authenticator that computes codes on your device—paired with practical guides that make account security easier to understand.

Browser-only Zero storage RFC 6238
Current code Example account
Local
Renews in 18 seconds SHA-1 · 6 digits
Secret handling Never leaves this browser
01

Paste securelyYour key remains on-device.

02

Use instantlyNo signup or sync needed.

Designed around three promises

0secret-related API calls
0accounts required
100%on-device computation

Privacy by architecture

Security you can understand.

2FAOTP avoids the usual cloud trade-off. The tool does one focused job, with fewer moving parts and no database holding your secrets.

01

Nothing to upload

Your Base32 secret is read by local JavaScript and passed directly to the browser's cryptographic engine.

02

Works after loading

TOTP is based on a shared secret and your device clock. Code generation needs no account and no live server response.

03

Clear, honest guidance

We explain what the tool can protect, what it cannot, and when a dedicated authenticator is still the safer choice.

How TOTP works

One secret. One clock. A code that keeps moving.

Your service and authenticator both hold the same secret. Every 30 seconds they independently combine it with the current time. Matching results confirm that you possess the secret—without transmitting it during sign-in.

Read the complete explanation →
  1. 1
    Enter a Base32 secret

    Usually shown below a 2FA setup QR code.

  2. 2
    Compute with Web Crypto

    HMAC combines the secret with a time counter.

  3. 3
    Use the short-lived code

    The code expires at the end of its time window.

Ready when you are

Generate a code without giving up your secret.

Open 2FAOTP