the Chromium logo

The Chromium Projects

Cookies Having Independent Partitioned State (CHIPS)


From the CHIPS explainer:

In order to increase privacy on the web, browser vendors are either planning or already shipping restrictions on cross-site tracking. This includes phasing out support for third-party cookies, cookies sent in requests to sites other than the top-level document's site, since such cookies enable servers to track users' behavior across different top-level sites.

Although third-party cookies can enable third-party sites to track user behavior across different top-level sites, there are some cookie use cases on the web today where cross-domain subresources require some notion of session or persistent state that is scoped to a user's activity on a single top-level site.

The Partitioned Attribute

Partitioned cookies are cross-site cookies which are only available on the top-level site they were created.

Third parties which want to opt into receiving partitioned cookies should include the Partitioned attribute in their Set-Cookie header:

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

Partitioned cookies must include the attributes required for the __Host- prefix (Secure, Path=/, and no Domain) and cannot have the SameParty attribute. Partitioned cookies may include the __Host- prefix in their name, but it is not necessary as long as they satisfy the other requirements.

Chrome will enforce these rules for cookies set with the Partitioned attribute even when cookie partitioning is disabled, but if the feature is disabled the resulting cookie will still be sent to requests to its host on different top-level sites than where it was set.

Origin Trial

The following only applies to Chrome version 103 or later.

If you are interested in participating in the CHIPS origin trial, then you need to include the Origin-Trial header with a valid token in any HTTP response that also includes a Set-Cookie header with the Partitioned attribute.

The Set-Cookie header does NOT have to result in a valid cookie.

If you have successfully opted into the origin trial AND have set a partitioned cookie, then subsequent requests from the Chrome client will include the Sec-CH-Partitioned-Cookies: ?0 whenever the partitioned cookie is included in the Cookie header.

Responses which do not include a Set-Cookie header with Partitioned will not impact a site's origin trial participation status.

Not all Chrome clients will be in the trial. If the client does not send the Sec-CH-Partitioned-Cookies header, then partitioned cookies are not enabled.

You can register your site for the origin trial here.

The origin trial is only available in Chrome versions 103-105.

Example usage

When a site wishes to participate in the origin trial, they should include the following headers in their response:

Origin-Trial: *valid Origin Trial token*
Set-Cookie: __Host-name=value; Secure; Path=/; SameSite=None; Partitioned;

Remember, in order to keep participating in the trial, you must include these headers in each HTTP response.

If the opt in is successful, Chrome will include the following headers in future requests:

Sec-CH-Partitioned-Cookies: ?0
Cookie: __Host-name=value


Frames that opt into the Origin Trial will have access to reading and writing partitioned cookies via JavaScript APIs such as document.cookie and the CookieStore API. Frames that are not in the trial's scripts will neither be able to read nor write partitioned cookies.

The CHIPS Origin Trial will not be supported in service workers.

Design doc

You can view the more detailed design document of the CHIPS Origin Trial here.

Local testing

If you want to test your changes locally on your machine, you can enable the CHIPS origin trial bypass feature (chrome://flags/#partitioned-cookies-bypass-origin-trial) on your local device to use partitioned cookies on any site without them needing to opt into the trial.

A/B testing

Sites can use the origin trial for A/B testing by sending the Origin-Trial and Accept-CH: Sec-CH-Partitioned-Cookies headers to users in the experiment group and not send those headers to users in the control group. However, determining which users should belong to which group is the responsibility of the origin trial participant's servers.

End-to-End Testing

These instructions describe how a web developer can perform end-to-end testing of Partitioned cookies in Chromium.

Note: these instructions will only work with a Chromium instance M100 or above.

  1. Go to chrome://flags/#partitioned-cookies and change the setting to "Enabled".

  2. Restart Chromium by clicking the "Relaunch" button in the bottom-right corner, or by navigating to chrome://restart.

Example Usage

Embeds which want to opt into using partitioned cookies should include the Partitioned attribute in their Set-Cookie header:

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

Note that the cookie has the __Host- prefix and does not include the SameParty attribute.

You can also set a partitioned cookie in JavaScript:

  name: '__Host-name',
  value: 'value',
  secure: true,
  path: '/',
  sameSite: 'none',
  // Set a partitioned cookie using the attribute below.
  partitioned: true,

Demo (Chrome 103 or later)

One you have followed the instructions in the End-to-End Testing section, you can use the following instructions to see a demonstration of the Partitioned attribute.

  1. Go to chrome://settings/cookies and make sure that the radio button is set to "Allow all cookies" or "Block third-party cookies in Incognito".

  2. Open a new tab and navigate to

  3. Click "Set cookie (SameSite=None)" to set an unpartitioned SameSite=None cookie named "unpartitioned".

  4. Click "Set partitioned cookie (SameSite=None; Partitioned)" to set a partitioned cookie, "__Host-1P_partitioned".

  5. Open DevTools to Application > Cookies > and you should see both the UI display both cookies. Note that the partitioned cookie has a "Partition Key",, whereas the unpartitioned cookie does not.

  6. Navigate to to see a site which embeds a cross-site iframe whose origin is As you can see, the unpartitioned SameSite=None cookie is available, but the partitioned cookie is not since we are now on a different top-level site.

  7. Click "Set partitioned cookie (SameSite=None; Partitioned)" to set a partitioned cookie, "__Host-3P_partitioned", in a third-party context.

  8. Open Application > Cookies > and you should see both cookies. Note that the new partitioned cookie's "Partition Key" is, the top level site ( is on the Public Suffix List).

  9. Go back to the first tab which has the chrome://settings/cookies page open. Change the setting to "Block Third-Party Cookies".

  10. Navigate back to the tab navigated to and refresh the page. You should see that only the partitioned cookie, "__Host-3P_partitioned", is available.

  11. Open DevTools to the Network > Cookies tab and refresh the page. Click on the request to "thirdparty.html". You should see that the unpartitioned cookie was blocked in a third-party context, but the partitioned cookie was allowed.

  12. Go back to the tab which has chrome://settings/cookies open. Change the setting back to "Allow all cookies" or "Block third-party cookies in Incognito".

  13. Open the tab which has open. You should see that both the "unpartitioned" and "__Host-3P_partitioned" cookies are available again.

  14. Click the "Clear cookies" button. This will cause to send the Clear-Site-Data: "cookies" header. You should see that both the "unpartitioned" and "__Host-3P_partitioned" cookies were removed.

  15. Navigate the tab back to You should see that the "__Host-1P_partitioned" cookie was not removed after sent the Clear-Site-Data header on a different top-level site.

  16. For Chrome versions 103 and 104, you can also click the "Opt-out of partitioned cookies" button to revert the partitioned cookie back to unpartitoned behavior. This option is only available to HTTP cookies during the CHIPS origin trial, which ends in 105, and is meant to demonstrate Chrome's behavior when a site opts out of the OT. If you navigate back to after clicking this button, the "__Host-1P_partitioned" cookie should still be available. Note that if you change the setting on chrome://settings/cookies to "Block Third-Party Cookies" then the "__Host-1P_partitioned" cookie is not available in a cross-site context.