How to use Google Authenticator

Key takeaways

  • Google Authenticator generates one-time codes from a shared secret and the current time, works without mobile service, and avoids SIM-swap risks of text-message codes.
  • Enable 2-Step Verification in your Google Account first, then scan each service's QR code, save recovery codes, and treat setup keys as sensitive.
  • To move to a new phone, sign in with the same Google Account for synced codes, or export and import them, then test before wiping.
  • Backup codes work once and a new set invalidates the old one, and you should never read a verification code to an unexpected caller.

Google Authenticator is a mobile app that generates one-time verification codes for accounts that support authenticator-based sign-in. It adds a second check alongside your password, and its codes work without mobile service or an internet connection. This article explains how to use Google Authenticator, connect accounts, transfer codes, and prepare for losing access to your phone. (google.com)

How does Google Authenticator protect your accounts?

Google Authenticator supports two-factor authentication by supplying a verification code in addition to your password. Someone who steals your password still needs to complete that second step to sign in. That extra requirement helps protect an account when its password is compromised. (support.google.com)

For time-based codes, the app and the service use a shared secret and the current time to calculate matching values. The code changes as each time interval passes, so it is not a permanent password you need to memorize. This also explains why an incorrect phone clock can cause otherwise valid-looking codes to fail. (rfc-editor.org)

Unlike text-message verification, an authenticator app does not depend on receiving a code through your phone number. The Federal Trade Commission notes that app-generated codes avoid risks such as SIM-swap attacks against text-message verification. They are not, however, permission to ignore suspicious websites or unexpected requests for codes. (consumer.ftc.gov)

Set up Google Authenticator and connect your first account

Start by installing Google Authenticator from Google Play or Apple’s App Store, checking that the publisher is Google LLC. The app supports multiple accounts, so you can keep codes for different compatible services together. Installing it is only the beginning: each service needs its own enrollment process. (google.com)

Complete your Google 2FA setup

For a Google Account, begin in the account’s security settings rather than inside the Authenticator app. Open Security & sign-in, find How you sign in to Google, and select 2-Step Verification. Follow Google’s instructions to enable it if it is not already active. Work or school accounts may require help from an administrator. (support.google.com)

Then open the Authenticator option in your Google Account’s 2-Step Verification settings and choose Set up authenticator. Follow the displayed instructions to connect the app. Google notes that a newly added Authenticator method can take up to seven days to become available for sign-in, so keep your existing verification options accessible. (support.google.com)

Add other compatible services

For another website or app, open that service’s security settings and choose its authenticator-app option. The enrollment flow generally asks you to connect the app and confirm a generated code. For example, Hawaii’s official account instructions use this sequence: (my.hawaii.gov)

  1. Display the setup QR code on the service’s registration screen.
  2. Open Google Authenticator and tap the plus button to add an account.
  3. Choose Scan a QR code and allow camera access if requested.
  4. Scan the service’s QR code, then locate the new account entry.
  5. Enter the generated verification code on the service’s setup screen.
  6. Save any recovery codes offered before finishing enrollment. (my.hawaii.gov)

Treat setup keys and enrollment QR codes as sensitive credentials. They contain the information needed to generate verification codes, rather than just an account label. Avoid including real enrollment codes in screenshots you share for troubleshooting. (rfc-editor.org)

Use the Google Authenticator app during everyday sign-ins

Once enrollment is complete, learning how to use the Google Authenticator app is straightforward: sign in to the service, open Authenticator when a verification code is requested, and enter the code for that account. You do not need to scan the setup QR code every time. Enrollment connects the app; subsequent sign-ins use its generated codes. (my.hawaii.gov)

Check the account label carefully if you have several entries for the same service. Use the current code before it expires; if it is nearly expired, wait for the next one. Authenticator can generate codes offline, although accessing the website itself still requires a connection. (support.google.com)

Google may offer another verification method, such as a prompt or passkey, instead of requesting an Authenticator code. That does not necessarily mean your setup failed: Google selects sign-in challenges based on the situation. Follow the legitimate account sign-in screen rather than expecting an identical sequence every time. (support.google.com)

How do you transfer Google Authenticator to a new phone?

