Cookie Status compares the tracking protections that the major browsers apply by default. It covers standard browsing only, not private or incognito modes or settings the user has to change.

tracker.example, embedded on news.example

HTTP/2 200 set-cookie: uid=8f3a; Max-Age=31536000; SameSite=None; Secure

what each browser does with it

brave partitioned chrome no restrictions edge limited firefox partitioned safari blocked

$ curl -sI https://www.cookiestatus.com
| grep -i set-cookie

no output: this site sets no cookies

Comparison

last_updated: 2026-10-31 · Added tracker blocking and fingerprinting rows, Safari 27 identity resolution blocking, and corrections for Brave, Edge and Safari from new tests.

Claims marked New changed in the latest update. Follow Details → in any cell for the full explanation on that browser's page.

Cookies set by the response to a top-level navigation are no longer capped at 7 days when the site’s own hostname is a CNAME to another domain, such as a hosting provider.

affects: cname cloaking · source: WebKit Features for Safari 27.2

Cross-site requests to “ID graph” services, which link the same person across sites and devices, are blocked whenever “Prevent cross-site tracking” is on. Apple maintains the list of domains.

affects: tracker blocking · source: Blocking identity resolution infrastructure (WebKit blog)

Firefox limits how much information about the device and browser is revealed to sites in its default mode, not only in Strict mode.

affects: fingerprinting · source: Firefox 151 release notes

Partitioned cookies with the Partitioned attribute are supported again, after being removed in Safari 18.5 for further work.

affects: 3rd-party cookies · source: WebKit Features in Safari 26.2

Topics, Protected Audience, Attribution Reporting, Related Website Sets and others are being phased out. CHIPS and FedCM stay.

affects: 3rd-party cookies · source: Update on plans for Privacy Sandbox technologies

Web browsers are going through fairly momentous shifts in order to better respond to the increasing number of data breaches and cases of data misuse by third parties.

Unfortunately, each browser (and the underlying browser engine) seems to have their own interpretation of how to best tackle the problem, which leads to a diverse set of features across the browser landscape.

What’s worse, the information about how these tracking protection mechanisms are deployed is all over the place: in release notes, in developer documentation, in Twitter threads, in working groups, in feature drafts, in bug patches, etc.

The purpose of the Cookie Status resource is to (attempt to) collect this information in one place for easy access and perusal.

There is no commercial agenda behind this project. In fact, there is no agenda other than knowledge transfer.

Just to kick things off. Hopefully the open-source nature of this project will invite others to contribute details about browsers that are doing significant work with regard to user privacy.

Cookie Status doesn’t use browser cookies, localStorage, or IndexedDB.

It doesn’t use sessionStorage either, and it doesn’t load anything from third-party servers. The search index is served from this site.

If you see anything contrary to the above, please raise an issue about this.