Privacy Browsers Compared: What Each One Actually Blocks

Last updated: October 29, 2026 · Based on published browser documentation

Privacy browsers are usually compared on a list of features: tracker blocking, cookie handling, fingerprint resistance, built-in encryption, a bundled VPN. The lists are close to useless on their own, because two browsers with identical feature checkboxes can behave very differently depending on what defaults they ship and what they let you change. This guide compares them by mechanism instead — what each browser does by default, what it lets you adjust, and what each of those choices costs you in everyday use.

Table of contents

• Three different things called “blocking”
• Defaults matter more than settings
• Browser by browser, mechanism by mechanism
• What blocking breaks, and whether it is worth it
• How to choose for your own use
• FAQ
• Bottom line

Three different things called “blocking”

Marketing uses one word for three mechanisms that behave differently.

• Network-level blocking. The browser refuses to resolve or connect to a known tracking domain, or blocks the request at the network layer. Cheap, effective against known third parties, and it never breaks first-party functionality because the page itself is untouched.
• Content-level blocking. The browser loads the page and then removes identifiable elements — a tracking script, a pixel, a beacon — from what the page runs. More thorough against the trackers that hide inside a page, and more likely to cause breakage, because it is modifying the page's behaviour after the fact.
• Reducing identity signals. The browser makes the requests that remain look less like a unique visitor: standardising the user agent, normalising fonts and canvas output, resisting fingerprinting so that two visits look like the same browser rather than two different ones. This does not block anything. It makes you harder to tell apart from other people who are not you.

These compose, and a browser that does all three is doing more than one that does only the first. The important difference between products is rarely which mechanisms exist and almost always which are on by default and whether you can turn them off.

Defaults matter more than settings

Every browser in this category ships with a settings page full of toggles, and the settings are where the marketing stops and the behaviour begins. Three questions settle most comparisons.

• What is on when you install it? A tracker blocker that ships disabled is a feature, not a protection. Note that some browsers enable protection only in their private windows, which is a reasonable design and a common source of confusion.
• Can you turn protection down? If a site breaks and there is no way to allow that one tracker, people will eventually disable the whole thing. A per-site control, and an obvious one, matters more than any number on a features list.
• What happens to the fingerprint defence? The measures that make you look like everyone else often degrade the page rendering, because sites detect the standardisation and compensate. Whether that is visible depends on the browser and the site.

A corollary: the most protective configuration is rarely the best one for a person whose time is better spent elsewhere. The protection you actually keep enabled is worth more than the protection you disable after a week of broken pages.

Browser by browser, mechanism by mechanism

Rather than a table of features, here is how the main approaches differ in practice.

The integrated browser. The largest browser vendors ship privacy controls inside the browser everyone already uses: a tracking-protection setting that blocks third-party cookies by default in some configurations, an anti-fingerprinting option, and a private mode that reduces cross-site tracking state. The strength is that there is nothing to install and nothing to keep configured; the weakness is that the control surface is comparatively limited, and in some cases the strongest options are behind a paid tier or a flag.

The blocking browser. A browser whose distinguishing feature is an integrated blocking list that is on by default, with the ability to allow or block per site. The strength is that protection is the default rather than an opt-in; the weakness is that it is a different browser with a different extension ecosystem, and the list is a published set of names, which is the same limit described in DNS-level blocking at home.

The anonymity-focused browser. A third approach, built around making the browser itself resist fingerprinting: standardised screen and hardware characteristics, partitioned storage, and a design assumption that you should look like a large group of other users rather than like yourself. The strength is that it addresses the trackers that content-level blocking cannot reach, because they are not identifiable in the first place. The weakness is that the standardised characteristics can make sites behave oddly, and that this approach sits on top of rather than instead of blocking.

The build-it-yourself combination. A mainstream browser with a blocking extension, and perhaps a fingerprint-resistance extension alongside it. The strength is flexibility and familiarity; the weakness is that everything depends on extensions staying installed, updated and compatible with each other and with the browser, and that no single switch controls the whole picture.

What blocking breaks, and whether it is worth it

Every mechanism has a cost, and knowing which is which lets you make a sensible trade.

