WebGL Fingerprint Test | IPOK

doc

Analyze your browser's WebGL fingerprint. Examine GPU renderer, vendor strings, and Canvas output to identify your browser.

WebGL is the browser API that lets a page draw directly on the graphics processing unit, the hardware path behind 3D scenes, visualizations and accelerated canvas effects. That same rendering path is one of the most stable surfaces for browser fingerprinting: the GPU, its driver and the graphics stack leave consistent, hardware-bound readings that are hard to fake and unlikely to change between visits.

What WebGL actually does

Canvas 2D draws two-dimensional shapes and text through a general software and compositing path. WebGL hands the workload to the GPU, running shader programs that compute pixels in parallel. The difference matters for fingerprinting: Canvas 2D differences come mostly from fonts and rasterization, while WebGL differences come from the graphics hardware, its driver, supported extensions and precision behavior.

A page that probes WebGL does not need to display anything visible. It can create a hidden rendering context, run a fixed shader, read back the resulting pixels, and hash the output. The rest is comparison across visits and machines.

Where the fingerprint comes from

FieldWhat it reportsWhy it helps identify the system
Vendor stringGraphics chip maker reported by the contextGroups machines by hardware family; often consistent across browsers on the same device
Renderer stringGPU model and driver descriptionNarrower than the vendor; rare integrated or specialized chips stand out clearly
Extension listWhich WebGL extensions the context exposesDetermined by hardware and driver version; matches the capabilities of that graphics stack
Parameter limits and precisionTexture sizes, shader precision, buffer limits and format supportVary by implementation even when the model name looks similar
Rendered image hashHash of pixels produced by a fixed shader or drawing routineReflects the whole pipeline: chip, driver, antialiasing and color handling; repeats deterministically

Drivers matter as much as the chip. Two devices with the same GPU model can report slightly different parameter sets or pixel output after driver updates, because the driver translates between the browser's requests and the hardware. This is why a graphics hash can shift after an operating system or driver patch without the machine having changed.

How to read a WebGL result

  1. Look at vendor and renderer first. A generic or masked string means the browser is hiding the hardware name; a raw model string exposes the chip directly. Note that masking reduces detail but does not remove the other readings.
  2. Check the parameter and extension set. Even when the renderer name is hidden, supported extensions and limits still describe the graphics class.
  3. Read the image hash across two checks. A stable hash on repeat visits means a durable tracking handle; a hash that differs between sessions is less useful for recognition. Compare against a fresh session after a restart rather than two tabs in the same run.
  4. Match the reading to the rest of the profile. An unusual renderer paired with an ordinary system, or a software renderer on a capable machine, forms a conspicuous combination on its own.

Why WebGL is hard to disguise

Most client-side signals come from software settings a browser can alter. The WebGL path reaches hardware controlled by drivers below the browser, and the output has to remain correct for real graphical applications. There is no clean setting that reports a generic GPU while still rendering properly: masking the string is possible, but parameter limits, extension behavior and shader output still reflect the underlying stack.

Forcing software rendering makes the WebGL profile uniform across machines, but it also creates a clearly recognizable class of browsers that did so, and it slows graphics-heavy pages. Randomizing pixels on each visit breaks the determinism the renderer needs for correct output and can be detected statistically by repeated sampling.

Common misreads

  • "Disabling WebGL makes me safe from this fingerprint." Disabling it removes the readings, but the absence of WebGL is itself a detectable property, and many pages will report the disabled state explicitly.
  • "A software renderer can fake any GPU." It can present generic values, but its limits, precision and output differ from real hardware and form a rare, identifiable group rather than an ordinary machine.
  • "The renderer string alone identifies me." It narrows the hardware family. Millions of devices share a chip; identification comes from combining it with fonts, parameters, canvas and other signals.
  • "My hash changed, so I was fingerprinted wrong." Driver and OS updates legitimately change rendering output. A changing hash after an update is normal maintenance, not evidence of tracking.

Lowering identifiability without breaking the web

The realistic goal is to blend into a common hardware and software class, not to produce random values. Keep the browser and its graphics stack current on mainstream hardware, avoid unusual display configurations that show up in parameters, and do not stack one-off patches that make the client look engineered. A detection page showing generic vendor and renderer values, ordinary parameter limits and a stable ordinary hash means the WebGL layer contributes little distinctiveness.

Frequently asked questions

Does a VPN change my WebGL fingerprint?

No. WebGL readings are produced locally by the device's GPU and driver; the network exit does not touch the rendering pipeline.

Can two identical computers report the same WebGL hash?

Often yes when hardware, driver version and system graphics settings match. That is why the hash narrows a device family rather than selecting a specific person.

Should I turn off hardware acceleration for privacy?

Only if you accept the trade-off: software rendering is slower and its profile is itself distinctive. For most users, keeping a mainstream, up-to-date stack blends better than forcing an unusual rendering mode.