Guide
How to use this tool well
Time-based one-time passwords (TOTP) rotate every 30 seconds from a shared secret. Enter the same Base32 secret as your authenticator app to confirm codes match before you rely on this page.
How TOTP lines up with Google Authenticator
Both sides hash the secret with the current time counter (usually 30-second steps) and show six digits. If codes differ by one step, check phone time sync (automatic date/time) and that you did not truncate the secret.
otpauth:// URLs include issuer and account name β our importer strips those so you paste only the secret key.
When TOTP helps
TOTP blocks most password-only phishing: the attacker needs the live six-digit code. Prefer hardware security keys (WebAuthn) for high-value accounts when supported; keep TOTP as a strong second factor everywhere else.
Back up secrets in your password managerβs OTP field or printable recovery codes β losing the phone without backup means account lockout.
Common questions
- Why did my code work in the app but not here?
- Common causes: spaces in the secret, wrong Base32 padding, or using floor vs round on Unix time. This implementation follows standard TOTP time steps.
- Should I use SMS instead?
- Authenticator apps are generally safer than SMS (SIM swap risk). Use SMS only when no other option exists.
Editorial standards: how we write and review guides.