Storage Access API
Lets an embedded frame ask to use its third-party cookies; the browser may prompt or auto-allow.
In one line
Can ask to use its own cookies when embedded in another site
Lets an embedded frame ask to use its third-party cookies; the browser may prompt or auto-allow.
Used by embedded SSO, comments and video frames to regain cross-site cookies on Safari, Firefox and Chrome. Safari prompts per embed; Firefox auto-grants after 5 prior interactions and a prompt in other cases; Chrome shows a prompt.
What it can and can't do
What the user does: You click a button in an embed, such as a login or comment box, and see a prompt
It can
- Ask the browser to let an embedded frame use its own cookies
- Keep you signed in to that embedded service
- Get approved without a prompt in some cases, based on past use
It cannot
- Use the cookies without approval from the browser or you
- Reach cookies of other sites
- Work if you click Don't allow
- Persist forever, since browsers can ask again
How it differs between platforms: Safari and Firefox show a prompt or approve automatically after use. Chrome allows it with less friction.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 119 | 2023-10-31 | None |
| Edge | Supported | 85 | 2020-08-27 | None |
| Firefox | Supported | 65 | 2019-01-29 | None |
| Safari | Supported | 11.1 | 2018-04-12 | None |
| Safari on iPhone | Supported | 11.3 | 2018-03-29 | None |
| Chrome on Android | Supported | 120 | 2023-12-05 | None |
| Samsung Internet | Supported | 25.0 | 2024-04-24 | None |
How a site asks for it
| API | document.hasStorageAccess(), document.requestStorageAccess(), Permissions API storage-access |
| Permission name | storage-access |
| Permissions policy | storage-access |
| Browser compat keys | api.Document.requestStorageAccessapi.Document.hasStorageAccess |
| How access is granted | prompt |
| What the user sees | Browser prompt: allow site to use cookies and data on this site |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Chrome grant lasts 30 days for the embed; Safari 24 hours of use then reprompt (approx.); Firefox 30 days |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Granted per embedded frame; sandbox needs allow-storage-access-by-user-activation |
Data you get
What comes back: Grant state
Shape: boolean
How often: per frame
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
granted | boolean | none | true or false | exact |
Technical limits
- Needs a user gesture in the iframe
- Frame must have interacted as first party in the past (Safari, Firefox)
- Sandboxed frames need allow-storage-access-by-user-activation
The story
What it is
Lets an embedded frame ask to use its cookies from other sites, and the browser may prompt you.
For you
You see a prompt in some browsers: this site wants to use cookies on another site. If you allow it, an embedded login, comment box or video frame can recognise you. In some browsers, it grants after some use.
For makers
Single sign on, comments and paid video frames need cookies from their own domain. The API gives them a way back in after blocking. It also gives the browser a place to ask the person, as a check on trackers.
Where you see it
| Type | Example | Apps |
|---|---|---|
| social | A comment box from a social site recognises you inside a news article, and lets you post. | Disqus, Facebook |
| video | A paid video embed checks your subscription cookie from its own domain, so it can play for you. | Vimeo, YouTube |
| games | A game inside a portal frame uses its cookie to remember your login and progress. | itch.io, Poki |
| enterprise | A work tool embedded in another app uses its login cookie in the frame. | Salesforce, Atlassian |
| payments | A payment frame recognises your saved card details, from its own domain. | Stripe, PayPal |
| security | Browsers use the prompt to stop trackers hidden in embeds from asking for cookies for free. | Safari, Firefox |
Risks
- Prompt can be clicked without thinking
- Rules differ across browsers
What the platform says
- Apple: Storage Access API. WebKit introduced it as a way for embedded content to ask for cookie access with the person's consent.
Good uses and abuse
Legitimate uses
- Embedded login and comment widgets
Known abuse
- Embedded tracker regaining cookies after prompt fatigue
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 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
- 2018-03, Safari 11.1: First browser to ship
- 2019-01, Firefox 65: Shipped
- 2023-10, Chrome 119: On by default
Related capabilities
Related
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
- Related Website Sets (retired). Can't let a group of related sites share cookies in Chrome anymore
Sources
How well checked: Checked against real behavior.