You normally do not back up the changing six-digit code itself. You preserve a supported recovery method: provider-issued recovery codes, an authenticator transfer or sync feature, another enrolled device, or a securely stored TOTP setup secret. This guide explains the differences and the limits of a local generator.
A changing TOTP code expires quickly, so saving screenshots of current codes is not a useful backup. A usable backup is usually a provider-issued recovery code, an authenticator export or sync method, another enrolled factor, or the original TOTP setup secret stored with strong protection.
A TOTP code is the changing 6 or 8 digit code generated from a shared setup secret. A backup or recovery code is usually a static emergency code issued by the account provider for one-time account recovery.
A Base32 setup secret or otpauth://totp/ link can generate future TOTP codes. A recovery code normally cannot generate TOTP codes; it is entered directly on the account recovery screen when the authenticator is unavailable.
This tool helps if you still have the original Base32 setup key or otpauth URI and need to generate the current authenticator code locally. It can also help test a copied setup key before you remove an old authenticator device.
It cannot recover a lost secret, extract codes from another app, create new recovery codes, approve push prompts, bypass an account provider, or generate a valid code after the original setup secret is gone.
Before removing an old phone, add the setup key to the new authenticator, compare the current TOTP code, store the account's official recovery codes, and only then disable or remove the old authenticator entry.
For temporary testing with a real setup key, prefer a fragment shortcut such as #secret=YOUR_BASE32_SECRET. Path and query shortcuts are supported for convenience but are server-visible and marked noindex.
Use the account provider's recovery codes and your authenticator app's supported transfer, sync, or export process. If you retain a TOTP setup secret, protect it like a password because anyone who has it can generate valid codes.
No. Backup or recovery codes are created by the account provider. This site only calculates TOTP authenticator codes from a setup secret or otpauth URI.
Only if you still have a valid setup secret, a synced authenticator account, another enrolled device, or official recovery codes. Otherwise you need the account provider's recovery process.
For important accounts, store recovery information carefully in a trusted authenticator app, password manager, or secure backup flow. Anyone with the TOTP setup secret can generate valid codes.
No. A Base32 secret is used by a TOTP generator to calculate changing authenticator codes. A recovery code is usually a one-time fallback code accepted directly by the website.