Check what WebGL reveals about your graphics setup
Run a local WebGL fingerprint test to see the renderer, vendor, graphics limits and hash exposed by your current browser. Hidden values are reported as hidden rather than guessed.
Your WebGL and GPU result
Computed for this visitRunning the test locally in your browser…
How this signal works
WebGL lets websites render hardware-accelerated graphics. To do that, the browser exposes capabilities such as maximum texture size, supported extensions and shader precision. Some browsers also reveal an unmasked GPU vendor and renderer, although privacy protections increasingly replace them with a generic value.
Combining these properties produces a fairly stable description of a graphics stack. It can help distinguish broad device configurations, but one result can still be shared by many computers sold with the same GPU, drivers and browser settings.
What this result cannot tell you
- Virtual machines, remote desktops and privacy browsers often return generic or software-rendered GPU details.
- Driver and browser updates can change extensions, limits and the resulting hash.
- WebGL describes a rendering environment; it does not expose a hardware serial number.
Use browser and network signals in your app
The verification API collects the broader fingerprint, binds it to the network request and returns the result to your backend.