Fingerprintscore Chart form FS-1 Rubric 1.0.0 Priors: assumed · Counts: real Donut Browser ↗

Signals · graphics · counted, not scored by the rubric

WebGL output

A hash of the WebGL parameter set: maximum texture sizes, supported extensions, shader precision formats and dozens more limits.

Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.


How a page reads it

The collector reads every parameter it can from a WebGL context and hashes the whole set. Two browsers share the value only when every limit and extension matched.

Why it splits browsers apart

Each combination of GPU, driver, operating system and browser engine produces its own set, so this hash separates graphics stacks that share a renderer name.

What moves it

A driver update, a browser update that changes the ANGLE backend, or a different GPU.

What moving it costs

Spoofing the renderer string without the parameters leaves a renderer that claims one GPU and limits that describe another.

How the count is made

Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.


Questions about webgl output

Why is my WebGL hash shared by so few devices?
Because it needs every one of dozens of values to match. Different drivers and browser builds change a few limits each, and any one change is a different hash.
Does a browser update change it?
Sometimes. A new graphics backend or a new extension changes the set, which is why this value is not part of the device key.

Next

Emoji rendering: A hash of how this browser draws a set of emoji: their sizes and pixels with the system emoji font.

Score this browser on the chart form →

Where the pens move

A value patched in the page is a patched value. Set in the engine, it is just a value.

Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.

It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.

Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.

Download Donut Browser Source on GitHub — AGPL-3.0 ↗