Recover Google Authenticator after losing a phone
Google Authenticator can hold codes for many services, not just Google. Recovering the app is different from recovering each account whose code it generated. The key question is whether your codes were synchronized to a Google Account or existed only on the missing device.
Start with the general lost-authenticator guide if you need the overall decision tree. This page covers Google Authenticator specifically and applies to accounts you own. If the Google Account holding synchronized codes is itself inaccessible, use Google account recovery.
1. Check whether your codes were synchronized
Google's Authenticator documentation explains synchronization when the app is used with a Google Account. On a replacement device, use the official app and sign in to the same Google Account that held the codes. Confirm the account identity rather than assuming every Gmail address you own has the same entries.
Look for the expected service names and usernames. An empty list may mean you selected the wrong Google Account or that the old app was used without synchronization. Do not immediately delete entries or remove the Authenticator service while you investigate.
Google notes that deleting synchronized codes can affect other devices. Treat a visible entry as recovery material until you have confirmed a working replacement. Cleaning up an unfamiliar-looking list too early can remove the very credential you need for a service you have not checked yet.
2. Transfer from the old device if it is still available
Google's official instructions also describe manually transferring codes from an old device. This route requires access to that device and its Authenticator app. It is useful during a planned phone change or when the old phone still works despite a broken connection.
Follow the export and import steps in the app. The transfer QR code contains sensitive authentication information, so do not photograph it into a shared album or send it to someone asking to help. Scan it only into your own trusted replacement setup.
Test the resulting codes with the relevant services before removing the old installation. A successful transfer of one entry does not confirm every account was selected. Keep a private checklist of services, without copying their codes into the checklist.
3. Use each service's backup route if the codes are gone
If neither synchronization nor an accessible old device can restore the entries, the Authenticator documentation directs recovery toward the protected accounts' alternatives. Google cannot generate a Discord, Roblox, or other service's replacement ownership proof simply because its app previously held the code.
Use an unused backup code, registered security key, another configured method, or that service's official account-recovery process. Our backup-code guide helps identify the right record. Codes from one provider cannot be substituted for another provider's codes.
For your Google Account specifically, Google's backup-code instructions describe the one-time codes generated for Google two-step verification. Those codes do not restore every third-party Authenticator entry. Use them for the account named on the record and follow each other service's process separately.
If its secret existed only on the lost phone, installing Authenticator again does not recover it. The service protected by that entry must accept another configured method or its own recovery checks. Some services cannot restore access when all those methods are gone.
If the phone was stolen
Use the phone platform's official lost-device controls and review the security of the Google Account used for synchronization. After establishing another working method, remove the lost device's access through the appropriate account settings. Do not erase the only recoverable copy impulsively before considering the account and data consequences.
If you suspect an authenticator secret was exposed, reconfigure that service's two-factor setup through its official security settings after recovery. Restoring the same entry on a new phone does not automatically invalidate a copy someone else may possess.
After you regain access
Decide deliberately whether to synchronize codes and understand which Google Account stores them. Keep service-specific backup codes securely outside the missing-phone dependency. Test the replacement app against important accounts before declaring the migration finished.
Login.com's Google Authenticator setup guide helps with ordinary configuration after recovery. Label entries with recognizable account identifiers and maintain an inventory of where each service's backup method is stored. The goal is to make a future phone loss a device-replacement task instead of many separate account lockouts.
Instructions checked against vendor guidance on 24 September 2026.