WebGL Fingerprint / GPU
See your GPU vendor, renderer and the WebGL limits any site can read.
How this test works
WebGL exposes the GPU vendor and renderer strings close to verbatim, along with dozens of numeric capability limits and the list of supported extensions. That combination is considerably more specific than a canvas hash — it often identifies the exact graphics chip and driver version, which narrows a population far faster than screen size or language. This page reads those values, shows you the renderer string in plain text so you can see precisely what is being handed over, hashes the rest, and discards everything.
What the results mean
- Renderer
- The GPU as reported. Where it names a specific chip, this is one of the most identifying single values a page can obtain.
- Vendor
- The GPU manufacturer, or a generic string where the browser has masked it.
- Capability values read
- How many distinct numbers and extension names contributed. More values means finer discrimination.
- Unavailable
- WebGL is disabled or blocked, which removes a large surface.
Common problems and fixes
- My renderer says something generic like ANGLE
- That is the browser masking the real value, which is what you want. Some browsers now return a generic renderer to every site by default.
- It names my exact graphics card
- That is the normal behaviour where masking is not applied, and it is why WebGL is such a strong signal — very few people share a specific GPU and driver combination.
- WebGL is unavailable
- Either it is disabled or the browser is blocking it. Either way the surface is closed, at the cost of breaking sites that render 3D.
Frequently asked questions
Why is WebGL a stronger fingerprint than canvas?
Because it names hardware. A canvas hash reflects rendering differences; WebGL frequently hands over the actual GPU model and driver, plus dozens of capability numbers, which together discriminate far more finely.
Should I disable WebGL?
It closes a significant surface but breaks maps, 3D and some video features. Browsers that mask the renderer string get most of the benefit without that cost.
Does a common GPU make me safer?
Somewhat, but only for this signal. Fingerprinting combines many surfaces, so a common GPU alongside an unusual font set is still identifiable.