Signals · graphics · counted, not scored by the rubric
WebGPU adapter
The WebGPU adapter's vendor and architecture, or no adapter, or unavailable.
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 asks navigator.gpu for an adapter and reads its info. Where WebGPU is missing the value is unavailable; where it exists but no adapter is granted, it is no adapter.
Why it splits browsers apart
The architecture field names the hardware generation (for example an Apple or Intel family), which is finer than the WebGL vendor and harder to keep consistent when spoofing.
What moves it
A browser version that adds or removes WebGPU, a graphics driver update, or a flag that disables it.
What moving it costs
A spoofed WebGL renderer that leaves the real WebGPU adapter in place tells on itself: the two APIs describe the same GPU.
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 webgpu adapter
- Why is WebGPU unavailable in my browser?
- Support is still uneven. Some browsers ship it only on some operating systems or behind a setting, and unavailable is then the shared value.
- Is WebGPU a new fingerprinting risk?
- It repeats what WebGL already reveals, in more detail. The risk is less the extra detail than the chance that a spoofed WebGL value and a real WebGPU value disagree.
In the same group
Next
WebGL output: A hash of the WebGL parameter set: maximum texture sizes, supported extensions, shader precision formats and dozens more limits.
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.