Google Authenticator Not Working? How to Fix It (2026 Guide)

You open Google Authenticator, type in the six‑digit code, and the website tells you it’s wrong. You try again with a fresh code — still wrong. It’s one of the most stressful tech problems there is, because a broken authenticator can lock you out of your email, your bank, and dozens of other accounts at the worst possible moment.

Here’s the good news: in the overwhelming majority of cases, Google Authenticator isn’t actually broken, and neither is your account. The codes are being rejected for one simple reason — your phone’s clock is even slightly out of sync. This guide walks through the single most common fix first (it takes about 30 seconds), then covers every other reason the app can fail and exactly how to recover if you’re already locked out.

Why Google Authenticator Codes Stop Working

Google Authenticator generates what are called TOTP codes — Time‑based One‑Time Passwords. The app doesn’t talk to the internet or to Google’s servers to get each code. Instead, it combines a secret key (set up when you first scanned the QR code) with the current time to mathematically produce a new six‑digit number every 30 seconds.

The website you’re logging into runs the exact same calculation on its end. As long as both clocks agree, both sides produce the same number and you get in. But if your phone’s clock drifts even a minute or two away from real time, your phone produces a number for the “wrong” 30‑second window — and the server rejects it as invalid. Nothing is corrupted; the math is simply being done at two different moments in time.

This is why the fixes below are almost entirely about time, and why the number‑one solution — setting your clock to automatic — resolves the problem for most people.

Fix #1: Set Your Phone’s Time to Automatic (The Top Solution)

This is the fix that works for the vast majority of “invalid code” complaints, and it’s the very first thing you should check. The culprit is almost always a manually set clock. People most often run into this while traveling to another country: you land, your phone hasn’t caught the new time zone yet, so you change the time by hand to match the wall clock — and from that moment your TOTP codes silently break. Even a manual change of a couple of minutes is enough.

The solution is to stop setting the time yourself and let your phone sync it automatically from the network, which is accurate to the second.

On iPhone (iOS)

Open the Settings app.
Tap General.
Tap Date & Time.
Turn Set Automatically ON (the toggle should be green).
If it was already on, turn it off, wait five seconds, then turn it back on to force a fresh sync.
Confirm the Time Zone shown just below matches where you actually are. If it’s greyed out, that’s normal — it’s being set automatically.

Now reopen Google Authenticator and try a fresh code. In most cases it works immediately.

On Android

Open the Settings app.
Go to System → Date & time (on Samsung: General management → Date and time).
Turn on Automatic date & time (sometimes labeled “Use network‑provided time”).
Turn on Automatic time zone as well.
If they were already on, toggle them off and back on to force a re‑sync.

The Android shortcut: “Time correction for codes”

The Android version of Google Authenticator has a built‑in tool that re‑syncs the app’s internal clock without touching your phone’s system settings. It does not change your phone’s displayed time — it only corrects the time the app uses to generate codes:

Open Google Authenticator.
Tap the three‑dot menu in the top‑right corner.
Tap Settings.
Tap Time correction for codes.
Tap Sync now. You’ll see a confirmation that the time has been synced.

Your codes will work right away after syncing. (Note: this specific option lives in the Android app; on iPhone you fix the clock through iOS Settings as described above.)

Fix #2: Force a Time Sync If Automatic Is Already On

Sometimes “Set Automatically” is already enabled but the clock still drifted — usually after a long flight, a dead battery, or a region with a weak cellular signal. The fix is to force the phone to re‑fetch the time:

