WebGL parameters and extensions
Reads the GPU vendor and model string, hardware limits and the list of supported WebGL extensions.
In one line
Can see your graphics card model, limits and which 3D features it supports
Reads the GPU vendor and model string, hardware limits and the list of supported WebGL extensions.
Exposes the exact GPU model and driver family (for example 'ANGLE (Apple, M2)'), which is a strong device class signal and reveals gaming, laptop or phone hardware.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Get the graphics chip name, for example Apple M2
- Get its hardware limits and feature list
- Tell if you use a phone, laptop or gaming PC
It cannot
- Ask permission first
- See your files
- Show you anything on screen
- Get the real chip name in browsers that mask it
How it differs between platforms: Safari and some Android browsers hide the chip name more than Chrome and Edge on desktop.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 9 | 2011-02-03 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 4 | 2011-03-22 | None |
| Safari | Partial | 5.1 | 2011-07-20 | Debug renderer returns generic 'Apple GPU' on Apple silicon since about Safari 15 |
| Safari on iPhone | Supported | 8 | 2014-09-17 | None |
| Chrome on Android | Supported | 25 | 2013-02-27 | None |
| Samsung Internet | Supported | 1.5 | 2013-09-25 | None |
How a site asks for it
| API | gl.getParameter(); getSupportedExtensions(); WEBGL_debug_renderer_info; getContextAttributes() |
| Browser compat keys | api.WebGLRenderingContext.getParameterapi.WEBGL_debug_renderer_info |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Create a WebGL context on a hidden canvas
- Call getParameter on 60 or more constants
- Enumerate extensions
- Optionally read UNMASKED_VENDOR_WEBGL and UNMASKED_RENDERER_WEBGL
Data you get
What comes back: About 70 numeric limits plus 30 to 40 extension names
Shape: object
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
MAX_TEXTURE_SIZE | integer | px | 4096 to 32768 | exact |
MAX_VERTEX_UNIFORM_VECTORS | integer | None | 128 to 4096 | exact |
UNMASKED_RENDERER_WEBGL | string | None | GPU string | full model on Chrome and Firefox desktop |
extensions | list | None | 30 to 40 names | exact |
Technical limits
- Needs GPU or SwiftShader, headless can reveal 'SwiftShader' or 'llvmpipe'
- Brave and Tor return generic values
- Cannot read VRAM size
The story
What it is
A script reads your GPU's vendor and model string, hardware limits and the list of supported WebGL extensions.
For you
You never see it. Your device quietly answers a long list of graphics questions. The answers are nearly the same each visit, so they help a site recognize your device.
For makers
Game and 3D makers read these to pick textures and effects. Fraud teams and trackers read the same list because it separates graphics chips and driver versions.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game like those running Unity or Babylon in a tab checks supported extensions, then picks the best texture format. | Unity WebGL games, Babylon.js demos |
| creative | A 3D editor in the browser checks which features exist, then turns on or off shadows and effects. | Figma, Spline |
| maps | A web map checks for float textures so it can draw smooth terrain on newer chips. | Google Earth |
| security | A fraud tool compares the list to known real devices and spots a virtual machine. | None named |
| ads | A tracker hashes the long extension list into an ID, since few devices match exactly. | None named |
| analytics | A visitor counting tool counts how many users have older graphics chips so a site knows what to support. | None named |
| developer | A game studio checks the crash reports by graphics model to fix a driver bug. | None named |
Risks
- Reveals your hardware
- Very stable ID
What the platform says
- MDN: WebGL extensions. Describes optional graphics features a browser may offer on top of the base WebGL set.
Good uses and abuse
Legitimate uses
- Pick shader quality tiers, report crashes by GPU
Known abuse
- Device class ID, VM and bot detection, spoof checks (renderer versus user agent mismatch)
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 6 | Rough identifying entropy, when known |
History
- 2017-01, paper: Cao et al. NDSS 2017 cross-browser fingerprinting via GPU features
Related capabilities
Related
- WebGL render hash. Can draw a hidden 3D scene and use the pixels to tell your device apart
- WebGPU adapter info. Can ask which graphics maker and design your device will use for 3D work
- WebGL shader precision formats. Can check how precise your graphics chip maths is, to guess your chip family
Sources
- MDN WEBGL_debug_renderer_info
- Cao et al., Cross-Browser Fingerprinting via OS and Hardware Level Features (NDSS 2017)
- BrowserLeaks WebGL
How well checked: Based on official documentation.