TOTP Generator
Compare published RFC 6238 vectors or generate a local code at the device clock or a specified Unix timestamp.
Reproduce a Published TOTP Vector
Use 16–128 decoded secret bytes and match the verifier’s algorithm, digits and period. An RFC example uses a public test key.
TOTP Generator: how to use it
- Enter an RFC 4648 Base32 secret or load the public RFC example for the selected hash.
- Choose HMAC SHA-1, SHA-256 or SHA-512, six to eight digits, and the verifier’s period.
- Choose the current device clock or enter a reference Unix timestamp. Generate the code and copy only when needed.
Limits and notes
Accepts canonical padded or unpadded Base32 for 16–128 decoded bytes, with ASCII grouping spaces allowed. Periods are 1–300 seconds. Uses the Unix epoch as T0 and Web Crypto on HTTPS or localhost. Secrets are kept in the current workspace state only.
How your privacy works →TOTP Generator: common questions
Why can two devices show different codes?
The secret, algorithm, digit count, period and time window must agree. A clock difference near a period boundary can also change the current code.
Does the reference timestamp keep changing?
Reference mode stays on the specified Unix second. Live mode recalculates when the current device clock enters a different period.
Are padding and lowercase accepted?
Canonical RFC 4648 padding is optional, and the decoder accepts ASCII lowercase. Incorrect length, extra padding and nonzero unused bits are rejected.