Third-Party Cookies in 2026: What Actually Happened After Years of Delays

Third-party cookies were supposed to be gone from Chrome years ago. Google first announced the plan in January 2020, aiming to complete the phase-out by 2022. That date came and went, replaced by a new date, which also came and went. By 2026, the honest status isn't "delayed again" — it's that Google walked away from the plan entirely, and did so more than a year ago.

Whatever happens with cookies, some tools never needed them in the first place — ClearText Editor processes everything locally in your browser, with nothing sent to a server to track.

The Actual Turning Point: April 2025

After years of postponements, Google's Privacy Sandbox team announced in July 2024 that it would abandon automatic blocking in favor of a "user choice" prompt — letting people decide for themselves whether to allow third-party cookies, rather than Chrome disabling them by default. That prompt never shipped either. On April 22, 2025, Google confirmed it would not introduce the standalone consent prompt, and restated its intention not to deprecate third-party cookies in Chrome at all. That announcement, not anything published in 2026, is the actual end of the deprecation story.

What Happened to Privacy Sandbox

Privacy Sandbox was the replacement system Google spent years building — a set of browser-level APIs (Topics, Protected Audience, Attribution Reporting, and others) meant to support ad targeting and measurement without third-party cookies. With cookies staying put, most of that infrastructure lost its reason to exist. On October 17, 2025, Google formally announced it would retire the majority of these APIs, citing low industry adoption. The UK's Competition and Markets Authority, which had spent four years investigating Google's original cookie-blocking plan over antitrust concerns, closed its case the same month and released Google from its related commitments — concluding that its competition concerns no longer applied, since the underlying plan to block cookies was gone.

The Privacy Sandbox retirement is worth sitting with for a moment: Google spent roughly five years and considerable engineering effort building a cookie replacement system, then wound most of it down within months of confirming cookies weren't going anywhere. The regulatory investigation aimed at preventing anticompetitive harm from the blocking plan closed not because the plan succeeded, but because the plan no longer existed.

A Caution: Some 2026 Coverage Still Gets This Wrong

Searching this topic in 2026 turns up a genuine split in accuracy. Some published content — including at least one piece dated well into this year — describes Google as having moved the deprecation deadline earlier, framing 2026 as a countdown to an imminent cutoff. That doesn't match the documented record: Google didn't move the deadline up, it eliminated the deadline by abandoning the plan in April 2025. It's a useful reminder that a topic which was genuinely uncertain and fast-moving for years can keep generating confident-sounding "next deadline" content well after the underlying story actually resolved.

The Part That Was True the Entire Time

While the Chrome story dominated headlines, other major browsers had already solved this independently, and without waiting on Google. Safari has blocked third-party cookies by default since 2020. Firefox blocks known trackers by default through its Enhanced Tracking Protection. Brave blocks third-party cookies entirely. None of that changed based on anything Google announced or reversed — those browsers made their own decisions years ago and never revisited them.

Because Chrome still holds roughly two-thirds of global browser traffic, its decision to keep cookies has an outsized practical effect — but it was never the whole picture. Depending on the audience a given site serves, a meaningful share of visitors were already browsing with third-party cookies blocked well before this entire saga started, and nothing about Google's reversal changes that.

What This Means Practically Right Now

For anyone who spent the past few years preparing for a cookieless future — building consent flows, testing Privacy Sandbox APIs, budgeting for a transition — the practical situation in late 2026 is that the transition they prepared for isn't happening on Google's end. Third-party cookies remain fully functional in Chrome, the browser most people use. That doesn't mean privacy pressure on tracking has disappeared entirely: regulation like the EU's ongoing consent requirements, and the roughly 20% of global browser traffic that already blocks third-party cookies by default, keep first-party and consent-based approaches relevant regardless of what Chrome does. But the specific, dated deadline that much of the ad-tech industry spent years planning around no longer exists.

This same gap — between what a company's roadmap promises and what a browser or platform actually enforces on the ground — is part of why relying on tools that don't need cross-site tracking in the first place remains a sound default. The broader question of what "processed on your device" actually protects against, separate from any single company's cookie policy, is covered in more detail in the earlier post on what processed locally really means.

---

The honest summary: third-party cookies were never actually deprecated in Chrome. Google confirmed on April 22, 2025 that the plan was cancelled, formally retired most of the Privacy Sandbox replacement system on October 17, 2025, and UK regulators closed their four-year investigation the same month because the underlying concern no longer applied. Safari, Firefox, and Brave block third-party cookies by default regardless of anything Google does — and have for years. If a 2026 article frames this as an approaching deadline, it's describing a story that already ended.