Google Authenticator Not Working — Fix Guide | 2faco

If your Google Authenticator codes are not working, you are not alone. Invalid or expired 2FA codes are one of the most common authentication problems. This guide explains the most common causes and how to fix them step-by-step.

Common Reasons Google Authenticator Fails

1. Time Sync Is Incorrect

Authenticator apps rely on your device’s time being perfectly synced. If your phone clock is even a few seconds off, the generated code may be rejected.

• Enable automatic date and time in device settings
• Restart your device
• Ensure timezone is correct

2. Code Has Expired

Each code is valid for only 30 seconds. If you wait too long before entering it, the login attempt will fail.

3. Wrong Account Selected

If you have multiple accounts saved, make sure you are using the correct one.

4. Secret Key Was Entered Incorrectly

If the account was manually added and the secret key was mistyped, codes will never match.

Quick Fix: The 30-Second Checklist

Before diving into the longer fixes, run through this checklist. It resolves the majority of cases:

1. Check the code is still valid — codes expire every 30 seconds. If it changed while you were typing, re-enter it from the top.
2. Check the clock — your phone must be set to automatic date and time. A drift of even one minute invalidates codes.
3. Check you're on the right account — with multiple accounts saved, it's easy to copy a code from the wrong one.
4. Check the field — some sites expect the code without spaces, others reject codes pasted with a trailing space.
5. Refresh the page and retry — occasionally a session glitch or an auto-filled password field eats the code.

How to Fix Time Sync Errors

On Android:

• Open Google Authenticator
• Go to Settings
• Select “Time correction for codes”
• Tap “Sync now”

On iPhone:

• Go to Settings → General → Date & Time
• Enable “Set Automatically”

What If You Lost Your Phone?

If you lost your device and cannot access your authenticator app:

• Use backup codes provided during setup
• Use a previously registered device
• Contact the service provider for identity verification

For detailed recovery steps, see our guide: Lost Phone With 2FA Enabled.

Wrong Account Selected or Mistyped Secret Key

If none of the above fixes resolve the issue:

• Double-check the original QR code or secret key
• Disable and re-enable 2FA on the account (if possible)
• Ensure no VPN or firewall is interfering

Google Authenticator App Crashes or Won't Open

If the Google Authenticator app itself is crashing or failing to load, try these steps:

1. Force stop the app — On Android: Settings → Apps → Google Authenticator → Force Stop. Relaunch it.
2. Clear the app cache — On Android: Settings → Apps → Google Authenticator → Storage → Clear Cache. This does not delete your accounts, only temporary files.
3. Update the app — An outdated version may have compatibility issues. Check the Play Store or App Store for updates.
4. Reinstall only as a last resort — Uninstalling Google Authenticator without first exporting your accounts will lock you out. If reinstalling is necessary, export accounts first (three dots → Transfer accounts → Export accounts).

Transferring Google Authenticator to a New Phone

Google Authenticator syncs to your Google Account by default since the 2023 update. If you are signed in to your Google Account in the app, your codes should restore automatically on a new device after signing in.

If automatic sync is off, use the built-in transfer feature:

1. On your old phone: open Google Authenticator, tap the three-dot menu, select Transfer accounts → Export accounts.
2. Choose the accounts to transfer and tap Next. A QR code is generated.
3. On your new phone: open Google Authenticator, tap the three-dot menu, select Transfer accounts → Import accounts, and scan the QR code.

If you no longer have access to your old phone, you will need to use backup codes for each service or go through account recovery.

Re-Enrol Google Authenticator From Scratch

If nothing else works, the most reliable fix is to remove Google Authenticator from an account and re-add it. This process varies by service but is generally:

1. Sign in to the account using a backup code (saved when you first set up 2FA) or through the account recovery process.
2. Go to Security settings and disable two-factor authentication temporarily.
3. Re-enable 2FA and scan the fresh QR code with Google Authenticator.
4. Save the new backup codes.

This is time-consuming if you have many accounts set up, but it fully resets the authenticator and eliminates any sync or configuration issues.

Less Common Causes Worth Checking

If the fixes above don't help, the problem is usually one of these:

• Wrong timezone on the website's side — your phone may be fine but the service you're logging into may be computing codes against a wrong server clock. Retry after a few minutes, or contact the service's support.
• Code entered into the wrong field — some sites ask for a one-time code from email or SMS in a separate step. Make sure you're entering the authenticator code, not an email or SMS code.
• A VPN or network proxy — extremely rare, but a misconfigured proxy can route you to a cached version of the login page with an old timestamp. Try logging in on a different network.
• Account recently re-enrolled — if you scanned a new QR code for the same account, the old one is dead. Delete the duplicate entry and keep only the newest.
• Clock is set to a non-automatic zone — even with "Set Automatically" on, some Android devices drift if the network time source is wrong. Reboot the phone after changing time settings.

How to Prevent This From Happening Again

The single best protection is to store your setup keys somewhere safe. When you enable 2FA on any account, most services show a secret key or QR code once — that key can regenerate valid codes forever. Saving it in a password manager (or printing it and storing it in a safe place) means you can re-add Google Authenticator at any time without contacting support.

Beyond that, keep these habits:

• Save the backup codes every time you set up a new account — they are the escape hatch when nothing else works.
• Enable Google Authenticator's cloud backup (sign in with your Google Account) so codes survive phone changes.
• Keep the app updated. Outdated versions can misbehave with newer device clocks.
• Test a code from a new setup before closing the setup page — this catches mis-typed keys immediately.

For a full breakdown of why codes stop matching and how to fix every case, see 2FA codes out of sync. If you're switching to a new phone entirely, follow how to transfer Google Authenticator first.

Google Authenticator FAQ

Why did Google Authenticator stop working for no reason?

Almost always a clock problem. Phone clocks drift slightly over time, and Google Authenticator's codes are generated from the current time. Re-syncing the clock (Settings → "Time correction for codes" → "Sync now" on Android, or enabling "Set Automatically" on iPhone) fixes it in seconds.

Does uninstalling Google Authenticator delete my codes?

If cloud backup is enabled and you're signed in with your Google Account, codes can be restored on a new device. If not, uninstalling without exporting accounts first will lock you out of every service — always export accounts before reinstalling.

Can I use Google Authenticator on two phones at once?

Yes. Scan the same QR code (or enter the same secret key) on both devices. Both will generate identical codes, which is a handy backup strategy. Avoid this if you share the device with others.

Is Google Authenticator safe to use?

Yes — it is one of the most widely used authenticator apps in the world and generates codes entirely on-device. For a deeper look, including privacy considerations, see is Google Authenticator safe.

Security Reminder

Never share your secret key or backup codes with anyone. Legitimate services will never ask for your 2FA code outside the login process.

Codes Work in One App But Not Another — Why?

If Google Authenticator's codes fail on one site while a different authenticator app works on the same account, the secret keys are almost certainly different. This happens when a service displays a new QR code between attempts, or when the secret was pasted with a hidden space. Each app stores its own key copy, so a mistyped key in one app makes that app's codes wrong.

Fix it by re-scanning the QR code exactly as the service provides it. If the service lets you enter a key manually, copy it as plain text to avoid invisible formatting. Then test both apps at the same moment.

When the Website Is the Problem

Not every 2FA failure comes from your phone. Some sites expire codes within 30 seconds instead of 30, or reject codes that are typed as the counter ticks over. If the code looks right but the page rejects it, wait for the next window and type the code within the first ten seconds.

Also check how the site expects the code: some forms insert dashes automatically, and a few only accept the code from the method you chose during setup. If you switched from SMS, log in with backup codes and confirm the 2FA method is set to the authenticator app.