Third-party cookies by browser (Nov 2026)
Whether an embedded site can set and read its own cookies on other sites, which varies by browser.
In one line
Can recognise you across sites with embedded cookies, unless your browser blocks them
Whether an embedded site can set and read its own cookies on other sites, which varies by browser.
Third-party cookies are how ad networks recognise the same person across sites. Safari blocks them, Firefox partitions them, Brave blocks them, Chrome leaves them on by default (user choice) and blocks them in Incognito.
What it can and can't do
What the user does: Nothing. It happens when a page with ads or embeds loads
It can
- Set and later see its own cookie from inside a page on another site
- Link your visits across the sites that embed it
- Keep working in Chrome, where these cookies stay on by default
- Ask the browser for access if it was blocked (Storage Access prompt)
It cannot
- Set these cookies in Safari, which blocks them
- Share one cookie across sites in Firefox, which keeps a separate jar per site
- Use them in Incognito windows in Chrome
- Get through in Brave, which blocks them
How it differs between platforms: Safari and Brave block them, Firefox splits them per site, and Chrome allows them by default but blocks them in Incognito.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 51 | 2016-05-25 | 3PC allowed by default; blocked in Incognito |
| Edge | Supported | 16 | 2017-10-17 | Blocks classified trackers only |
| Firefox | Removed | 103 | 2022-07-26 | Partitioned by default |
| Safari | Removed | 13.1 | 2020-03-24 | Blocked entirely |
| Safari on iPhone | Removed | 13.1 | 2019-09-19 | None |
| Chrome on Android | Supported | 51 | 2016-06-08 | Allowed by default |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | Allowed by default, Smart Anti-Tracking blocks some |
How a site asks for it
| API | document.cookie in iframes; Set-Cookie with SameSite=None; Secure; Storage Access API |
| Browser compat keys | http.headers.Set-Cookie.SameSite |
| How access is granted | settings |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Cookie lifetime per cookie; Chrome caps at 400 days |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Cookie jar per top-level site (partitioned) or global
Shape: object
How often: continuous
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
cookie | string | bytes | up to 4096 per cookie | n/a |
Technical limits
- Safari: blocked for all, no exceptions except Storage Access API
- Firefox: Total Cookie Protection partitions per top-level site by default (June 2022, Firefox 103)
- Chrome: kept on by default; no deprecation prompt after the April 2025 decision; Incognito blocks by default
- Edge: Tracking Prevention blocks classified trackers, not all
The story
What it is
Whether an embedded site can store cookies on other sites, which depends on which browser you use.
For you
You never see these cookies, but they decide whether an ad for boots follows you from a shoe shop to a news site. In Safari and Firefox it mostly cannot. In Chrome it still can, unless you turn it off in settings.
For makers
Ad networks use these cookies to recognise the same person across sites for targeting, frequency caps and conversion counting. Sites also use them for legitimate embeds like logins and payments. When a browser blocks them, makers must switch to first-party data or new APIs.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A retailer's ad network sets a cookie when you view boots, then recognises you on a recipe blog and shows the same boots. | Google Display Network, Criteo |
| social | A Like or Share button embedded on a news article recognises your logged-in account and counts the visit. | Facebook, X |
| video | An embedded video on a blog remembers your player settings and view history through the video host's own cookie. | YouTube |
| games | A browser game embedded in a portal page saves your progress under the game host's cookie, which breaks when the browser blocks it. | itch.io |
| payments | A card check inside a frame on a shop page relies on the bank's cookie to recognise a trusted device. | Stripe |
| security | A bot defence service sets one cookie across many customer sites to spot a scraper hopping between them. | Cloudflare |
| analytics | A marketing platform ties an ad click on one site to a purchase on another to report which campaign worked. | Google Ads |
Risks
- Cross-site profiles of your habits
- Settings differ by browser, so protection is uneven
What the platform says
- Apple: Intelligent Tracking Prevention. Safari blocks cross-site tracking by default so websites cannot follow you from site to site.
- Mozilla: Enhanced Tracking Protection. Firefox keeps each site's cookies in a separate jar so trackers cannot connect your visits.
- Google: Privacy Sandbox. Chrome kept third-party cookies and gives people a choice, while offering newer ad tools as alternatives.
Good uses and abuse
Legitimate uses
- Embedded video, chat, SSO, payment frames
- Ad measurement
Known abuse
- Cross-site profile building by ad networks
- Silent identifiers synced across domains
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2020-03, Safari 13.1: Full third-party cookie blocking
- 2022-06, Firefox 103: Total Cookie Protection default for all users
- 2024-01, Chrome 120: 1% of Chrome users had third-party cookies restricted (testing)
- 2024-07, Chrome 127: Google proposed user choice instead of deprecation
- 2025-04, Chrome 135: Google confirmed no standalone prompt; users keep the Settings choice
- 2025-10, Chrome 141: Oct 17: Google retired most remaining Privacy Sandbox APIs; third-party cookies stay
Related capabilities
Related
- CHIPS partitioned cookies. Can keep a cookie for an embedded service, separate for each site it appears on
- Storage Access API. Can ask to use its own cookies when embedded in another site
- Cookie syncing. Can let ad companies swap IDs so each recognizes you across sites
Sources
- Privacy Sandbox status (updated Aug 14, 2026)
- WebKit Full Third-Party Cookie Blocking
- Mozilla Total Cookie Protection
How well checked: Checked against real behavior.