Browser Fingerprinting Protection: Randomize, Blend In or Block

A page can ask the browser which graphics card it runs on, through WebGL, the browser's 3D graphics interface. An unprotected browser answers with the exact model. Brave answers with one word, "Brave", for the vendor and the renderer alike. That is deliberate: Brave decided the model is too identifying to give out, which makes it the simplest case of browser fingerprinting protection.

A fingerprint works for a tracker only when it is distinctive (few other browsers match it) and stable (it survives from one session to the next). Defenses go after one or the other, and most browsers mix them.

A browser can make your fingerprint shared, shifting or unreadable. It can't make it disappear, because a page can't render without reading some of those values.

Three kinds of browser fingerprinting protection

• Blend in. Many browsers report identical values, so the fingerprint stops being distinctive: it points to a crowd instead of a person. Tor Browser and Mullvad Browser are built on this.
• Keep changing. The browser adds small random noise to what it returns, so the fingerprint is not stable: the same machine looks different to every site and again after a restart. Brave is built around this.
• Block. The browser stops scripts that appear on lists of known fingerprinters, or refuses to return the data at all, so there is nothing to read. Firefox, Safari, Edge and DuckDuckGo lean on lists like this, and Tor Browser also withholds canvas image data.

Which move fits depends on the value. Canvas pixels and audio samples survive a nudge nobody can see. A name does not: a GPU model can only be replaced by something generic.

Brave fingerprinting protection: noise for pixels, one name for the GPU

Brave calls its noise farbling. Canvas readback, Web Audio output and WebGL values come back slightly altered, by an amount nobody notices on screen. The noise comes from a seed that is new every session and different for every site. Inside one site and one session the answers stay consistent, so pages keep working; across sites and across restarts they don't match. An embedded tracker doesn't get a seed of its own. It inherits the one of the page it sits on, so the same tracker reads different values on two sites and can't join the visits. Fingerprinting scripts typically hash many values into one ID, so changing a single input changes the whole hash.

For names, Brave blends in. In version 1.93, rolled out from August 2026 on desktop and Android, the WebGL vendor and renderer strings both come back as "Brave", the WebGPU adapter details are emptied, and the list of supported WebGL extensions gets noise, because that list differs by GPU and driver. Every Brave user presents the same graphics card, which makes a crowd, though the string also tells a site which browser it is talking to.

Firefox and Safari fingerprinting protection: some noise, some lists

Since Firefox 151 (May 2026), desktop Firefox changes the canvas image a script exports, differently in each browsing session, in every window. Its standard tracking protection also blocks the known fingerprinters. Private windows and Strict mode add more, including a coarse CPU core count. The pixel noise they are meant to add on top doesn't currently run next to the lighter mode, so a script that reads canvas pixels directly still gets the real ones. Tor-style uniformity (the resistFingerprinting preference) is an advanced setting, off by default.

Safari takes two routes. In Private Browsing it adds tiny noise to 2D canvas and WebGL readback and to Web Audio samples, and it reports the screen as the same size as the window; the same set can be turned on for every tab in Advanced settings. In normal windows, since Safari 26 (September 2025), known fingerprinting scripts can't reliably read screen size, CPU core count, speech voices, audio or 2D canvas, and can't store long-lived data. That layer works from a list; a script that isn't on it still reads a normal window.

Browser fingerprinting protection compared

The table covers one question. What each browser also blocks, sends home, hides with a built-in VPN or does with AI is in the full comparison of 11 browsers.

When protection makes you stand out

Blending in works only where the crowd is big. A US English setting is common on most sites, yet on a small foreign-language site the same setting can single you out, and a browser can't know how many visitors resemble you on each site.

The same logic punishes rare setups. Brave dropped its Strict fingerprinting mode: it broke sites, and fewer than 0.5% of users ran it, a group small enough to stand out. Tor Browser doesn't let you choose which operating system you appear as, because any choice would make users more unique. Changing many settings, or stacking extensions that rewrite values, tends to make a browser rarer, not more private.

Randomization has the opposite limit. It is a best-effort defense against trackers working at web scale, and a determined attacker aiming at one person can try to filter the noise out.

What incognito and a VPN leave alone

A private window in Chrome leaves canvas and GPU values as they are. In Firefox and Safari it switches on the extra protections above. A VPN swaps the IP address and leaves every value measured inside the browser untouched. Below the browser, the first TCP packet still shows the operating system's network stack, whatever the user agent claims, and no browser setting edits it.

How to check what your browser really does

1. Open the Privacy & Trust Index and let the scan finish. Note the result on the Canvas Fingerprint card and the WebGL renderer under Graphics & Media Fingerprint. A stable canvas hash is shown there too.
2. Close and reopen the browser, or use a private window, and scan again. A hash that changed is being randomized. One that stayed the same is a stable ID.
3. Read the card. CANVAS LEAK means the drawing was identical every time and lowers the Privacy score. IDENTITY SHIFTING means it changed between reads, PROTECTED means light noise, CANVAS INTERCEPTED means a tool is handling it, CANVAS BLOCKED means the canvas is off. None of the five results lowers the Trust score.
4. Read the renderer string. A generic or empty value is protection; a string that names your actual GPU is public to every page.

A single scan can't measure how rare you are, because rarity depends on who else visits. The canvas leak guide explains each result and how the browsers above draw the line.