WebGL Report
Your graphics card, its driver limits and every extension it exposes - as any website can read them.
What this page read
🖐️ One vector is not a fingerprint
Nothing on this page identifies you on its own - it describes a class of machine. What makes a browser recognisable is several stable signals at once, which is what the full test measures and scores.
🖐️ Run the full fingerprint testWebGL Report
WebGL gives web pages access to your graphics hardware, and with it a long list of parameters describing that hardware: the renderer string naming your GPU, the driver limits, the shading language version, and the full set of extensions your driver supports. None of it requires permission. This page reports every value a site can read, in full rather than truncated.
Why the renderer string is the strongest line
Most of the values here describe a category of hardware. The unmasked renderer string is different: it frequently names the exact GPU model, sometimes down to the driver revision. In a population of web users, that alone splits everyone into fairly small groups, and it is stable across browsers on the same machine because it comes from the driver rather than the browser. Chrome and Firefox both expose it through WEBGL_debug_renderer_info, which is enabled by default.
The extension list is its own signal
Two machines with the same GPU can still differ in which extensions their drivers expose, because that set changes with driver version, operating system and browser build. The count alone is informative and the exact list more so, which is why the complete list is printed on this page rather than summarised. It is worth reading it as a tracker would: not "does this machine support X" but "how many other machines support exactly this set".
What reduces it
Firefox can be told to withhold the unmasked renderer, which replaces the specific model with a generic string. Brave reports a standardised value. Disabling WebGL entirely removes the vector but breaks maps, 3D content and a growing number of ordinary interfaces. As with the other vectors here, this is measured inside the browser, so no VPN or proxy changes any value on this page.
WebGL Report - FAQ
Common questions about this specific signal.
What does the WebGL report reveal about me?
Primarily your graphics hardware: the GPU model and vendor, the WebGL and shading language versions, driver limits such as maximum texture size, and the list of extensions your driver exposes. Together these describe your machine precisely enough to be a strong component of a browser fingerprint, and no permission prompt stands between a website and any of it.
Why does my GPU model show up on a website?
Because WebGL was designed to let pages adapt to the hardware they are running on, and the WEBGL_debug_renderer_info extension exposes the unmasked renderer and vendor strings for that purpose. It is genuinely useful for games and 3D applications choosing quality settings. It is also readable by any page that asks, including ones with no 3D content at all.
Should I disable WebGL?
For most people, no. Disabling it removes this vector but breaks map interfaces, 3D viewers and an increasing amount of ordinary web content, and being one of the few visitors with WebGL switched off is itself a distinguishing signal. Withholding the unmasked renderer string, which Firefox supports, removes the sharpest line without breaking rendering.
Is the WebGL report the same in every browser on my computer?
The hardware values are largely the same, because they come from the driver rather than the browser - which is what makes this vector useful for linking activity across browsers on one machine. The extension list and reported limits can differ between browsers, since each ships its own graphics layer and applies its own policy about what to expose.
🧰 Related tests
Every test runs entirely in your browser - nothing is stored unless you choose to share the result.