Shared Storage API (retired)
Cross-site storage whose values could only be read in a locked worker. Retired Oct 2025.
In one line
Can't store cross site data for ads in Chrome anymore, since it was retired in 2025
Cross-site storage whose values could only be read in a locked worker. Retired Oct 2025.
Let scripts write cross-site values (for example a frequency count) and read them only inside a worklet that output through limited channels (selectURL, Private Aggregation). Disabled starting build 153.0.8001.0; code removal follows.
What it can and can't do
What the user does: Nothing. It used to happen in the background on pages with embedded ads
It can
- Have stored values in the browser that any site could use through a locked worker
- Have helped choose an ad or count reach without naming you
It cannot
- Run in Chrome after retirement
- Work in Edge, Firefox or Safari
- Show stored values to the page directly
- Replace cookies for all ad needs
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Removed | 153 | 2026-09-08 | Disabled in 153 |
| Edge | Not supported | Not available | Not listed | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Removed | 153 | 2026-09-08 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | window.sharedStorage.set(), worklet.run(), selectURL() |
| Permissions policy | shared-storage |
| Browser compat keys | api.WindowSharedStorage |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Entries expire after 30 days, renewable on write |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Key/value pairs readable in worklet only
Shape: object
How often: writes any time
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
entry lifetime | integer | days | up to 30 | renewed on write |
Technical limits
- Reads only inside a worklet
- selectURL leaks log2(n) bits capped at about 12 bits per 24 hours per top-level site (budget)
- No direct script access to values
- Chrome only
The story
What it is
Chrome storage that held cross site values in a locked room. Retired.
For you
You never saw it. A script could write a value, such as a count, that other sites could read only inside a locked worker. Chrome is turning it off. You will not meet it.
For makers
It was meant to help with things like frequency capping and A/B tests without tracking. Reads had to go through limited paths. With the Privacy Sandbox ad parts retired, it is going away.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | An ad network counted how many times you saw an ad across sites to avoid showing it too often. | Google Ad Manager |
| analytics | A test tool used it to keep the same A or B design across sites you visit. | None named |
| games | A game studio could cap how often it showed the same promo across sites. | None named |
| media | A publisher used it to pick which ad creative to show without a profile. | None named |
| shopping | A retailer used it to know a visitor saw a sale ad on a partner site. | None named |
| social | A social login widget could have stored a flag across sites, read only in a safe room. | None named |
Risks
- Retired in Chrome
- Never widely adopted
What the platform says
- Google Chrome: Shared Storage API. Chrome pitched it as unpartitioned storage that could be read only in a locked worklet with limited outputs.
Good uses and abuse
Legitimate uses
- Cross-site A/B tests, frequency caps (historical)
Known abuse
- Cross-site counters tied to fingerprints
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2023-09, Chrome 117: Shipped
- 2025-10, Chrome 141: Retirement announced (Private Aggregation including Shared Storage)
- 2026-01, Chrome 144: Deprecation per release notes
- 2026-09, Chrome 153: Disabled from 153.0.8001.0, code removal without staged rollout (post dated Sep 30 2026)
Related capabilities
Related
- Private Aggregation API (removed). Can't send noisy ad totals from Chrome anymore, since it was removed in August 2026
- Fenced Frames (being phased out). Can't fully show an ad in a sealed frame, as Chrome makes it a stub
Sources
- Privacy Sandbox: Update on plans (Oct 17, 2025)
- Privacy Sandbox feature status page (updated Aug 14, 2026)
- Privacy Sandbox history and removal timeline (checked Oct 2, 2026)
- Shared Storage explainer
How well checked: Checked against real behavior.