Skip to Content
Platform.Ontology

CHIPS partitioned cookies

Lets an embedded service keep a cookie that is private to each top-level site where it is embedded.

Works without askingTracking across apps and sitesBefore the visitWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported1142023-05-30None
EdgeSupported1142023-06-02None
FirefoxSupported1412025-07-22Verify exact milestone
SafariNot supportedNot availableNot listedBlocks third-party cookies anyway
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported1142023-05-30None
Samsung InternetSupported23.02023-10-18None

How a site asks for it

APISet-Cookie: ...; Secure; Partitioned (SameSite=None implied)
Browser compat keyshttp.headers.Set-Cookie.Partitioned
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsSame lifetime rules as normal cookies; up to 400 days in Chrome
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Cookie with Partitioned attribute
Shape: string
How often: set by response or script

FieldTypeUnitRangePrecision
size capintegerbytes0 to 10240 per partitionexact

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

TypeExampleApps
paymentsA payment widget remembers your cart on one store without knowing which other stores you visit.Stripe, PayPal
socialA chat widget on a shop keeps your chat open as you move between pages of that shop only.Intercom, Drift
mapsAn embedded map remembers your zoom and layers on a hotel site, but not across other sites.Google Maps, Mapbox
videoAn embedded video player remembers your volume and captions on a news site.YouTube, Vimeo
gamesAn embedded game on a portal saves your progress for that portal only, and does not follow you to other portals.itch.io, Poki
securityA 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

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits0Rough 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)

Sources

How well checked: Based on official documentation.

On this page