Why fingerprinting is different from a leak
A DNS or WebRTC leak exposes a specific piece of data (an IP address) that a fix either blocks or doesn't. Browser fingerprinting is different: it combines many small, individually harmless signals — canvas rendering quirks, WebGL renderer strings, audio processing output, installed fonts, screen size, timezone — into a combination that can be unique enough to re-identify you across visits, even without cookies. There is no single switch that "fixes" fingerprinting; the goal is to reduce how distinctive your combination of signals is.
Step 1 — See your current fingerprint surface
Open the Browser Fingerprint Test and run the four subtests: Canvas, WebGL, Audio, and Font. These show what your browser currently exposes on each signal. Write down or screenshot the results so you have a "before" to compare against.
Step 2 — Firefox: enable resistFingerprinting
Firefox has a built-in, comprehensive anti-fingerprinting mode inherited from the Tor Uplift project.
- In the Firefox address bar, type
about:configand press Enter. - Click "Accept the Risk and Continue".
- Search for
privacy.resistFingerprinting. - Double-click it to set the value to
true. - Restart Firefox.
This randomizes canvas and audio readback per session, restricts the WebGL parameters a page can query, rounds timezone to UTC, and limits font enumeration to a fixed list shared across all Firefox users on resistFingerprinting — rather than reporting your specific installed fonts.
Trade-off: resistFingerprinting can break some sites (canvas-based CAPTCHAs, certain WebGL-heavy web apps) and changes your timezone display to UTC everywhere. Test it on your regular sites before relying on it daily.
Step 3 — Brave: check Shields fingerprinting settings
Brave applies fingerprint randomization ("farbling") by default, and lets you adjust its strength per site.
- Click the Brave Shields icon (the lion) in the address bar.
- Open Advanced controls.
- Find "Fingerprinting" and choose Standard (randomizes canvas, audio, and WebGL output per site per session — the default) or Strict (blocks more aggressively, more likely to break sites).
Standard mode is a reasonable default for daily browsing. Strict mode trades more site breakage for less fingerprinting surface — use it only on sites where you don't need full functionality.
Step 4 — Safari: confirm built-in protection is on
Current Safari versions include fingerprinting protection enabled by default.
- Open Safari Settings (or Preferences on older macOS) > Privacy.
- Confirm "Advanced Tracking and Fingerprinting Protection" is switched on.
Safari also limits the information available to fingerprinting scripts by reporting a simplified system font list and restricting some Canvas/WebGL API access on suspected tracking scripts, without requiring configuration.
Step 5 — Chrome: use an extension, or switch to Brave
Chrome does not include built-in fingerprint resistance. Two practical options:
- Extension route: install a reputable privacy extension that specifically targets canvas/WebGL/audio fingerprinting (check current extension store ratings and permissions before installing — a poorly-chosen extension can itself become a fingerprinting or tracking risk).
- Browser route: use Brave for privacy-sensitive browsing instead of Chrome. It is Chromium-based (so most extensions and sites work the same way) but includes fingerprint farbling by default — see Step 3.
Step 6 — Verify the change
Return to the Browser Fingerprint Test and re-run the canvas, WebGL, audio, and font subtests. You should see values that differ from your "before" results, are reported as restricted/blocked, or match a common baseline shared by many other users of the same setting — rather than a value unique to your machine.
A limit worth understanding
Reducing fingerprinting signals is not the same as becoming unidentifiable. A browser configuration that is itself unusual — for example, being one of a very small number of people with resistFingerprinting enabled, on an otherwise distinctive setup — can sometimes stand out precisely because it's rare, even though each individual signal is blocked or randomized. This is a known trade-off in fingerprinting defense: blending in with a common configuration is sometimes more effective than maximizing individual protections. Treat these steps as a meaningful reduction in casual, ad-network-style fingerprinting, not a guarantee against a determined, resourced adversary — see how to think about your privacy risk for which level of protection actually matches your situation.
Related guides and tools
Frequently asked questions
Will these changes make me completely un-fingerprintable?
No. They reduce the distinctiveness of individual signals, but a fully unique combination can still exist, and a sufficiently motivated adversary can combine multiple weaker signals. These steps target casual, ad-network-style fingerprinting, not a targeted, resourced attacker — see how to think about your privacy risk for that distinction.
Does incognito or private browsing mode block fingerprinting?
No. Private browsing modes clear cookies and history after the session, but they don't change what your browser's APIs report to a page. Canvas, WebGL, audio, and font signals are the same in private mode unless you separately enable an anti-fingerprinting setting.
Why does Firefox's resistFingerprinting change my timezone?
Reporting your exact timezone is itself a fingerprinting signal (it narrows your likely location). resistFingerprinting rounds the reported timezone to UTC for every user who enables it, so this specific signal becomes identical across all of them instead of revealing your real one.
Do ad blockers like uBlock Origin stop fingerprinting?
They help indirectly by blocking many tracking scripts before they run, but they don't randomize or restrict the canvas/WebGL/audio/font APIs themselves the way resistFingerprinting or Brave's farbling do. A script that isn't blocked by a filter list can still fingerprint a browser with a standard ad blocker installed.
Is a VPN enough to stop fingerprinting?
No. A VPN changes your IP address and apparent network location, but fingerprinting signals come from the browser and device, not the network path. A VPN and fingerprint-reduction settings address different exposure types and are complementary, not substitutes for each other.