Federated Credential Management (FedCM)
A browser mediated sign in that works without third party cookies or hidden redirects.
In one line
Can sign you in with the account you pick in a browser prompt
A browser mediated sign in that works without third party cookies or hidden redirects.
The browser asks the identity provider for account data, shows a prompt, and only after consent shares the ID token with the site. Stops identity providers from tracking silently. Google is moving its sign in to FedCM.
What it can and can't do
What the user does: You tap Sign in with Google (or similar) and choose an account in the browser box
It can
- Show a browser account picker listing accounts you already have with the sign in provider
- Receive a sign in token for the one account you choose
- Sign you in without third party cookies or a pop up window
It cannot
- Get your account details before you approve in the prompt
- Work in Firefox or Safari; only Chrome, Edge and Samsung Internet support it
- Pick an account for you; the prompt always asks first
How it differs between platforms: Chrome, Edge and Samsung Internet support it. Firefox and Safari do not, so sites there fall back to pop ups or redirects.
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 | No public ship found, verify |
| Safari | Not supported | Not available | Not listed | No public ship found, verify |
| 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: [...]}}) |
| Permission name | identity-credentials-get |
| Permissions policy | identity-credentials-get |
| Browser compat keys | api.IdentityCredential |
| How access is granted | prompt |
| What the user sees | Browser account chooser dialog |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Browser remembers sign in state per account; revocable in site settings |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Typical flow
- Site calls credentials.get with identity
- Browser contacts IdP, shows chooser
- Person consents
- Site receives token
Data you get
What comes back: ID token after consent
Shape: object
How often: per sign in
No individual data fields. The signal is the access itself.
Technical limits
- Needs HTTPS and a well known file at the provider
- Shows browser UI before any data is shared
- Chrome ships it; other browsers vary
The story
What it is
The browser itself runs a sign in with Google style prompt, so no hidden cookies are needed.
For you
You see a small box from your browser saying something like 'Continue as Sam' with your account picture. It appears before you type anything. You tap once and you are in.
For makers
Sites keep one click social login alive even when browsers block third party cookies. The browser, not the site, controls the prompt, so sign in rates stay high without sneaky redirects.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game portal shows a 'Continue as Sam' box so a player can sign in and load saved progress in one tap, before the game even starts. | Poki, CrazyGames |
| media | A news site lets a returning reader sign in with Google in one tap so a paywall opens and their saved articles appear. | The New York Times |
| shopping | A store shows the account chooser at checkout so a shopper skips typing an address and card details. | None named |
| productivity | A design or notes web app offers a one tap sign in the moment the page loads, so the team can jump straight into a shared board. | Figma, Notion |
| security | A site checks that the sign in came through the browser prompt, which makes fake pop up login pages harder to pass off. | None named |
| ads | Identity providers can no longer quietly learn every site you visit, because the browser asks you first and hides your visit until you agree. | None named |
Risks
- Identity provider learns you visited
- 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
- Third-party-cookie free federated login
Known abuse
- Identity providers learning relying sites
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-11, Chrome 108: FedCM shipped
- 2024-06, Chrome 126: Updates: multiple IdP and button mode (verify milestone)
Related capabilities
Related
- Sign in with Google. Can sign you in with Google and learn your name, email and photo
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
Sources
How well checked: Checked against real behavior.