You cannot delete a fingerprint, but you can make yours far less distinctive. A realistic, step-by-step guide to blending in — and the common mistakes that backfire.
On this page
If you cannot delete a fingerprint the way you delete a cookie, what can you actually do about it?
That is the question that follows once you understand how browser fingerprinting works. The frustrating answer is that there is nothing stored to remove. But you can change the game. The goal is not to hide; it is to look ordinary. What follows is what actually reduces your fingerprint, in rough order of impact, and the popular “fixes” that quietly make things worse.
The rule that runs against instinct
The single most important idea in fingerprint resistance is this: standing out is the problem, so being unusual is not the solution. Every rare setting, exotic font, or obscure extension you add makes your combination of traits more distinctive, not less. A visitor with a spoofed user agent, three privacy extensions and a custom font list is often easier to single out than someone on a stock browser.
The short version
Effective defence means joining the largest possible crowd of identical-looking users. Keep that in mind and the rest follows.
What actually reduces a fingerprint
Work down this list, because the order is the order of impact.
- Use a mainstream browser at its defaults. The most common browser and operating system combinations produce the most common fingerprints. A default installation of a popular browser on a popular OS puts you in a huge crowd, so resist the urge to heavily customise the parts that are visible to websites. Check what your setup currently announces with the user agent tool — if it already looks completely standard, that is a good sign.
- Consider a browser that normalises fingerprints. Some browsers treat fingerprinting as a threat to design against, not just a nuisance. The Tor Browser is the gold standard: it deliberately makes every user look as similar as possible — same window size, same fonts, same reported values — so that individual fingerprints collapse into one shared profile. It is slower, but nothing else comes close. Brave randomises certain signals like canvas and audio on each session, which frustrates attempts to build a stable identifier. Firefox offers built-in resist-fingerprinting protections that block or standardise many of the usual signals.
- Rein in your fonts. The set of installed fonts is one of the richest signals there is. See how exposed you are with the font detection test; browsers with fingerprinting protection limit what sites can enumerate.
- Rein in canvas and WebGL. These rendering signals are extremely stable, and browsers that randomise or block them remove one of the tracker’s best tools.
- Rein in screen and window size. An unusual resolution or a maximised window at an odd size is distinctive, and Tor addresses this by nudging everyone toward standard window dimensions.
The fixes that backfire
Plenty of well-meaning advice does more harm than good. Avoid these:
- Spoofing your user agent by hand. It rarely matches the rest of your fingerprint, and the mismatch itself is a glaring signal.
- Piling on privacy extensions. Each one can add detectable behaviour. A short, well-chosen set beats a long list.
- Chasing a “unique” look. Uniqueness is the enemy here. If a tweak makes you rarer, it is working against you.
- Assuming a VPN helps. A VPN changes your IP address, which is valuable, but it does not touch your fingerprint at all. They are separate problems, as we explain in cookies versus fingerprinting.
Run both tests
Perfect anonymity is not the aim for most people, and it is not achievable without real inconvenience. The point is not to disappear — it is to stop being the easiest person in the room to single out. A sensible middle ground — a mainstream browser with sane privacy settings, or Brave for everyday use and Tor when it truly matters — dramatically reduces casual tracking without upending how you browse.
Whatever you choose, measure it. Run these two: the fingerprint test before and after each change, and the font detection test to see how much of your type list a site can enumerate. Watch how your uniqueness score moves. Seeing the number drop is the only way to know a tweak actually helped rather than backfired.