Credential Management (password and federated)
Lets a site store and fetch saved passwords through the browser.
In one line
Can fetch a saved login after you pick an account in a browser sheet
Lets a site store and fetch saved passwords through the browser.
Gets a stored username and password after the person picks an account, without scraping form fields.
What it can and can't do
What the user does: You tap the username box or Sign in and choose an account from the sheet
It can
- Show saved accounts for that site in a chooser
- Receive the username and password for the account you pick
- Sign you in again next time if you turned on auto sign in
It cannot
- See saved logins for other sites
- Get a password without the chooser, unless you allowed auto sign in
- Work in Firefox or Safari; those use built in autofill instead
How it differs between platforms: Chrome and Edge support it. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 51 | 2016-05-25 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Not supported | Not available | Not listed | Only navigator.credentials basic (60), no PasswordCredential |
| Safari | Not supported | Not available | Not listed | navigator.credentials basic (13); no PasswordCredential |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 51 | 2016-06-08 | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | navigator.credentials.store(new PasswordCredential()), navigator.credentials.get({password:true}), preventSilentAccess() |
| Browser compat keys | api.PasswordCredential |
| How access is granted | prompt |
| What the user sees | Account chooser sheet; auto sign in option |
| 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 store and fetch saved passwords through the browser.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
id | string | None | username | Not listed |
password | string | None | stored secret | only for the selected entry |
name, iconURL | string | None | Not listed | Not listed |
Technical limits
- PasswordCredential only in Chromium
- Firefox and Safari lack PasswordCredential
- No bulk password read
The story
What it is
Lets a site save and fetch your login through the browser.
For you
You may see a small chooser listing your saved accounts, or you may be signed in with no typing at all. After sign up the browser may ask to save your login.
For makers
Makers get smoother sign in without reading form fields by hand. Auto sign in lifts returning visitor rates, which matters for shops, media and games that need the person logged in.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A returning player opens a browser game and is signed in automatically, so the lobby loads with their name and stats. | None named |
| shopping | A shop's single page checkout grabs the saved account so the order goes through in one tap. | None named |
| media | A news site signs a subscriber in on page load so the paywall never blocks them. | None named |
| productivity | A web email or notes app restores a signed in account after the browser restarts. | None named |
| security | A site ends auto sign in when it sees a risk signal, such as a new device, and asks for a stronger check. | None named |
| analytics | A product team measures how many returning visitors signed in automatically versus manually. | None named |
Risks
- Auto sign in on shared computers
- Stored in one browser
What the platform says
- MDN (standards docs): Credential Management API. Describes a way for sites to ask the browser to create, store and retrieve credentials such as passwords and federated logins.
Good uses and abuse
Legitimate uses
- One tap sign in
Known abuse
- Phishing on look alike sites
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 3 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
- 2016, Chrome 51: PasswordCredential and FederatedCredential ship
- 2023, Safari 17: preventSilentAccess in Safari
Sources
How well checked: Checked against real behavior.