v150 · removal · privacy sandbox

RWS to CHIPS Migrator

Paste your .well-known/related-website-sets.json manifest and get the CHIPS (Partitioned) cookie configuration for every cross-site domain in your set. See the old RWS access pattern beside the new cookie header, plus a feature-detect panel and privacy comparison.

Chrome 150: Related Website Sets no longer grants cross-site cookie access. CHIPS (Partitioned attribute) is the recommended path for third-party cookies that only need per-site isolation — no manifest, no API calls required.
.well-known/related-website-sets.json — paste your manifest or load an example
Feature detect — APIs available in this browser

CHIPS requires no API — it is a cookie attribute. These are the storage access APIs that remain after RWS removal.

Privacy model comparison

Property Related Website Sets (removed) CHIPS — Partitioned
Cookie scope Unpartitioned — shared across all top-level sites in the set Partitioned — isolated per top-level site
Requires manifest Yes — .well-known/related-website-sets.json on the primary domain No — just add Partitioned to Set-Cookie
Requires API call Yes — requestStorageAccessFor() or requestStorageAccess() depending on context No — works automatically for cookies with the attribute
Cross-site state sharing Allowed within set — session on brand.example readable on shop.example Not allowed — each top-level site sees its own partition
Tracking surface Larger — shared identity across set members creates a cross-site tracking vector Minimal — partition key includes the top-level site, no cross-site linkage
Browser support Chrome only (now removed). Not in Firefox or Safari. Chrome 114+, Firefox (partial), Safari (planned). Becoming the standard.
User prompt Sometimes — requestStorageAccess() could prompt Never — no permission prompt needed
Status in Chrome 150 Removed Fully supported

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