Google Account QR Code: Legitimate Sign-In or Scam?

Google does use QR codes in some legitimate sign-in and passkey flows. The code alone does not prove that a message or page is genuine. Check whether you started the sign-in, where the code appeared, and what your phone asks you to approve.

When a Google Account QR code can be legitimate

Google says it may show a QR code as an extra step when you sign in on a new device. You scan it with a phone or tablet where you are already signed in to the same Google Account, then follow the instructions on that device. Google also documents a QR code for signing in on a computer with a passkey stored on your phone.

Review Google's current QR sign-in instructions and passkey sign-in instructions. A normal pattern is that you start the Google sign-in on one device, the QR code appears there, and your already signed-in or passkey-enabled phone asks you to finish that same action.

An unexpected QR code in an email, text, attachment, chat, or support message does not have that context. Do not treat Google branding, a sender name, or a familiar-looking address as proof of the whole request.

Check the context before you continue

  1. Ask whether you started the sign-in. A QR code on the Google sign-in screen you just opened is different from one pushed to you in a message.
  2. Keep both devices in view. The account and action shown on your phone should match the sign-in you began on the other device. Stop if the request is unexpected or the details do not match.
  3. Do not share the code or approval. Someone who contacts you unexpectedly should not direct your sign-in, request a screenshot of the code, or tell you which prompts to approve.
  4. Open Google independently if you are unsure. Type myaccount.google.com yourself or use a Google app you already trust. Do not return through the message, attachment, or support pop-up.
  5. Use another sign-in method when needed. Google provides a "Try another way" option if you cannot scan the QR code or do not want to use that flow.

The FTC recommends avoiding unexpected QR codes that create urgency and contacting the organization through a website or number you already know. See the FTC's QR phishing guidance.

What to do after you scanned or approved it

Match the response to the action you completed. Scanning a code and closing it is different from entering a password, approving a passkey sign-in, granting app access, or installing software.

  • You only scanned it: close the page or prompt. Open your Google Account directly and review recent security events if the code was unexpected. Scanning alone does not establish that your account was accessed.
  • You entered your password: change your Google password from the account page you opened independently. Change it anywhere else you reused it, then review security events and devices.
  • You approved a sign-in or passkey request: review the passkeys and security keys in your Google Account, remove anything you do not recognize, and sign out unfamiliar devices.
  • You granted an app access: review your Google Account's linked apps and remove the connection if you did not intend to authorize it.
  • You cannot sign in or see unfamiliar activity: use Google's account recovery and compromised-account guidance. Do not pay or call a number supplied by the QR page.
  • You installed something: remove software or browser extensions you do not trust, update the device, and run a security scan before changing passwords from that device.

Google's compromised-account guide covers recovery, recent activity, devices, passwords, and suspicious settings. Its linked-app guide explains how to review and remove third-party access.

What QRsafer can and cannot check

QRsafer can help decode a QR code that contains a normal web destination and let you review that destination before opening it. That can help with an unexpected link, but a familiar domain is only one signal and does not prove that the complete request is appropriate.

QRsafer cannot authenticate Google, the sender, the account, a passkey request, a device-to-device sign-in session, or future page behavior. A Google sign-in QR code may not be an ordinary website link, so verify the account action inside the Google flow you started.

Frequently asked questions

Does Google use QR codes to sign in?

Yes. Google documents QR codes as an extra verification step during some sign-ins and for using a phone's passkey to sign in on a computer. The code is more credible when it appears on the device where you just started a Google sign-in and your already signed-in phone asks you to finish that same action.

Does a Google-looking QR code prove the sign-in is legitimate?

No. A logo, familiar design, sender name, or recognizable URL fragment does not prove the complete request is genuine. If you did not start the sign-in, stop and open your Google Account directly rather than using the message or code.

What if I entered my Google password after scanning?

Open your Google Account directly, change the password, review recent security events and signed-in devices, and change any other account that reused the same password. If you cannot sign in, use Google's account recovery page.

Can QRsafer verify a Google sign-in QR code?

QRsafer can help decode and review a QR code that contains a normal web link. It cannot authenticate Google, a sender, an account, a passkey request, a sign-in session, or what a page will do later. Some Google sign-in QR codes are part of a device-to-device flow rather than an ordinary website link.

Review web-link QR codes before opening them

QRsafer can decode web-link QR codes and let you review the destination first. Verify Google sign-in and passkey requests through the Google flow you started.

See also