Sign in with Google
A one click login where Google tells the site who the person is.
In one line
Can sign you in with Google and learn your name, email and photo
A one click login where Google tells the site who the person is.
The site gets a signed ID token with sub (stable user ID), email, email_verified, name, picture, locale and for Workspace users the hd domain. Extra scopes can add Calendar, Drive or Contacts. The site gets the same sub every visit.
What it can and can't do
What the user does: You tap Sign in with Google and pick an account in the Google box
It can
- Receive a Google ID that stays the same each time you visit
- Get your name, email, profile photo and language
- Learn your company domain when you use a Workspace account
- Ask for extra access such as Calendar, Drive or Contacts on a second screen
It cannot
- Get your Google password
- See your Calendar, Drive or Contacts unless you approve that extra access
- See your email inbox without a separate approval
- Sign in without you picking an account
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | :Redirect or popup, works in all browsers |
| Edge | Supported | 1 | Not listed | :Redirect or popup, works in all browsers |
| Firefox | Supported | 1 | 2004-11-09 | :Redirect or popup, works in all browsers |
| Safari | Supported | 1 | 2003-06-23 | :Redirect or popup, works in all browsers |
| Safari on iPhone | Supported | 1 | 2007-06-29 | :Redirect or popup, works in all browsers |
| Chrome on Android | Supported | 1 | Not listed | :Redirect or popup, works in all browsers |
| Samsung Internet | Supported | 1 | 2013-04-27 | :Redirect or popup, works in all browsers |
How a site asks for it
| API | Google Identity Services: google.accounts.id.initialize(); OIDC id_token |
| How access is granted | prompt |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Google session cookies keep the person signed in; site stores its own session |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Typical flow
- Person clicks Sign in with Google
- Google shows account chooser
- Site receives ID token
- Site creates its account or session
Data you get
What comes back: ID token claims
Shape: object
How often: at sign in
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
sub | string | id | up to 255 chars | exact |
email | string | address | any | exact |
email_verified | boolean | none | true or false | exact |
Technical limits
- Default scopes are openid, email and profile
- ID token expires after 1 hour
- Google also sees every site the person signs in to
- Third-party cookie free path via FedCM
The story
What it is
A one click login where Google tells the site who you are.
For you
You click a Google button, pick your account and agree. The site now knows your name, photo and email. Next time it may offer a one tap box right when the page loads.
For makers
Makers skip building password systems and get a verified email. They get a stable user ID and a profile picture for personalizing the app, and sign ups are faster, which improves conversion.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A web game lets a player sign in with Google so scores, skins and a friends leaderboard follow them to a new laptop. | Google Play Games on PC, CrazyGames |
| games | A cloud gaming service such as GeForce NOW offers account sign in options so a person can start streaming a game on any browser. | GeForce NOW |
| productivity | An online editor reads the sign in token to open a person's own files and show their picture on live cursors. | Figma, Canva, Notion |
| shopping | A store gets a verified email at checkout, so receipts and order tracking work with no extra form. | None named |
| education | A school web app uses the Workspace domain claim to let only students and teachers of that school in. | Google Classroom, Khan Academy |
| analytics | A growth team counts new accounts made with Google versus email to tune the sign up page. | None named |
| security | A site can block throwaway sign ups because Google already checked that the email is real. | None named |
Risks
- Google sees where you sign in
- If the Google account is lost, so are the logins
What the platform says
- Google: Sign in with Google. Google pitches a quick, secure sign in using an account people already have, with one tap on web and mobile.
Good uses and abuse
Legitimate uses
- Frictionless sign up and login
Known abuse
- Google learning every site the person uses; email address given to site
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-08, all: Google Identity Services replaced Google Sign-In JS library
- 2025-01, Chrome 132: GIS One Tap uses FedCM by default (verify exact milestone)
Related capabilities
Related
- Federated Credential Management (FedCM). Can sign you in with the account you pick in a browser prompt
- Sign in with Apple. Can sign you in with Apple and get a real or hidden email address
Sources
How well checked: Based on official documentation.