You can transfer Google Authenticator codes through Google Account synchronization or by manually exporting them from your old device and importing them on the new one. Synchronization requires previously saved codes in the relevant Google Account; manual transfer requires access to the old phone. Check which arrangement you use before replacing your device. (support.google.com)

Restore synchronized codes

If your codes are synchronized, install Authenticator on the new device and sign in within the app using the same Google Account. Your saved codes synchronize to that device. Google introduced this feature to make codes available across devices and reduce lockout problems when a phone is lost. (security.googleblog.com)

Keep another way to access that Google Account. Otherwise, you could need a code from the very app you are trying to restore. A previously configured security key, passkey on another device, or saved backup code can provide an alternative sign-in route. (support.google.com)

Transfer codes manually

To use Google Authenticator’s transfer feature without relying on synchronization, keep both phones available and update the app on the old device. Then follow this process: (support.google.com)

  1. On the old phone, open the menu and select Transfer codes or Transfer accounts, then Export.
  2. Unlock the device when requested and select the accounts to move.
  3. Generate the transfer QR code or codes.
  4. On the new phone, open the transfer menu and choose Import.
  5. Scan every generated QR code and check for transfer confirmation. (support.google.com)

As a final precaution, test sign-ins with the new phone before wiping or trading in the old one. Make this a separate check, not an assumption based on seeing account names appear.

How can you use Google Authenticator on a PC?

The straightforward way to use Google Authenticator on a PC is to sign in through the computer’s browser while generating the verification code on your phone. Display the enrollment QR code on the computer during setup, scan it with the mobile app, and enter phone-generated codes into the browser afterward. (my.hawaii.gov)

Distinguish that workflow from installing a desktop authenticator. Login.gov lists Google Authenticator among its Android and iOS options, while listing different products for Windows, Mac, and browser extensions. A desktop tool with “Authenticator” in its name should not automatically be treated as Google’s mobile app. (login.gov)

If phone-free sign-in is your goal, investigate whether the account supports passkeys. Google supports passkeys on compatible computers, allowing authentication using a supported device-unlock method. This is a different sign-in approach, not a desktop version of Google Authenticator. (support.google.com)

Prevent lockouts and troubleshoot rejected codes

Before relying on Authenticator, create an independent recovery route. For Google Accounts, backup codes can replace your normal second step when it is unavailable. Each code works once, and generating a new set invalidates the old set. Store them somewhere secure that you can access without the missing phone. (support.google.com)

Use this checklist when something goes wrong:

  • Rejected code: Verify the service and account label, wait for a fresh code, and check that your phone’s date and time are correct.
  • Missing entries: Check which Google Account is selected and whether the codes were stored without an account.
  • Lost phone: Use a previously configured alternative verification method or the service’s account-recovery process.
  • Stolen phone: Secure the affected account and sign out the missing device; Google also recommends changing your Google Account password. (support.google.com)

Keep verification codes private

Never read a verification code to an unexpected caller or send it in response to an unsolicited message. Google warns that scammers request these codes to take over accounts and that Google will not call to verify one. Enter codes only during a sign-in you initiated on the genuine service. (support.google.com)

Authenticator codes improve security, but passkeys offer stronger phishing protection because they are tied to the legitimate website rather than manually entered into a page. Consider them where supported. (developer.mozilla.org)

Start with one important account, complete enrollment, and save its recovery options. Then test the full sign-in process before expanding to other accounts. The goal is protection you can confidently use—and recover when your devices change.

Sources

  1. Google Mobile
  2. Turn on 2-Step Verification - Computer - Google Account Help
  3. RFC 6238: TOTP: Time-Based One-Time Password Algorithm | RFC Editor
  4. consumer.ftc.gov: Use two factor authentication protect your accounts
  5. Get verification codes with Google Authenticator - iPhone & iPad - Google Account Help
  6. Set Up Google Authenticator for MFA – myHawaii Citizen Identity Initiative
  7. Get verification codes with Google Authenticator - Android phone & tablet - Google Account Help
  8. Google Online Security Blog: Google Authenticator now supports Google Account synchronization
  9. Fix common issues with 2-Step Verification - Google Account Help
  10. Authentication application | Login.gov
  11. support.google.com
  12. support.google.com
  13. Phishing - Security | MDN