Skip to content

What does WebGL say about your GPU?

WebGL names the graphics card and driver, reports dozens of hardware limits, and renders a shader whose low bits differ by GPU. Here it is all read back and checked against the platform this browser claims.

Not run

Nothing has been measured yet.

The test opens a WebGL context, reads the vendor and renderer strings, parameters, precision formats and extensions, renders one shader, and compares the GPU with the claimed platform.

Runs in your browser. Nothing is kept.
GPU maker
-
Context
-
Extensions
-
Render hash
-

01Reading

What it reveals

The GPU is hard to fake halfway.

Changing the renderer string is easy. Making every other WebGL value agree with it is not.
  • 01

    Renderer, limits and render hash describe one card

    The renderer names the GPU, the parameters list its limits and the shader hash shows how it rounds. A spoofed name over the real limits, or a real name over a software renderer, is a contradiction a site can test in a few milliseconds.
  • 02

    The backend gives away the operating system

    ANGLE draws through Direct3D on Windows, Metal on Apple platforms and OpenGL or Vulkan elsewhere, and the backend is in the renderer string. A User-Agent that claims another operating system is contradicted before any other check runs.

VeilBrowser keeps each profile's WebGL identity consistent with the platform the profile claims, so the renderer, its limits and the User-Agent describe the same machine.

Contact salesFingerprint documentation

More tools