Dostawca i renderer WebGL

What the WebGL Vendor & Renderer tool exposes

WebGL is the browser API that lets web pages draw hardware-accelerated 3D graphics, and to do its job it has to tell the page a fair amount about your graphics stack. This tool asks WebGL those questions directly and shows you the answers, so you can see exactly which details about your GPU your browser is handing to every site you visit. It is the fastest way to find out whether your setup leaks a precise graphics-card model, whether your browser masks that information, and how much your hardware narrows you down. Reach for it when you are auditing a privacy browser, comparing devices, or trying to understand why you feel "recognised" online even after clearing everything.

How it reads your graphics hardware

The tool creates a throwaway , requests a webgl (or legacy experimental-webgl) context, and then queries the driver through standard parameters. The most revealing values come from the WEBGL_debug_renderer_info extension, which exposes the unmasked vendor and renderer strings. Typical output includes:

• Unmasked vendor and renderer — often something like ANGLE (NVIDIA, NVIDIA GeForce RTX 3060 Direct3D11 ...) on Windows, naming your actual GPU and driver path.
• Generic vendor and renderer — the deliberately vague VENDOR and RENDERER strings browsers report when the debug extension is blocked.
• GL version and GLSL (shading language) version — the OpenGL ES level and shader compiler your browser supports.
• Capability limits such as maximum texture size, which vary by hardware generation.

On most Chromium and Windows combinations you will see the "ANGLE" prefix, because Chrome translates WebGL calls to Direct3D through Google's ANGLE layer; that string alone reveals both your GPU family and the graphics backend in use. If your browser has hardened its WebGL surface, the unmasked fields will read something like "blocked by browser" and you will only get the generic strings — a sign your renderer is being protected.

Why it matters for privacy, and how to respond

Your graphics renderer is one of the highest-entropy fingerprinting signals available to a website, because a specific GPU-plus-driver-plus-OS combination is far less common than a browser version or a screen size. Combined with your other attributes, it can pin down your exact device model. A few things worth knowing:

• WebGL info is independent of your IP address, so switching networks does not change it — hardware exposure and network exposure are separate problems.
• Disabling WebGL entirely stops the leak but breaks maps, games and some video apps, and being one of the rare "no WebGL" visitors is itself a fingerprint.
• Browsers like Tor and Brave normalise or block the unmasked strings; running this tool in each is a quick way to compare their protection.

Because this signal is baked into your hardware, the practical move is to reduce how easily it can be correlated with the rest of your identity: keep a mainstream configuration and make sure your network path is consistent, for example by routing through a VPN so your visible location and your device profile do not contradict each other.

Your privacy here

This check is performed entirely by JavaScript running on this page. The WebGL context is created in your browser, the parameters are read from your own graphics driver, and the results are displayed locally. Nothing about your GPU is sent to us or to anyone else — reading your WebGL info makes no network request whatsoever.