How to Get Rid of Tracking Cookies (and What It Fixes)

If you've searched for how to get rid of tracking cookies, you've probably noticed that every browser handles it a little differently, and that clearing cookies once doesn't make the tracking stop for good. Here's what each major browser actually lets you do, which ones block third-party cookies automatically, and where cookie clearing runs out of road.

How do I clear tracking cookies from my browser?

Chrome (desktop). Click the three-dot menu at the top right, then go to Delete browsing data. Google's own instructions walk through it this way: "At the top right, select More Delete browsing data... Choose a time range, like Last hour or All time... Select Cookies and other site data... Check other items you want to delete... To confirm, select Delete data," according to Google's Chrome Help page on managing cookies. Pick "All time" if you want a full wipe rather than just a recent window.

Safari (iPhone). Go to Settings, tap Apps, then Safari, then Advanced, then Website Data. From there, tap Remove All Website Data and confirm with Remove Now. Apple describes this as clearing "data that's used for tracking and by websites to save login information for faster browsing," per Apple's support page on deleting Safari history and cookies. Expect to be logged out of sites you'd saved passwords for, since that data goes too.

Firefox. Firefox's own documentation focuses less on manual deletion and more on its built-in blocking, since the browser already isolates third-party cookies by default. If you want to clear stored cookies anyway, you can do so from Firefox's privacy and security settings; the tracking-protection controls that handle most third-party cookies automatically are covered in the next section, per Mozilla's support article on third-party trackers.

Microsoft Edge. Open the three-dot menu, go to Settings, then Privacy, search, and services, to manage cookies. To check what's currently stored, Microsoft's instructions note you can view stored cookies by selecting Cookies, then clicking "See all cookies and site data to view all stored cookies and related site information," according to Microsoft's support page on managing cookies in Edge.

Can I block third-party cookies instead of clearing them?

Clearing cookies is a one-time cleanup. Blocking third-party cookies stops new ones from being set in the first place, which is generally the more durable fix.

Chrome: Go to Settings, then Privacy and security, then Third-party cookies, and choose "Block third-party cookies." Google notes that "if you block third-party cookies, all third-party cookies from other sites are blocked unless the site is allowed on your exceptions list," per Google's Chrome Help cookie settings page.
Safari (iPhone): Go to Settings, tap Apps, choose Safari, tap Advanced, and turn on Block All Cookies, then confirm with Block All. Apple warns this is more aggressive than a third-party-only block and "removes all existing cookies and website data," per Apple's Safari cookie instructions. It can also break sign-ins: "You will likely not be able to sign in to a site, even when using your correct username and password," Apple cautions.
Firefox: Enhanced Tracking Protection already does this automatically. Switching it to Strict mode "blocks all cross-site (third-party) cookies, enhancing your privacy by preventing cross-site tracking," according to Mozilla's third-party trackers support page.
Edge: Go to Settings, then Privacy, search, and services, select Cookies, and enable the "Block third-party cookies" toggle, per Microsoft's Edge cookie management guide. Microsoft flags the tradeoff directly: "doing this might prevent some pages from displaying correctly, or you might get a message from a site letting you know that you need to allow cookies to view that site." If a trusted site breaks, Edge lets you allow it individually under Cookies, then "Allowed to save cookies," using the Add site option.

Which browsers block tracking cookies by default?

Not all four handle this the same way out of the box, and the differences matter if you never touch a settings menu.

Safari and Firefox block third-party cookies by default and have for years, through Safari's Intelligent Tracking Prevention and Firefox's Enhanced Tracking Protection, independent of whatever Chrome decides to do, according to Cookiebot's explainer on third-party cookies and Google's policy. Chrome's own help page confirms one exception: inside Incognito mode, third-party cookies are blocked by default, but that protection doesn't extend to normal browsing windows, per Google's Chrome Help page on managing cookies.

Chrome itself ships with third-party cookies allowed unless you turn blocking on. Google spent years planning to phase them out, but reversed course. According to Cookiebot's explainer on Google's third-party cookie reversal, Google scrapped its deprecation plan in mid-2024 and, by April 2025, confirmed Chrome would not add a replacement consent prompt either, so third-party cookies stay active in Chrome by default, managed only through the browser's existing privacy settings. The replacement tracking technology Google had been building, called Privacy Sandbox, didn't survive either: Google abandoned those APIs in October 2025. If you use Chrome, flipping on the manual block described above is currently the only way to get Safari- or Firefox-level default protection.

Does clearing cookies actually stop all tracking?

No. Clearing or blocking cookies addresses one tracking method, not every one. Two gaps are worth knowing about specifically.

The first is browser fingerprinting, which identifies your device using characteristics like screen size, fonts, and configuration rather than a stored file, so there's nothing to delete. For a full breakdown of how that works and why it survives a cookie wipe, see Privacy Unpacked's guide to browser fingerprinting.

The second is server-side tracking, where a site logs your activity on its own servers using your account, IP address, or other identifiers rather than a cookie on your device. As the industry shifts away from third-party cookies, Cookiebot's explainer notes that site owners are increasingly leaning on exactly this kind of first-party data collection, something clearing your browser's cookie jar does nothing to touch.

A first-party example surfaced in federal government code in September 2026: Login.gov, the identity system behind the new America.gov portal, added a cookie called nds_experiment_uuid that is set using Ruby on Rails' cookies.permanent function, which the framework's own documentation says expires in 20 years. According to Biometric Update's reporting, the identifier can be generated before a visitor signs in, gets attached to Login.gov's analytics events, and is not deleted even when a user opts out of the interface experiment that created it. Login.gov's privacy assessment, posted on GSA's site, does not address this particular identifier, a reminder that deleting cookies in your own browser only removes what's already been set; a site can simply issue a new one on your next visit, with a lifespan and purpose you can't see from the browser settings alone.

If you're on a phone and want to limit tracking beyond the browser itself, including tracking by apps, Privacy Unpacked also has a guide on turning off ad tracking on iPhone and Android.

Checklist: getting rid of tracking cookies

Clear what's stored: Chrome's Delete browsing data (cookies and site data); on iPhone, Settings > Apps > Safari > Advanced > Website Data > Remove All Website Data, per Apple's support page.
Stop new ones: turn on third-party cookie blocking in Chrome (Settings > Privacy and security > Third-party cookies) and Edge (Settings > Privacy, search, and services > Cookies); set Firefox's Enhanced Tracking Protection to Strict. Safari and Firefox block by default.
Expect some breakage, and allow trusted sites individually rather than switching protection back off.
Remember what survives a cookie wipe: browser fingerprinting and server-side tracking.

Updated 15 October 2026: Added a real-world example — a newly discovered 20-year Login.gov tracking cookie tied to the America.gov portal — to illustrate why clearing cookies doesn't permanently stop tracking.