Cookie isolation is a browser rule that stores each website's cookies in a separate container, so a cookie set on one site cannot be read on another. Instead of one shared pool for every site a user visits, the browser keeps a distinct "cookie jar" for each top-level site. The main goal is to stop advertisers and other third parties from recognising the same visitor across unrelated websites.
What a cookie jar is and why it matters
A cookie jar is the storage area a browser assigns to a given site. Without isolation, a widget or ad script embedded on many pages could set one identifier and read it everywhere it appears. With isolation, the same embedded script gets a different jar depending on which site the user is currently on.
Isolation is usually built on a few related parts:
- Top-level site: the address shown in the address bar. This is the key that decides which jar is used.
- Partition key: the label a browser attaches to a cookie, usually combining the embedded site and the top-level site.
- Storage buckets: cookies, local storage and caches that are kept apart per partition.
- Exceptions: narrow allowances for legitimate cross-site features such as some login flows.
Partitioned cookies, CHIPS and state partitioning
Isolation goes by several names, and the names are not interchangeable. Partitioned cookies are cookies that carry the Partitioned attribute, a flag that tells the browser to keep the cookie inside the top-level site where it was created. Google calls this approach CHIPS, which stands for Cookies Having Independent Partitioned State. The specification says the Partitioned attribute is only accepted on cookies sent over secure connections, so a developer must also set the Secure flag.
Total Cookie Protection is Firefox's version. Mozilla describes it as a separate cookie jar for each website, and the same mechanism also covers other storage such as local storage and caches. Firefox applies it by default. Safari and Brave also restrict third-party cookies, and the approaches differ in detail, so a test in one browser does not prove behaviour in another.
Blocking is a related but different idea. A blocked third-party cookie is not stored at all. An isolated one is stored, but only usable on its own top-level site. Isolation keeps legitimate embedded features working while cutting off the cross-site link, which is why it is often preferred over a flat ban.
How isolation works step by step
The browser applies the rule each time a request is made. The sequence below uses a simple example: a news site embeds a video player from a third-party provider.
- The user opens the news site, which becomes the top-level site.
- The video player loads inside an embedded frame and tries to set a cookie.
- The browser attaches the partition key, so the cookie is filed under the pair "news site plus video provider".
- The user opens a shopping site that also embeds the same provider. The browser now uses a different partition key.
- The provider finds no cookie in the shopping site's jar, so it cannot match the visitor to the first visit.
The same logic explains the breakage described below. If the provider needs to see a login cookie that was set under a different top-level site, the request fails.
Practical considerations and limits
Isolation reduces one tracking method, but it does not remove tracking. Browser fingerprinting, which combines device and browser traits, can still produce a recognisable pattern without any cookie. Isolation also does not clear data that a site stores on its own domain, such as after a user logs in.
Breakage is the most common complaint. Mozilla's own support page explains that sites can fail because developers often do not expect third-party storage to be divided by top-level site. Single sign-on and embedded payment widgets are the usual cases. Firefox tries to relax the rule for some sign-in services, but it can still ask the user for permission in certain cases.
Chrome's position has changed over time. Google had planned to phase out third-party cookies, then abandoned that plan, and third-party cookies remain on by default in Chrome, managed through the existing Privacy and Security settings. For a site owner, that means isolation should be treated as a browser behaviour that varies, not a guaranteed outcome for every visitor.
Isolation matters most for people who manage several accounts. Each profile in an antidetect browser normally has its own storage, so a cookie from one profile should not leak into another. Setting that up correctly is a separate task from understanding the browser rule itself, and users who need it should read our Best Free Antidetect Browser in 2026 comparison before choosing a tool. You can also check how your own browser handles cross-site storage with the checker below.
Isolation compared with third-party cookie blocking
| Aspect | Cookie isolation (partitioning) | Third-party cookie blocking |
|---|---|---|
| Where data is stored | In a jar tied to the top-level site | Not stored for cross-site use |
| Cross-site tracking | Prevented, because jars do not match | Prevented, because cookies are refused |
| Embedded features | Often keep working inside the same site | Often break, such as some sign-ins |
| Typical example | Firefox Total Cookie Protection, CHIPS | Strict tracker blocking modes |
| Main risk | Unexpected breakage in complex sites | Broader breakage for embedded content |
Managing isolated cookies in practice
If you test sites or manage accounts, start by checking which browser and settings you use, because the default differs between products. Keep a record of which cookie partitions a site needs, and do not assume a cookie set on one site will be available on another. For exporting or moving cookie data between tools, our Cookie Converter guide to Netscape and JSON formats explains the file formats involved.
Frequently Asked Questions
FAQ
What to do next
Treat cookie isolation as a browser rule to verify, not an assumption. Open the cookie settings in the browser you use, confirm whether partitioning or third-party blocking is active, and test the sites you depend on after any change. If a login or embedded widget breaks, the cause is usually the partition, and the fix is an exception or a different browser profile rather than a wider change to your privacy settings.