FedCM (Federated Credential Management)
Lets a site ask the browser to sign the person in with Google, Apple or similar without third party cookies.
In one line
Can sign you in with Google, Apple or similar using a browser account picker
Lets a site ask the browser to sign the person in with Google, Apple or similar without third party cookies.
Gives the site an ID token for a chosen identity provider account; the browser mediates the prompt.
What it can and can't do
What the user does: You tap Sign in with Google (or similar) or answer a prompt that appears on the page
It can
- Show a browser box listing accounts you have with a sign in provider
- Receive a sign in token for the account you choose
- Show the prompt on the page itself or after you tap a button
It cannot
- Get your account details before you approve
- Work in Firefox or Safari
- Use third party cookies to track you quietly between sites
How it differs between platforms: Chrome, Edge and Samsung Internet support it. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 108 | 2022-11-29 | None |
| Edge | Supported | 108 | 2022-12-05 | None |
| Firefox | Not supported | Not available | Not listed | Login Status only (138) |
| Safari | Not supported | Not available | Not listed | identity_option member in 27; no IdentityCredential |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 108 | 2022-11-29 | None |
| Samsung Internet | Supported | 21.0 | 2023-05-19 | None |
How a site asks for it
| API | navigator.credentials.get({identity:{providers:[{configURL,clientId,nonce}],mode:'active'|'passive'}}); navigator.login.setStatus('logged-in') |
| Permissions policy | identity-credentials-get |
| Browser compat keys | api.IdentityCredential |
| How access is granted | prompt |
| What the user sees | Browser account chooser (passive in the page or active after a click) |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Lets a site ask the browser to sign the person in with Google, Apple or similar without third party cookies.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
token | string | None | JWT or structured JSON (143) | Not listed |
isAutoSelected | boolean | None | true or false | Not listed |
accounts | list | None | name, email, picture | only shown in the browser UI |
Technical limits
- Chrome and Edge only; Firefox and Safari not shipped (Firefox ships Login Status 138)
- IdP Registration, Fields API and multiple IdPs still on the roadmap
- Safari 27 has options members but no IdentityCredential
The story
What it is
A browser run login box that signs you in with Google, Apple or similar, with no cookie tricks.
For you
You see a small prompt from the browser offering to continue as your account. You tap to agree. Nothing happens until you do.
For makers
Makers keep one tap social login working as third party cookies go away. Sign in conversion stays high and the browser enforces privacy rules for them.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A web game portal shows a prompt so a player signs in and loads a saved profile at once. | Poki |
| media | A streaming site offers one tap sign in so a viewer resumes where they stopped. | None named |
| shopping | A store shows the prompt on page load so returning customers reach saved carts faster. | None named |
| news | A news site uses it to recognize subscribers and skip the paywall. | None named |
| productivity | A web app embeds the prompt in a sidebar so teammates can join a shared document fast. | None named |
| ads | Ad and measurement partners lose the old hidden login cookie link, so a visit can no longer be quietly matched to a Google account. | None named |
Risks
- Identity provider may see your visits
- Prompt fatigue
What the platform says
- Google Chrome: Federated Credential Management. Chrome pitches it as keeping one click sign in alive as third party cookies fade, with the browser running the prompt.
- MDN (standards docs): FedCM API. Describes a browser mediated way for people to sign in to sites using an identity provider, without tracking by cookies or redirects.
Good uses and abuse
Legitimate uses
- Sign in with Google
- Delegated login
Known abuse
- IdP learns which RP the person visits
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 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-12, Chrome 108: FedCM ships
- 2023-11, Chrome 120: Login Status API and isAutoSelected
- 2026-01, Chrome 143: Structured JSON token accepted, stricter client metadata checks
- 2026-03, Chrome 145: accounts_endpoint enforced, IdentityCredentialError.code renamed to error
Sources
How well checked: Checked against real behavior.