Skip to Content
Platform.Ontology

Shared Storage API (retired)

Cross-site storage whose values could only be read in a locked worker. Retired Oct 2025.

Used to track youTracking across apps and sitesPrivacy SandboxWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeRemoved1532026-09-08Disabled in 153
EdgeNot supportedNot availableNot listedNone
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidRemoved1532026-09-08None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIwindow.sharedStorage.set(), worklet.run(), selectURL()
Permissions policyshared-storage
Browser compat keysapi.WindowSharedStorage
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsEntries expire after 30 days, renewable on write
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Key/value pairs readable in worklet only
Shape: object
How often: writes any time

FieldTypeUnitRangePrecision
entry lifetimeintegerdaysup to 30renewed 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

TypeExampleApps
adsAn ad network counted how many times you saw an ad across sites to avoid showing it too often.Google Ad Manager
analyticsA test tool used it to keep the same A or B design across sites you visit.None named
gamesA game studio could cap how often it showed the same promo across sites.None named
mediaA publisher used it to pick which ad creative to show without a profile.None named
shoppingA retailer used it to know a visitor saw a sale ad on a partner site.None named
socialA 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

Good uses and abuse

Legitimate uses

  • Cross-site A/B tests, frequency caps (historical)

Known abuse

  • Cross-site counters tied to fingerprints

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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)

Sources

How well checked: Checked against real behavior.

On this page