• Known trackers blocked. Minimal breakage. Some sites depend on a blocked script for a non-tracking function, and the fix is a per-site allow.
• Cookies and storage partitioned. Low breakage. This is the mechanism behind most “sign out of everything” complaints, and it is a deliberate trade of convenience for isolation.
• Fingerprint resistance. Moderate breakage on some sites, because standardising characteristics triggers fallback code and occasionally a degraded interface. It is also invisible to you most of the time, which makes it hard to attribute a problem to it.
• Aggressive content rewriting. The highest breakage rate, because it changes what the page is allowed to do. Sites that rely on injected scripts can fail in ways that look like a broken site rather than a blocked one.
• Built-in network protection. Occasionally causes connectivity problems in networks that inspect or rewrite traffic, and it can interfere with enterprise setups.

The honest summary is that the more a browser hides you, the more likely a site is to behave oddly. The question is whether that trade suits you, and for many people a moderate setting that stays on indefinitely beats an aggressive one that gets switched off.

How to choose for your own use

1. Start from your actual behaviour. If you use one browser for everything and never change its settings, a different browser will not help unless it protects by default. If you are willing to install one extension and keep it, a mainstream browser plus that extension is fine and less disruptive.
2. Decide what you are protecting against. Tracking that follows you between sites is a different problem from tracking that follows your device, and different tools address different halves.
3. Try the free option first. The privacy controls already in your browser, turned on, are free and require nothing. Establish whether they are sufficient before paying for anything.
4. Test on the sites you use daily. Sign-in, payments, video calls, and whatever you use for work. These are the ones that must work every time.
5. Check the per-site controls work. Break something deliberately, then fix it. A control you cannot find when you need it is not a control.
6. Decide about the ecosystem. A privacy browser with fewer extensions is a browser where your tooling does not work. If your workflow depends on extensions, check before switching.
7. Re-evaluate after a month. The right configuration is the one you will still have switched on.

The layered picture, including what a network-level tool does and does not add on top of browser-level tools, is in ad and tracker blocking layers.

FAQ

Is a privacy browser worth switching to?

If you would keep the protections on, yes, because protection that ships enabled beats protection you have to remember to configure. If you would spend the first fortnight fighting broken pages and then switch back, a mainstream browser with one well-chosen extension will serve you better. The deciding question is which version you will actually keep.

Do private windows make me anonymous?

No, and the confusion here causes real problems. A private window stops local history and cookies being stored on that device and separates that session's state from your main one. It does not hide your IP address, it does not make you unidentifiable to fingerprinting, and it does not affect what a server records about the request.

Do these browsers slow the page down?

Some do, and the mechanism is usually clear: blocking something the page needed removes work it would have done, and fingerprint resistance adds processing. On a modern machine the difference is usually small. The cases where it is noticeable are heavy pages, and low-powered hardware.

Does a built-in VPN in a browser help?

It encrypts the connection between your browser and its provider, which stops the local network seeing your traffic. It is narrower than a system-wide VPN, it routes through a provider you then depend on, and it does not cover the applications on your device. As a layer in a stack it is reasonable; as a replacement for a system-wide tool it is not.

What about the browser's own tracker protection?

It is worth turning on if you have not, because it is free, already installed and requires no decisions. It is usually a network-level blocklist, which means it handles known third parties well and leaves first-party measurement alone. That is the same division of labour described in DNS-level blocking at home, applied inside the browser.

Bottom line

What matters is not which browser has the longest feature list but three quieter things: what is protected by default, whether you can adjust it per site, and whether you will leave it switched on. Start by turning on the privacy controls already in the browser you use, because they are free and need no decisions. If the gap that remains is cross-site tracking you can feel, a browser with blocking enabled by default is the step up. If the gap is being uniquely identifiable, look at the fingerprint-resistance approach and accept the rendering trade-off. And keep the layer model in mind throughout: the network removes requests that never needed to be made, the browser handles what the page does with the ones that were, and no single layer does everything.

If you have decided which layer you want to strengthen, the link below goes to our own page for the category.

See current blocking tool plans →