Different credentials, different jobs

Setup Key vs Backup Code: Know Which 2FA Credential You Have

A setup key generates temporary codes. A backup code is a separate recovery credential issued by a service. Confusing them can expose a reusable secret or leave you relying on material that cannot restore access.

Identify the purpose and origin of each item before entering it anywhere. The TOTP generator accepts only an existing raw Base32 setup key. It does not scan enrollment images, import links, recover secrets, or verify backup credentials.

Recognize the reusable setup secret

The setup key, also called a TOTP secret or seed, is the reusable input established during authenticator enrollment. A manual entry option may show it as grouped letters and numbers. It is not the account password and not the short number you submit at sign-in. This tool needs this raw value: 16 to 256 Base32 characters using A-Z and 2-7, with optional ordinary ASCII spaces. Lowercase is normalized. Valid trailing padding is supported, but incomplete encoding groups and invalid trailing bits are rejected.

Keep a real secret only in protected storage approved for that account, if retaining it is appropriate. For example, a folder titled New workstation containing an unlabelled setup screenshot is a poor record: it hides neither the credential nor which enrollment it belongs to. Do not move a secret into an ordinary onboarding checklist to make that checklist complete. A nonsecret note can identify the account owner and protected recovery location without reproducing credentials. Anyone who obtains the active seed may calculate later TOTP numbers, so treat it differently from a used temporary output.

Distinguish a QR image from an enrollment URI

An enrollment QR code is a visual carrier of setup data. A common format carries an otpauth URI that can include the secret, an account label, an issuer, and calculation parameters. That package is more than the raw Base32 field. A screenshot of the QR can therefore be sensitive even though it does not look like a password. Authenticator transfer QR codes may carry a different package and should not be assumed to be ordinary single-account enrollment data. Neither kind of image is accepted by this generator.

Imagine preparing a training document that shows where a service displays its pairing image. Use a fictional illustration or the public demo workflow, not a capture of your real enrollment screen. Do not paste the complete URI into this tool or a general-purpose online decoder. If the service offers a trusted manual-key view, use that raw secret and separately confirm its settings; otherwise continue through its supported authenticator flow. Copying only the raw key does not transfer any accompanying issuer, account label, or parameter information into this tool.

Identify the temporary number used at sign-in

A current TOTP number is output from the secret and time, not a substitute for the secret. Saving today’s number does not preserve the ability to generate tomorrow’s numbers. Likewise, a number beginning with zero must retain that zero when entered. This tool defaults to SHA1, six digits, and 30-second windows, with optional SHA256, SHA512, eight digits, and 60 seconds. Those settings must be chosen explicitly to match the enrollment. A raw key does not identify them, and a longer displayed number does not automatically mean better compatibility.

Suppose you are assembling a device-replacement checklist and find an old note labelled Login code. If it contains only a temporary number, do not file it as an authenticator backup. Determine whether a current enrolled authenticator or protected setup record exists instead. The generating device needs an accurate clock, but you do not need to manually change timezone to UTC. This tool does not synchronize time over the network. A visible number confirms a local calculation only; it never confirms account ownership, live testing, or acceptance by a service.

Practice without private material

Use the public demonstration key

Explore the generator with its explicit demo instead of using screenshots or credentials from a real enrollment.

Keep backup codes in the provider recovery process

Backup codes are separately issued by a provider for a recovery or alternative sign-in route. Their appearance alone is not a reliable classifier: an eight-digit backup code can resemble an eight-digit TOTP output while serving a different purpose. Google, for example, documents eight-digit backup codes that become inactive after use, and says creating a new set invalidates the old set. Those are Google rules, not a universal promise about every service. Use the issuing provider instructions to understand availability, reuse, replacement, and the exact prompt that accepts them.

For a practical filing decision, keep a provider-issued recovery sheet identified by provider, account, and generation date within protected storage. Replace obsolete copies when the provider issues a replacement set. Do not paste the sheet into the setup-key field to see which line works, and do not send it to a helper who asks to check it. This generator cannot look up recovery keys, validate an unused backup code, or regenerate a provider list. A recovery key may also be a distinct credential under that service terminology, so follow its documented purpose rather than inferring behavior from the name.

Plan replacement without mixing up revocation

Different actions replace different material. Refreshing a backup-code set is not the same operation as replacing the authenticator seed. Clearing this browser field is neither of those provider actions. If a seed was included in a shared attachment, use the account security process to replace that enrollment rather than assuming a password change alone removes the seed. Complete the provider confirmation requirements and preserve an available legitimate sign-in method while working. Security changes may require reauthentication, and recovery options differ between accounts; a currently open session is not a guarantee that changes are permitted.

During a planned phone replacement, separate three questions: whether the current authenticator can be transferred through its supported process, whether an independent recovery route is available, and whether any old credential needs revocation. Do not use this page as a transfer archive. It has no saved account list or project export. Nor can it replace SMS, push, passkey, or counter-based HOTP enrollment. If the current key is missing, use an enrolled method or official recovery. Trying to reconstruct it from a previous code or your username is outside this tool’s capabilities.

Handle each item according to its exposure

When exploring, load the public demo. Its key is published, so it must never protect a real account. For real input, the isolated sandbox performs local calculation without a generation API or server upload of the key or code. There is no tool-managed storage, history, PDF, or saved project. Changing an input invalidates the result until Get code is selected again. Remember: a generator is a temporary calculation surface, while your approved credential storage and the provider remain responsible for retention and enrollment management.

The working key clears when the tab is hidden and on pagehide, restoration, or freezing. Copy code copies only the temporary number; it does not copy a credential bundle, and clearing does not clear the clipboard. Browser extensions, clipboard history, screenshots, and browser-memory remnants remain outside this control, with no secure-erasure or absolute-security promise. Finish a credential-sorting task with protected records in the right place and no secrets in ordinary notes. If a current number is still rejected after you identify the correct material, continue with the TOTP diagnosis guide.

Questions about Setup Keys and Backup Codes

Can I use a backup code as the secret setup key?

No. Use backup credentials only in the issuing service recovery or alternative sign-in flow. A code that happens to resemble Base32 text is not evidence that it is a TOTP seed, and this tool cannot check its recovery status.

Does photographing the enrollment QR make a safe backup?

A pairing image can expose the same reusable secret as manual entry. Do not treat a photo as harmless documentation or assume this tool can import it. Follow the provider and your organization rules for protected backup or transfer.

Will replacing my backup codes fix an exposed authenticator key?

Do not assume so. The backup-code set and authenticator enrollment are different credentials. Use the provider process to replace the exposed TOTP enrollment, then review its recovery material separately.

Continue with another authenticator guide

Use the Online 2FA Authenticator with your existing setup key, or choose a related guide. More utilities are available in all free tools.

For a correctly identified setup key

Calculate with the documented parameters

Return to the generator only with the current raw secret and matching settings. Keep backup credentials in the provider recovery flow.