How to fix 1Password authenticator not working
If your 1Password authenticator is not working, the problem is usually tied to time sync, vault sync, app updates, or a changed account setup.
This guide walks through the most common causes and the exact fixes that restore one-time passwords and login access.
1Password stores and generates TOTP codes for services such as Google, Microsoft, GitHub, and Amazon.
When those codes fail, the issue can look like a broken app even when the underlying problem is something small.
What usually causes 1Password authenticator codes to fail?
1Password authenticator codes rely on time-based one-time password, or TOTP, standards.
That means the code must match the service’s expected secret and your device must be generating codes on the correct clock.
- Device time is incorrect: Even a small clock drift can make TOTP codes invalid.
- Vault or app sync is delayed: The secret may not have finished syncing across devices.
- Old app version: An outdated 1Password app can cause login and display issues.
- Wrong item or account: You may be viewing a similar login entry that does not contain the current secret.
- Service-side changes: The website may have reset the 2FA secret or rotated credentials.
- Browser or extension conflict: Autofill or extension bugs can interfere with code copy and form completion.
Check the time on your device first
The fastest way to fix 1Password authenticator not working is to verify system time.
TOTP codes are based on the current time window, so even a short mismatch can cause the code to fail immediately.
On iPhone and iPad
- Open Settings.
- Tap General.
- Tap Date & Time.
- Turn on Set Automatically.
On Android
- Open Settings.
- Go to System or General management.
- Open Date & time.
- Enable Use network-provided time and Use network-provided time zone.
On Windows or macOS
- Set the clock to update automatically.
- Restart 1Password after changing the time settings.
- If the issue continues, sign out and back in to force a fresh sync.
After adjusting time settings, generate a new code and test it right away.
If the website accepts the new code, the issue was clock drift.
Confirm you are using the correct 1Password item
Many login problems happen because users save duplicate entries for the same site.
If one login item contains an outdated secret and another contains the current one, the authenticator code can appear broken even though 1Password is working correctly.
- Search the exact website name in 1Password.
- Open the item and check the one-time password field.
- Compare the username, URL, and notes to the website you are trying to access.
- Look for duplicate logins created during password resets or account migrations.
If the site recently asked you to re-enroll in two-factor authentication, the old TOTP secret may no longer be valid.
Delete or archive the stale item only after confirming the new one works.
Force a sync in 1Password
1Password 8 and earlier versions rely on account sync to keep vault data current.
If the authenticator entry was added on one device but not visible on another, the secret may simply not have synced yet.
- Make sure you are signed into the correct 1Password account.
- Check whether the item appears on every device.
- Manually refresh the app or restart it.
- Verify the device has a stable internet connection.
- Sign out and sign back in if the vault looks stale.
This matters especially for teams using 1Password Business or family sharing, where a login item may be stored in a shared vault and not immediately visible on every device.
Update 1Password and your browser
Outdated software can create unexpected behavior with autofill, passkey prompts, and one-time password fields.
Updating the app is a simple step that eliminates known bugs and compatibility problems.
- Update the 1Password desktop app.
- Update the mobile app from the App Store or Google Play.
- Update your browser, especially Chrome, Edge, Firefox, or Safari.
- Install any pending operating system updates.
If you use the 1Password browser extension, reinstalling it can help when code injection or field detection fails.
A fresh extension install often resolves issues that look like broken OTP generation but are actually browser integration problems.
Verify the website has not changed the two-factor setup
Some services invalidate old authenticator secrets when you change your password, reset security settings, or enable a new multi-factor authentication method.
In that case, 1Password still shows a valid code, but the website rejects it because it is expecting a different secret.
Check the account security page for the service you are trying to access.
Look for signs such as:
- A new QR code was scanned during recent setup.
- The site asked you to remove and re-add authenticator app support.
- The backup codes were regenerated.
- The login page says the code is incorrect even though it looks fresh.
If the service rotated the secret, remove the old one-time password entry and add the new QR code or setup key to 1Password.
Rescan the QR code or re-enter the setup key
If you originally added the authenticator secret manually, a single typo can break the code generator.
The safest way to fix a corrupted or outdated setup is to re-enroll the account from the website.
- Open the website’s security or two-factor settings.
- Choose to set up an authenticator app.
- Scan the new QR code with 1Password or enter the setup key manually.
- Save the item and test the generated code immediately.
When manual entry is used, verify each character carefully.
Secrets may include uppercase letters, digits, and symbols that are easy to confuse.
Check for regional, browser, or autofill issues
Sometimes the code itself is correct, but the login flow fails because of browser behavior.
A page may refresh, autofill may overwrite the OTP field, or an extension may paste the code into the wrong input.
- Try signing in with the browser extension disabled temporarily.
- Paste the code manually instead of using autofill.
- Use the 1Password desktop app or mobile app to compare the code.
- Open the login page in a private window to rule out cache or extension conflicts.
If the code works on one device but not another, focus on browser extensions, form behavior, and autofill settings rather than the authenticator entry itself.
Use backup codes if you are locked out
If you cannot get 1Password authenticator working quickly and you need immediate access, recovery codes are often the safest fallback.
Many services provide backup codes during two-factor setup for exactly this reason.
- Check the service’s account recovery or backup code area.
- Use a saved backup code if available.
- Store the account again in 1Password after regaining access.
- Generate new backup codes if the service allows it.
Backup codes are not a permanent fix, but they can prevent account lockout while you repair the authenticator setup.
When to contact support
If none of the above steps solve the issue, the problem may be tied to the service provider, a corrupted vault item, or an account sync error that requires support intervention.
Contact 1Password support if the app crashes, the item disappears, or the secret fails on every device after a fresh setup.
Contact the website’s support team if the service rejects a code that you know is current, or if the account security page shows a mismatch between enrolled authenticators and active sessions.
In enterprise environments, an administrator may also need to review identity provider settings, device trust rules, or multi-factor authentication policy changes.
Quick troubleshooting checklist
- Set your device clock to automatic time.
- Confirm you opened the right login item in 1Password.
- Check that the secret synced to all devices.
- Update 1Password, your browser, and your operating system.
- Verify the website did not reset or rotate the authenticator secret.
- Re-add the account with a fresh QR code if needed.
- Use backup codes if you are locked out.
Following these steps covers the most common causes of 1Password authenticator not working and helps you restore reliable one-time password access without guesswork.