CHIPS partitioned cookies
Lets an embedded service keep a cookie that is private to each top-level site where it is embedded.
In one line
Can keep a cookie for an embedded service, separate for each site it appears on
Lets an embedded service keep a cookie that is private to each top-level site where it is embedded.
A widget (chat, maps, payments) can remember state per embedding site without a cross-site ID. Capped at 10 KiB per partition, so it cannot build a cross-site profile. Supported on Chrome 114 and later; Firefox also ships it.
What it can and can't do
What the user does: Nothing. It happens when a page includes an embedded chat, map or video
It can
- Save a cookie inside an embedded service on a page
- Keep that cookie separate for each top level site
- Remember a chat or login state on that one site
It cannot
- Share the cookie with the same service on other sites
- Be used to follow you across sites
- Work in Safari and iPhone browsers, which have no CHIPS
- Survive if you clear cookies
How it differs between platforms: Chrome, Edge, Firefox and Samsung Internet support it. Safari and iPhone browsers do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 114 | 2023-05-30 | None |
| Edge | Supported | 114 | 2023-06-02 | None |
| Firefox | Supported | 141 | 2025-07-22 | Verify exact milestone |
| Safari | Not supported | Not available | Not listed | Blocks third-party cookies anyway |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 114 | 2023-05-30 | None |
| Samsung Internet | Supported | 23.0 | 2023-10-18 | None |
How a site asks for it
| API | Set-Cookie: ...; Secure; Partitioned (SameSite=None implied) |
| Browser compat keys | http.headers.Set-Cookie.Partitioned |
| 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 | Same lifetime rules as normal cookies; up to 400 days in Chrome |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Cookie with Partitioned attribute
Shape: string
How often: set by response or script
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
size cap | integer | bytes | 0 to 10240 per partition | exact |
Technical limits
- Key is the top-level site, so the same iframe on another site sees a different jar
- 10240 bytes max per partition for all CHIPS cookies of that embedded origin
- Must be Secure
- Safari blocks all third-party cookies so the attribute is moot there
The story
What it is
A cookie for an embedded widget that is kept apart for each site it appears on.
For you
You do not see it. A chat box, map or payment widget on a site can remember you on that site only. It cannot use the same cookie to know you on another site.
For makers
Widgets still need to remember state, like a chat session or a login, after third party cookies went away. Splitting the cookie per site gives them that without a cross site profile. The 10 KiB cap makes it hard to store much.
Where you see it
| Type | Example | Apps |
|---|---|---|
| payments | A payment widget remembers your cart on one store without knowing which other stores you visit. | Stripe, PayPal |
| social | A chat widget on a shop keeps your chat open as you move between pages of that shop only. | Intercom, Drift |
| maps | An embedded map remembers your zoom and layers on a hotel site, but not across other sites. | Google Maps, Mapbox |
| video | An embedded video player remembers your volume and captions on a news site. | YouTube, Vimeo |
| games | An embedded game on a portal saves your progress for that portal only, and does not follow you to other portals. | itch.io, Poki |
| security | A bot checking widget keeps a short session on each site separately, which stops it from building a cross site list of visitors. | Cloudflare Turnstile |
Risks
- Still allows tracking within one site
- Only for embedded content
What the platform says
- Google Chrome: CHIPS. Chrome describes it as a way for embedded services to keep cookies that are split per top level site.
Good uses and abuse
Legitimate uses
- Embedded chat widgets
- Per-site payment iframes
- CDN session affinity
Known abuse
- Not for cross-site tracking by design
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 0 | Rough identifying entropy, when known |
History
- 2023-07, Chrome 114: CHIPS on by default (origin trial ran Chrome 100 to 116)
- 2025-07, Firefox 141: Firefox ships partitioned cookie attribute (verify exact milestone)
Related capabilities
Related
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
- Storage partitioning. Can't use the same embedded storage to recognize you across different sites
Sources
How well checked: Based on official documentation.