Cookies Having Independent Partitioned State (CHIPS)

Allow developers to opt-in a cookie to "partitioned" storage, with a separate cookie jar per top-level site.


  • June 2022: Based on feedback, setting cookies with the Partitioned attribute no longer requires omitting the Domain attribute. This allows subdomains of a third-party site to access cookies within a partition.

Implementation status

What is CHIPS

Cookies Having Independent Partitioned State (CHIPS) allows developers to opt a cookie into partitioned storage, with separate cookie jars per top-level site, improving user privacy and security.

Browsers are well under way in phasing out unpartitioned third-party cookies, so CHIPS and Related Website Sets (formerly called First-Party Sets) will be the only way to read and write cookies from cross-site contexts, such as iframes, when third-party cookies are blocked.

Without partitioning, third-party cookies can enable services to track users and join their information from across many unrelated top-level sites. This is known as cross-site tracking.

Without cookie partitioning, a third-party service can set a cookie when embedded in one top-level site and access that same cookie when the service is embedded in other top-level sites.

CHIPS introduces a new cookie attribute, Partitioned, to support cross-site cookies that are partitioned by top-level context.

Set-Cookie header:

Set-Cookie: __Host-name=value; Secure; Path=/; SameSite=None; Partitioned;


Document.cookie="__Host-name=value; Secure; Path=/; SameSite=None; Partitioned;"

A partitioned third-party cookie is tied to the top-level site where it's initially set and cannot be accessed from elsewhere. This way cookies set by a third-party service can only be read within the same embedded context of the top-level site where they were initially set.

With cookie partitioning, a third-party service that sets a cookie when embedded in one top-level site cannot access that same cookie when the service is embedded in other top-level sites.

With partitioned cookies, when a user visits site A and embedded content from site C sets a cookie with the Partitioned attribute, the cookie is saved in a partitioned jar designated only for cookies that the site C sets when it's embedded on site A. The browser will only send that cookie when the top-level site is A.

When the user visits a new site, for example site B, an embedded C frame will not receive the cookie that was set when C was embedded in site A.

If a user visits site C as a top level website, the partitioned cookie that C set when it was embedded in A will not be sent in that request either.

With cookie partitioning, a third-party service that sets a cookie when embedded in a site cannot access that same cookie even when the users visits the service as top-level site.

Use cases

For example, the site retail.example may want to work with a third-party service to embed a support chat box on its site. Many embeddable chat services today rely on cookies to save interaction history.

Top-level site retail.example embedding a third-party service

Without the ability to set a cross-site cookie, could instead rely on retail.example passing along their first-party session identifier (or some derived value of it). In that case, every website that is embedded on would require additional setup to pass along the state.

Alternatively, may request retail.example to embed JavaScript that's hosted on on retail.example pages. This introduces security risks, because it allows the script to have elevated privileges on retail.example, such as the ability to access authentication cookies.

