Diagnose before another attempt
TOTP Code Not Working: A Practical Troubleshooting Guide
A rejected authenticator code does not identify its cause. Work through the requested method, timing, input, parameters, and enrollment in order. Stop repeated submissions while you diagnose; a service may limit attempts.
Keep any legitimate signed-in session available, but expect the provider to require further verification for security changes. The local TOTP generator can calculate a code from an existing key. It cannot test account acceptance or explain a provider decision.
Separate an input error from a rejected sign-in
First locate the failure. If Get code produces an input error or leaves the result empty, the generator has not produced a usable result for the current inputs. Check the key and controls before touching the sign-in form again. If a number appears here but the service rejects it, the calculation succeeded locally; that does not prove the secret, destination, or enrollment is correct. Record only the nonsecret error wording when seeking help. Do not send a screenshot containing the key or a current code.
Read the destination prompt carefully. An authenticator-app challenge differs from an SMS code, email code, push approval, passkey, backup code, or recovery key. This page supports TOTP only, not counter-based HOTP or any of those other methods. It cannot look up or verify recovery credentials. For example, an account may offer both a text-message route and an authenticator route. A TOTP number belongs only in the matching authenticator prompt, not whichever field happens to accept six digits. Use the official sign-in choices to select an enrolled method.
Check the current instant before changing timezone
Check the generating device date and time against a reliable reference and use its operating system synchronization controls if needed. This generator reads the local clock and has no network time synchronization. A laptop waking after a long period offline is a useful example: the browser may be working normally while the system time is wrong. Fix the actual clock, then generate afresh. You do not need to manually change timezone or display UTC; TOTP uses an underlying timestamp, not the city label beside the clock.
Once the clock is accurate, consider the time spent moving between screens. If only two seconds remain before the next window, typing slowly can deliver the number after that boundary. Wait for a fresh window, copy once, and submit promptly to the correct destination. Keep leading zeros. The countdown describes this device calculation, not a provider promise about expiry or allowed drift. Recopying the same still-current number is not a new challenge, and a provider need not accept a number again after successful use. Avoid deliberately shifting the clock to chase acceptance.
Inspect the raw key without inventing repairs
Compare the input with the original trusted manual setup record. This tool accepts 16 to 256 Base32 characters using A-Z and 2-7, after removing optional plain ASCII spaces and excluding valid trailing padding. Lowercase is accepted through normalization. Tabs, line breaks, nonbreaking spaces, labels, and punctuation are not allowed substitutes for ordinary spaces. The complete input is limited to 512 characters. If a key was copied from a formatted document, hidden formatting may explain rejection, but remove only formatting you can distinguish from the actual credential.
Some lengths or trailing bits cannot represent a complete canonical Base32 value. Incorrect padding is also rejected. Do not append a guessed letter, replace an ambiguous character on instinct, or shorten the key until the error disappears. A complete otpauth URI, a QR image, and an authenticator transfer QR are not raw-key inputs here. Use a trusted manual-key option when available; otherwise use the provider-supported enrollment route. If your saved material is a backup-code sheet rather than a secret, consult the credential differences guide before proceeding.
Check one cause at a time
Return with the confirmed settings
Use the existing current setup key only after checking the requested method, clock, and documented parameters.
Verify parameters from the setup record
The initial configuration is SHA1, six digits, and a 30-second period. SHA256, SHA512, eight digits, and 60 seconds are supported alternatives, not automatic discoveries. A raw key cannot tell this page which combination the account expects. Consider a development dashboard whose documented enrollment uses eight digits and 60 seconds: six-digit default output would not match that instruction even with the right secret. Check the original enrollment requirements or ask the authorized administrator, rather than trying every available combination against a live account.
After correcting a key or setting, select Get code again. Each input change invalidates the previous result, so an empty display after an edit is expected. Clear removes the key and result but does not reset all controls to defaults. Loading the public demo does reset the controls to SHA1, six digits, and 30 seconds. Remember that distinction when moving from demonstration to diagnosis. The demo key is public and must never protect a real account; a changing demo number shows the local display running, not that your account configuration is correct.
Check for a replaced key or a cleared session
Ask whether the enrollment changed after the key was recorded. Re-enabling an authenticator, replacing a lost device through a fresh enrollment, or an administrator reset may leave an older secret obsolete. It can still pass Base32 checks and produce numbers. The generator has no account lookup with which to flag that history. For example, a protected note saved before an approved authenticator replacement may now contain a well-formed but irrelevant key. Use records of the latest completed enrollment, not the most conveniently accessible copy.
Also distinguish missing input from a lost account enrollment. Hiding the tab clears this tool’s key and result; pagehide, restoration, and freezing clear them too. Returning to a blank field after checking another tab is expected. Copy code before leaving, since the button copies only the number and the clipboard is not cleared with the page. If automatic copying fails, use the selected code with the keyboard or device menu. Never paste a clipboard value back blindly: a different application may have replaced it, or it may contain an older number.
Stop at the recovery boundary
If the current key or enrollment requirements are unavailable, repeated generation cannot recover them. Use an existing enrolled method, an unused provider-issued backup credential where supported, or the official account recovery process. Do not disable a working factor just to experiment, and do not sign out your remaining legitimate session unnecessarily. Describe the problem without credentials when contacting authorized support: for example, that a device was replaced and the previous enrollment record no longer matches. No local generator can promise recovery eligibility or a successful sign-in.
This tool calculates inside an isolated sandbox without a generation API or server upload of the key or result. It has no tool-managed storage, history, PDF, or saved project for later diagnosis. That does not control clipboard managers, browser extensions, screen capture, or every browser-memory copy, and clearing is not guaranteed secure erasure. Use the public demo for demonstrations, clear real input when finished, and follow the provider replacement process if a secret may have been exposed. Local calculation and sandboxing reduce particular exposures; they are not absolute security or acceptance guarantees.
Questions about TOTP Troubleshooting
Why does the same code appear when I select Get code again?
An unchanged key and configuration in the same time window normally produce the same number. Generating again does not request a new server challenge. Wait for the next window when appropriate, and follow any provider retry limits.
Two generators agree. Does that rule out the key?
No. They may both be calculating from the same outdated or wrong-account secret. Agreement can help compare a calculation, but neither generator knows which enrollment the provider currently associates with your account.
Why is the key gone after I checked the sign-in tab?
The generator clears when its tab becomes hidden. Copy the current code before switching away and use it promptly. The copied number may remain on the system clipboard even though the key and result are cleared here.
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.
When the credential is unclear
Identify the material before using it
A setup secret, temporary code, and backup credential serve different purposes. Keep recovery in the provider process.