demo · v150
Deprecation Timeline
Related Website Sets shipped in Chrome 113 as the first cross-site bridge in the Privacy Sandbox. By Chrome 150 the entire stack is being wound down. This timeline traces the full arc — from the original third-party cookie deprecation plan through the Privacy Sandbox pivot — and shows exactly what is still working in Chrome 150 vs what is gone.
RWS and Privacy Sandbox timeline
Click any milestone to toggle its detailed view. Filter the timeline by status:
2019–2021
Privacy Sandbox announced
Google announces intent to deprecate third-party cookies by 2022. First Parties Sets (now RWS) proposed as a bridge for same-org cross-site cookie sharing.
historical
Chrome 113 — May 2023
Related Website Sets ships
RWS + Storage Access API integration ships to stable. Sites can declare a
.well-known/related-website-set.json to enable limited cross-site cookie access via requestStorageAccess() without a user gesture for set members.shipped Chrome 113
Chrome 119 — Nov 2023
requestStorageAccessFor ships
document.requestStorageAccessFor(origin) ships — the top-level site can request storage access on behalf of embedded origins that are RWS members, without requiring a gesture inside the iframe.shipped Chrome 119
April 2024
Google reverses 3PC deprecation
Google announces it will no longer deprecate third-party cookies by default, following UK CMA concerns. With 3PC staying, the core premise of RWS — acting as a substitute for 3PC — is invalidated. Chrome begins planning the wind-down.
pivot announced
Chrome 149 — Q2 2026
Deprecation announced for RWS and requestStorageAccessFor
Chrome announces both RWS and
requestStorageAccessFor will be removed. Console deprecation warnings begin appearing. requestStorageAccess() inside iframes continues to work as the long-term standard replacement.deprecated Chrome 149
Chrome 150 — NOW
requestStorageAccessFor removed; RWS wind-down
document.requestStorageAccessFor() is undefined in Chrome 150. RWS membership grants no special Storage Access API privileges. The .well-known/related-website-set.json file is no longer parsed for cross-site cookie benefits.removed Chrome 150
Chrome 151+ — future
Full RWS infrastructure removal
Remaining RWS list fetching and set-membership checks are removed. Sites should have migrated to
requestStorageAccess() from inside embedded iframes, or to CHIPS (Partitioned attribute) for embedded storage that doesn't need to be shared.planned
What still works in Chrome 150?
| Feature | Chrome 149 | Chrome 150 | Replacement |
|---|---|---|---|
document.requestStorageAccessFor() |
deprecated (warns) | REMOVED | requestStorageAccess() in iframe |
RWS gesture-bypass for requestStorageAccess() |
deprecated | NO — user gesture required | Require user gesture in iframe |
document.requestStorageAccess() |
works | works | Already the standard API |
document.hasStorageAccess() |
works | works | Already the standard API |
CHIPS (Partitioned cookie attribute) |
works | works | Use for partitioned cross-site embed storage |
| Third-party cookies (SameSite=None) | works | works | 3PC not deprecated — still works |
see also
- RWS Detection Probe — check what's present in your browser
- Storage Access Migration — requestStorageAccess() replacement
- CHIPS Explainer — partitioned cookies as the long-term alternative
- ChromeStatus: Deprecate RWS
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