Toggle it off and on: In Date & Time, switch automatic time off, wait a few seconds, then switch it back on.
Change time zones manually, then back to automatic: This nudges the system to pull a fresh time from the network.
Connect to Wi‑Fi or move to better signal: Your phone needs a network connection to fetch accurate time.
Restart the phone: A reboot forces a clean time sync on startup (see Fix #6).

Fix #3: Check Your Internet Connection

Google Authenticator generates codes offline, so the app itself doesn’t need data. But your phone does need a connection to keep its clock accurate, and the website you’re logging into obviously needs to be reachable. If you’re on airplane mode, a captive hotel Wi‑Fi that hasn’t been authorized, or a dead zone, your clock can drift and your login can fail for reasons that look identical to a bad code. Make sure you have a working connection, then retry.

Fix #4: Update or Reinstall the App

An outdated app can misbehave, especially after a major iOS or Android update.

iPhone: Open the App Store, search for Google Authenticator, and tap Update if it’s available.
Android: Open the Play Store, search for Google Authenticator, and tap Update.

Important warning before you reinstall: Do not delete and reinstall Google Authenticator to “fix” it unless you have backups. If your accounts aren’t synced to your Google account (a newer feature) or saved as backup/transfer codes, deleting the app erases your authenticator secrets and you can lock yourself out. Update from the store rather than uninstalling whenever possible.

Fix #5: Make Sure You Enter the Code Before It Expires

Each code is valid for only 30 seconds — that’s the colored timer (or shrinking circle) next to it. If you start typing a code with only two or three seconds left, it may expire by the time you hit submit, and the site will reject it. Wait for a fresh code at the start of its cycle and enter it promptly. Also double‑check you’re reading the code for the correct account if you have several listed.

Fix #6: Restart Your Phone

A simple reboot clears temporary glitches and forces your phone to re‑sync its clock with the network the moment it powers back on. It sounds basic, but after the automatic‑time fix, restarting is the second most reliable way to clear a stubborn time drift. Power your phone fully off, wait about ten seconds, turn it back on, then try a new code.

Fix #7: If Codes Still Fail — How to Recover Access

If you’ve corrected the time and codes are still rejected, the problem may be on the account side rather than the app. Here’s how to get back in:

Use your backup codes. Most services (Google, Microsoft, banks, crypto exchanges) give you a set of one‑time backup codes when you first enable two‑factor authentication. Look for the “Use a backup code” or “Try another way” link on the login screen.
Use account recovery. For a Google account, go to the Google Account Recovery page and follow the prompts to verify your identity another way.
Try another 2FA method. Many sites let you fall back to SMS, email, a security key, or a prompt on a trusted device.
Restore from a transfer or backup. If you recently switched phones, your codes may not have transferred. On the old phone, use Transfer accounts → Export accounts in Google Authenticator to move them, or sign in to sync them to your Google account.
Contact the service’s support. As a last resort, the account provider (not Google) can help you regain access after identity verification.

Quick Troubleshooting Checklist

Symptom	Most Likely Cause	Fix
Every code is rejected, started after travel	Clock set manually / wrong time zone	Fix #1 — set time to automatic
Codes worked yesterday, fail today	Clock drifted over time	Fix #2 — force a time re‑sync
Codes fail only on hotel/public Wi‑Fi	No real network time / captive portal	Fix #3 — verify connection
App crashes or looks broken after an update	Outdated app	Fix #4 — update (don’t delete)
Code rejected only sometimes	Entering it too close to expiry	Fix #5 — use a fresh code
Nothing works after fixing the time	Account‑side or phone‑transfer issue	Fix #7 — recover access

How to Prevent This From Happening Again

Always leave “Set Automatically” on. Never set your phone’s time by hand, even when traveling — let it sync to the local network instead.
Save your backup codes somewhere safe (a password manager is ideal) the moment you enable 2FA on any account.
Turn on cloud sync in Google Authenticator so your codes are tied to your Google account and survive a lost or replaced phone.
Before switching phones, use the app’s Transfer accounts feature to move your codes to the new device.

Frequently Asked Questions

Why does Google Authenticator say my code is invalid even though I typed it correctly?

Almost always because your phone’s clock is out of sync with real time. The app builds each code from the current time, so a clock that’s off by even a minute produces codes the server rejects. Setting your time to automatic (Fix #1) resolves it in most cases.

Does Google Authenticator need the internet to work?

No — it generates codes completely offline. However, your phone needs a network connection to keep its clock accurate, and an inaccurate clock is the leading cause of failed codes.

Why did my codes break right after I traveled abroad?

When you arrive in a new country, your phone may not immediately update the time zone, so many people set the time manually to match the local clock. That manual change throws off the time‑based code calculation. Switch “Set Automatically” back on and the codes will work again.

Will fixing the time delete my accounts in the app?

No. Changing your phone’s clock or using “Time correction for codes” does not touch your saved accounts — it only realigns the time used to generate codes. (Deleting/uninstalling the app, on the other hand, can erase them if you have no backup.)

I lost my phone — how do I get my codes back?

Use the backup codes you saved when setting up 2FA, or your account provider’s recovery process. Going forward, enable Google Authenticator’s cloud sync so your codes are backed up to your Google account automatically.

The Bottom Line

When Google Authenticator stops working, resist the urge to delete the app or assume your accounts are compromised. Nine times out of ten the real problem is a clock that’s a minute or two off — most often because the time was set manually after a trip. Turn on automatic time, force a quick re‑sync, and your codes should start working again within seconds. Keep automatic time enabled and your backup codes saved, and you’ll rarely run into this again.

Google Authenticator Not Working? How to Fix It (Start With Your Phone’s Clock)