The Privacy Sandbox timeline

The Privacy Sandbox proposals are in various stages of development. This timeline reflects when we expect new privacy-preserving APIs and other technologies to be ready in support of key use cases, so that Chrome can responsibly phase out third-party cookies. Information may change and will be updated monthly. Last update: December 2021.
DiscussionThe technologies and their prototypes are discussed in forums such as GitHub or W3C groups. Some limited testing of solutions might happen at this stage to facilitate discussions.
TestingAll technologies for the use case are available for developers to test and may be refined based on results. This may happen at any point during the quarter.
Ready for adoptionOnce the development process is complete, the successful technologies are ready to be used at scale. They will be launched in Chrome and ready for scaled use across the web.
Transition period: Stage 1APIs for each use case are available for adoption.
Chrome will monitor adoption and feedback carefully before moving to next stage.
Transition period: Stage 2Chrome will phase out support for third-party cookies over a three-month period finishing in late 2023.
Fight spam and fraud on the web
Show relevant content and ads
Measure digital ads
Strengthen Cross-site Privacy Boundaries
The Privacy Sandbox initiative also includes several proposals addressing covert tracking techniques, such as fingerprinting and network-level tracking.

Frequently Asked Questions

How often will the timeline be updated?

The timeline will be updated monthly.

Is this the definitive list of technologies Chrome will be supporting?

Not necessarily. Chrome is focused on developing proposals that support key use cases. The set of proposals solving for a particular use case (for example, showing relevant content and ads) may change and evolve over time, with web community feedback and testing. The APIs shown on the timeline are based on current expectations and might change.

How firm are the dates on the timeline?

It’s difficult to forecast how long the open, public process for developing a new web technology might take, as the new APIs may receive a lot of feedback or require multiple testing cycles. These extended discussions and testing stages often produce better, more complete solutions, and the timeline for testing and ready for adoption of use cases might change accordingly.

Where can I learn more about the timeline to phase out third-party cookies support in Chrome?

You can read an announcement of this change on the Keyword blog.

Why doesn’t the timeline show all the Privacy Sandbox proposals?

The timeline is specific to key use cases related to Chrome’s plan to phase out third-party cookies. The technologies solving for the second goal of the Privacy Sandbox initiative -- prevent covert tracking -- will follow separate timelines, as noted above.

What does origin trial (“OT”) mean in the timeline?

Origin trials are one method of testing new web technologies in Chrome. “OT” labels are shown when a Chrome origin trial has been publicly announced, is in progress or has concluded. We will add new origin trials, and other forms of available testing, on the timeline as part of the monthly updates.

How can I find out exactly when an origin trial (“OT”) is starting or ending?

Chrome’s origin trial registration page provides information for origin trials that are live or starting soon. Click the “Register” button for an active origin trial to see planned start and end dates. Note, it’s common to extend origin trials when further testing is needed. It is also common for technologies to go through multiple origin trials as they are refined.

Does this timeline reflect when the APIs will be available globally?

The “ready for adoption” milestone reflects when Chrome expects each use case to be supported globally. It is common for testing to begin with a limited population and gradually expand. We are committed to making all of the Privacy Sandbox technologies available for testing worldwide before they launch. For the “testing” stage, certain APIs may be available in limited ways, for example in selected countries.

Is Chrome considering proposals from other members of the web community?

This timeline reflects the use cases Chrome expects to support before phasing out third-party cookies. Many of the proposed technologies shown on the timeline incorporate concepts and feedback from industry and ecosystem stakeholders. We'll continue to engage publicly and review other proposals as we consider the best way to address critical use cases that support the open web ecosystem.

What does "Feature Flag" mean on the timeline?

While features are in development they are often made available behind one or more temporary flags (off by default) that can be used to enable and configure their behavior for local developer testing purposes. This may be as command line flags that need to be passed in when launching Chrome or as options in the chrome://flags browser interface.