Learn more about third-party cookie changes and understand what actions you need to take.
Prepare for changes
Review your cookies and make a list of those cookies for which you will need to take action to ensure they keep functioning properly.
Start auditing
Set up Chrome to simulate the state when third-party cookies are blocked by user choice.
Start testing

Migrate to privacy preserving solutions

Once you have identified the cookies with issues and you understand the use cases for them, you can work through the following options to pick the necessary solution.
The new cookie attribute, Partitioned, allows developers to opt a cookie into partitioned storage, with separate cookie jars per top-level site.
Explore CHIPS
Storage Access API allows iframes to request storage access permissions when access would otherwise be denied by browser settings.
Explore Storage Access API
Related Website Sets (RWS) is a way for a company to declare relationships among sites, so that browsers allow limited third-party cookie access for specific purposes.
Explore Related Website Sets
A web API for privacy-preserving identity federation.
Explore FedCM

Guides for common workflows

Understand how to test common workflows that may rely on third-party cookies and decide on which privacy-preserving alternatives to migrate to.
Find recommended solutions for sign-in scenarios.
Learn more
Test for embed-related journeys that rely on third-party cookies, and learn how to choose between the privacy-preserving alternatives.
Learn more

Temporary exceptions

Cross-site cookies have been a critical part of the web for over a quarter of a century. This makes any change, especially a breaking change, a complex process that requires a coordinated and incremental approach. As with many previous deprecations on the web, we understand there are cases where sites need extra time to make the necessary changes and preserve critical user experiences.
Learn more
If your first-party site relies on third-party embedded services and third-party cookie deprecation has caused functionality on your website to break, you may be eligible for the first-party deprecation trial.
Learn more
If you are a third-party service provider and third-party cookie deprecation has caused your embeds and service functionalites to break, you may be eligible for the third-party deprecation trial.
Learn more
Learn more about temporary heuristics based exceptions.
Learn more
Learn more about Chrome Enterprise policies for third-party cookies.
Learn more
Features and tooling to help you transition from third-party cookies.
For sites taking part in either of the third-party cookie deprecation trials, Chrome provides a grace period to temporarily re-enable third-party cookies. During the grace period, sites can access third-party cookies in Chrome, even if they haven't yet deployed trial tokens. Chrome is now providing a mechanism to allow sites to opt out of the grace period for a percentage of users.
Chrome 126 starts origin trials for the Continuation API bundle and Storage Access API auto-grant
From July 1, 2024, sites and services that registered for one of the third-party cookie deprecation trials will receive a grace period of 60 days to deploy trial tokens, starting from the date their trial registration was approved.
We want to ensure we capture the various scenarios where sites break without third-party cookies to ensure that we have provided guidance, tooling, and functionality to allow sites to migrate away from their third-party cookie dependencies. If your site or a service you depend on is breaking with third-party cookies disabled, you can submit it to our breakage tracker.
Report an issue