Example use cases for CHIPS include any scenarios where cross-site subresources require some notion of session or persistent state that is scoped to a user's activity on a single top-level site, such as:

  • Third-party chat embeds
  • Third-party map embeds
  • Third-party payment embeds
  • Subresource CDN load balancing
  • Headless CMS providers
  • Sandbox domains for serving untrusted user content (such as and
  • Third-party CDNs that use cookies to serve content that's access-controlled by the authentication status on the first-party site (for example, profile pictures on social media sites hosted on third-party CDNs)
  • Front-end frameworks that rely on remote APIs using cookies on their requests
  • Embedded ads that need state scoped per publisher (for example, capturing users' ads preferences for that website)

As browsers are phasing out unpartitioned third-party cookies, a couple of other approaches to partitioning have been attempted.

Firefox announced that they are partitioning all third-party cookies by default in their ETP Strict mode and private browsing mode, so all cross-site cookies are partitioned by the top-level site. However, partitioning cookies without a third-party opt-in can lead to unexpected bugs, since some third-party services have built servers which expect an unpartitioned third-party cookie.

Safari previously tried partitioning cookies based on heuristics, but eventually chose to block them altogether, citing developer confusion as one of the reasons. Recently, Safari expressed interest in an opt-in based model.

What sets CHIPS apart from existing implementations of partitioned cookies is the third-party opt-in. Cookies must be set with a new attribute in order to be sent on cross-party requests once (unpartitioned) third-party cookies are obsoleted.

While third-party cookies still exist, the Partitioned attribute provides an opt-in to a more restrictive, more secure type of cookie behavior. CHIPS is an important step to help services make a smooth transition to a future without third-party cookies.

CHIPS design details

Partitioning model

Today, cookies are keyed on the hostname or domain of the site that set them, that is, their host key.

For example, for cookies from, the host key is ("").

Under CHIPS, cookies that opt into partitioning will be double-keyed on their host key and partition key.

A cookie's partition key is the site (scheme and registrable domain) of the top-level URL the browser was visiting at the start of the request to the endpoint that set the cookie.

In the example above where is embedded on https://retail.example, the top-level URL is https://retail.example.

The partition key in that case is ("https", "retail.example").

Likewise, a request's partition key is the site of the top-level URL the browser is visiting at the start of a request. Browsers must only send a cookie with the Partitioned attribute in requests with the same partition key as that cookie.

Here's what the cookie key in the example above looks like before and after CHIPS.

Site A and the embedded site C share a partitioned cookie. When not embedded, site C cannot access the partitioned cookie.

Before CHIPS



key={("https", "retail.example"),

Related Website Sets (RWS) is a web platform mechanism for developers to declare relationships among sites, so that browsers can use this information to enable limited cross-site cookie access for specific, user-facing purposes. Chrome will use these declared relationships to decide when to allow or deny a site access to their cookies when in a third-party context.

The current Related Website Sets design relies on Storage Access API and does not integrate with CHIPS partitioning.

Consider Related Website Sets in situations where you need the same cookie to be available to a service that's embedded in multiple related sites.

CHIPS provides the functionality for a service to act as an isolated component across multiple sites. If the service that's a member of a Related Website Set sets a partitioned cookie, its partition key will be the top-level site and that cookie will not be available to other set members.

If you have a use case that relies on a shared cookie partition across sites within a FPS you can provide examples and feedback on the GitHub issue.

Security design

To encourage good security practices, with CHIPS, cookies are only set by and sent over secure protocols.

Partitioned cookies must be set with Secure.

It is recommended to use the __Host prefix when setting partitioned cookies to make them bound to the hostname (and not the registrable domain).


Set-Cookie: __Host-example=34d8g; SameSite=None; Secure; Path=/; Partitioned;


This demo will walk you through how partitioned cookies work and how you can inspect them in DevTools.

Site A embeds an iframe from Site B which uses JavaScript to set two cookies: a partitioned and unpartitioned cookie. Site B displays all cookies accessible from that location using document.cookie.

When third-party cookies are blocked, site B will only be able to set and access the cookie with the Partitioned attribute in cross-site context.

When third-party cookies are allowed, site B is able to also set and access the unpartitioned cookie.

Site A and site B
Left: Third-party cookies are blocked. Right: Third-party cookies are allowed.


  1. Chrome 114 or higher.
  2. Ensure third-party cookies are blocked:
    • Open Settings > Privacy and security.
    • Click Third party cookies.
    • Select Block third party cookies.
Chrome cookie settings.
Chrome cookie settings.

Use DevTools to inspect partitioned cookies

  1. Visit
  2. Press Control+Shift+J (or Command+Option+J on Mac) to open DevTools.
  3. Click the Application tab.
  4. Navigate to Application > Storage > Cookies.
  5. Click on

DevTools will display all the cookies from the selected origin.

Cookies from site B in the DevTools Application tab.

Site B can only set the partitioned cookie in cross-site context, the unpartitioned cookie will be blocked:

  • You should see __Host-partitioned-cookie with the partition key of the top level site
Partition key for __Host-partitioned-cookie.
  1. Click Go to Site B.
  2. In DevTools, navigate to Application > Storage > Cookies.
  3. Click on
Site B

In this scenario, because you are on site B in top-level context, it can set and access both cookies:

  • unpartitioned-cookie has an empty partition key.
  • __Host-partitioned-cookie cookie has the partition key
Cookies from site B in the DevTools Application tab when visiting B as a top-level site. __Host-partitioned-cookie has the partition key

If you navigate back to site A, unpartitioned-cookie is now stored in the browser, but it will not be accessible from site A.

  1. Click Go to Site A.
  2. Click the Network tab.
  3. Click on
  4. Click on the Cookies tab.

While on site A, you should see the __Host-partitioned-cookie with the partition key of the top level site

Network tab showing cookies from site B iframe that are accessible when it's embedded on site A.

If you check show filtered out cookies requests DevTools will show that the unpartitioned cookie is blocked, highlighted in yellow with a tooltip: "This cookie was blocked due to user preferences".

Network tab showing blocked cookies from site B iframe.

In Application > Storage > Cookies clicking on will show:

  • unpartitioned-cookie with the empty partition key.
  • __Host-partitioned-cookie cookie with the partition key
Cookies from site B in the DevTools Application tab. __Host-partitioned-cookie cookie has the partition key unpartitioned-cookie is shown, but it's not accessible to site B iframe when it's ebmedded on site A.

Clear cookies

To reset the demo, clear all cookies for the site:

  • Press Control+Shift+J (or Command+Option+J on Mac) to open DevTools.
  • Click the Application tab.
  • Navigate to Application > Storage > Cookies.
  • Right click on
  • Click Clear.