How to fix Google Authenticator not working
If Google Authenticator is failing to generate valid codes, the problem is usually tied to time drift, app setup, device changes, or account recovery settings.
This guide walks through the most reliable fixes so you can get back into your accounts without unnecessary risk.
Check whether the problem is with the app or the account
Before changing settings, confirm where the failure is happening.
A code that is rejected by one service but works on another may indicate a site-specific issue, while codes rejected everywhere usually point to a device, time, or app problem.
- If all codes fail, inspect your phone’s date and time settings.
- If only one account fails, the service may need a fresh QR setup or backup code.
- If the app opens but shows no codes, the account may have been removed or migrated incorrectly.
Fix time synchronization issues
Time mismatch is one of the most common reasons Google Authenticator stops working.
The app generates time-based one-time passwords using the current time, so even a small clock drift can make valid codes appear incorrect.
Set your device to automatic time
On Android or iPhone, make sure the phone uses network-provided date, time, and time zone settings.
Manual time settings can cause repeated login failures, especially after traveling or switching carriers.
- Open the device settings.
- Go to Date & Time.
- Enable automatic date and time.
- Enable automatic time zone if available.
Use the app’s time correction feature on Android
On Android, Google Authenticator may include a built-in time correction option.
If your codes are close but still rejected, this feature can resync the app’s internal clock with the current network time.
- Open Google Authenticator.
- Tap the menu or settings area.
- Look for Time correction for codes.
- Follow the prompts to resync.
Verify that the correct account was added
Another frequent issue is a mistaken or incomplete account entry.
If you restored the app, changed phones, or scanned a QR code twice, the wrong account may be stored or the original secret key may not match the service’s current authentication setup.
- Check the service name shown beside the code.
- Compare the account label to the login screen you are trying to access.
- Confirm whether the account uses Google Authenticator, not another authenticator app or SMS fallback.
If the code label looks unfamiliar, remove it only if you are sure you have another recovery method available.
Deleting the wrong entry can lock you out until the service issues a new setup process.
Make sure the app and phone are updated
Outdated app versions or operating system bugs can interfere with code generation, background refresh, and account transfer tools.
Updating both the app and the phone software can resolve problems that appear to be random.
- Update Google Authenticator from the App Store or Google Play.
- Install the latest iOS or Android updates.
- Restart the phone after updates to clear temporary glitches.
On some devices, battery optimization, low-power mode, or restricted background activity can prevent apps from behaving normally.
If the app seems delayed or unstable, check whether power-saving features are limiting it.
Restore access after changing phones or resetting the device
Phone migration is a major cause of authenticator issues.
If you moved to a new device without transferring accounts properly, the app may open correctly but lack the secret keys needed to create valid codes.
Use the transfer tool if you still have the old phone
Google Authenticator supports account transfer between devices.
When available, this is the safest way to move codes because it preserves the original entries instead of forcing you to re-enroll each account manually.
- Keep both phones nearby.
- Open the transfer or export option on the old device.
- Import the accounts on the new device.
- Test a login before removing the old phone.
Use backup codes or recovery options
If the original phone is lost, wiped, or damaged, the service you are trying to access may offer backup codes, recovery email, security keys, or support-assisted verification.
These options are often the fastest path back in when the authenticator app is unavailable.
- Check whether you saved backup codes during setup.
- Look for recovery links on the sign-in page.
- Use a secondary authentication method if one was configured.
Check for clock, battery, and connectivity issues
Although Google Authenticator does not usually need an internet connection to generate codes, surrounding device problems can still affect setup, syncing, and account management.
Poor connectivity can also prevent you from reaching the service’s recovery page or support tools.
- Confirm the phone has a stable network connection for account recovery.
- Restart the device if the app freezes or shows stale data.
- Charge the battery and disable extreme power-saving modes if the device behaves inconsistently.
Some users also experience issues after traveling across time zones.
In that case, re-enabling automatic time and reopening the app often fixes the problem quickly.
Re-add the account if the secret key is still available
If you still have access to the original QR code, setup key, or recovery information, removing and re-adding the account may solve a broken entry.
This is especially useful when codes were set up manually and the app stored incomplete data.
- Delete only the affected account entry.
- Start the two-factor authentication setup again from the service’s security settings.
- Scan the new QR code or enter the new key exactly as provided.
- Verify the new code before logging out of the service.
Be careful not to re-use an old setup key.
A regenerated secret from the service usually invalidates previous entries, which means the old code will no longer match.
Protect yourself before trying advanced recovery steps
If you are locked out of an important account, it is tempting to repeatedly guess codes or reinstall the app right away.
That can make recovery harder if you lose the last valid setup information.
- Take screenshots or notes of recovery options before making changes.
- Keep backup codes stored securely in a password manager or offline location.
- Avoid deleting authenticator entries unless you have a confirmed backup method.
- Contact the service provider if account access is tied to email, banking, work, or enterprise systems.
When to contact support
Some authenticator failures are not solvable from the device side.
If the app is functioning but the service rejects every code, or if you no longer have the original phone, support may need to verify your identity and reset multi-factor authentication on the account.
This is especially important for Google Workspace, Microsoft 365, banks, cryptocurrency exchanges, and other services where security policies can block access after repeated failed attempts.
Support teams may ask for identity confirmation, trusted device verification, or alternate recovery methods.
Common reasons Google Authenticator stops working
- Phone time or time zone is incorrect.
- The account was not transferred correctly to a new device.
- The service needs a fresh two-factor authentication enrollment.
- The app entry was deleted, renamed, or set up with the wrong key.
- The device has software bugs, outdated system files, or restrictive battery settings.
- Recovery codes or backup methods were never saved.
Fast checklist to try first
- Set the phone to automatic date and time.
- Restart the device.
- Update Google Authenticator and the operating system.
- Confirm the code is for the correct account.
- Use transfer tools or backup codes after a phone change.
- Contact the service provider if codes are still rejected.