GPU via WebGL unmasked renderer
Reads the graphics card and driver name through WebGL.
In one line
Can see your graphics card and driver name through WebGL
Reads the graphics card and driver name through WebGL.
Exposes GPU model and driver (ANGLE (NVIDIA, GeForce RTX 4070 ...)). Identifies the device tier and OS. Safari reports a generic Apple GPU; Brave and Firefox spoof or trim it.
What it can and can't do
What the user does: Nothing. It happens when a page draws 3D graphics or tests for it
It can
- See your GPU make and model, like an NVIDIA GeForce
- See your driver and graphics layer
- Guess your device tier and OS
- Tune graphics settings to your GPU
It cannot
- See the exact GPU in Safari; it shows a generic Apple GPU
- See the real name in Brave or Firefox when they hide it
- See your files or screen contents
- Work if graphics support is off
How it differs between platforms: Safari shows a generic Apple GPU. Brave and Firefox hide or trim the name.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 33 | 2014-02-20 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 53 | 2017-04-19 | None |
| Safari | Supported | 9.1 | 2016-03-21 | Generic Apple GPU string since Safari 15 |
| Safari on iPhone | Supported | 9.3 | 2016-03-21 | None |
| Chrome on Android | Supported | 33 | 2014-02-26 | None |
| Samsung Internet | Supported | 2.0 | 2014-10-17 | None |
How a site asks for it
| API | gl.getParameter(UNMASKED_VENDOR_WEBGL / UNMASKED_RENDERER_WEBGL) via WEBGL_debug_renderer_info |
| Browser compat keys | api.WEBGL_debug_renderer_infoapi.WebGLRenderingContext.getParameter |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
UNMASKED_RENDERER_WEBGL | string | None | free text, about 300 known values | GPU model plus backend |
UNMASKED_VENDOR_WEBGL | string | None | Google Inc. (NVIDIA) etc. | Not listed |
VENDOR, RENDERER | string | None | masked WebKit WebGL values | Not listed |
Technical limits
- No driver version precision on Safari
- Extension can be disabled by browser policy
The story
What it is
Reads the name of your graphics card and driver through the browser's 3D drawing tool.
For you
You never see it. A game or video site reads your graphics chip name to pick settings, for example turning on high detail for a strong card. Safari shows a generic name to protect you.
For makers
Graphics apps use the name to apply known fixes for specific chips and to choose a quality level. Fraud teams spot virtual machines by names like SwiftShader. Trackers use the exact name as a fingerprint piece.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game sees an RTX card and starts on ultra graphics, while a weak integrated chip gets low settings. | None named |
| games | A cloud gaming site picks a different video decoder path for a known buggy graphics driver. | Xbox Cloud Gaming, GeForce NOW |
| security | A bot defence service flags a visit that reports SwiftShader, which is how many headless servers draw graphics. | DataDome |
| developer | A support team reads the graphics name from a bug report to match a known driver bug. | Sentry |
| ads | An advertiser treats a high end graphics chip as a sign of a gaming PC and shows hardware ads. | None named |
| creative | A browser 3D design tool turns off heavy effects on integrated graphics. | None named |
| analytics | A product team counts graphics chips to decide whether it can require newer features. | None named |
Risks
- Names your exact hardware
- Browsers like Safari and Brave hide or blur it
Good uses and abuse
Legitimate uses
- Quality settings by GPU
- Driver bug workarounds
Known abuse
- High-precision device ID
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 5 | Rough identifying entropy, when known |
A real example: LinkedIn
WebGL renderer, vendor, extensions, 65+ parameters. Read by the LinkedIn APFC fingerprint script (48 features, alleged by BrowserGate, partly confirmed by BleepingComputer).
History
- 2016-01, paper: WebGL renderer 3.4 bits, vendor 2.14 bits in AmIUnique
- 2021-09, Safari 15: Unmasked renderer returns generic Apple GPU
- 2025-11, Firefox 145: Fingerprinting protection limits graphics hardware info in Private Browsing and ETP Strict
- 2026-01, brave 1.93: Brave cuts three GPU signals by default
Related capabilities
Related
- WebGL parameters and extensions. Can measure about 65 graphics limits that point to your GPU and driver
- WebGPU adapter info. Can see your GPU maker, design family, and graphics limits through WebGPU
Sources
- fingerprintjs source: webgl
- AmIUnique: Beauty and the Beast, Laperdrix et al. 2016 (attribute entropy)
- Mozilla Security Blog 2026-11-10: harder to fingerprint
- ppc.land: Brave cuts three GPU signals in 1.93
How well checked: Based on official documentation.