WebGL parameters and extensions
About 65 WebGL limits and an extension list that differ by GPU and driver.
In one line
Can measure about 65 graphics limits that point to your GPU and driver
About 65 WebGL limits and an extension list that differ by GPU and driver.
MAX_TEXTURE_SIZE (4096 to 32768), MAX_VERTEX_ATTRIBS, shader precision formats and supported extensions together fingerprint the GPU even when the renderer string is hidden.
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
- Check texture size limits, shader precision, and extension lists
- Tell GPU and driver families apart
- Use the pattern to recognize your device even when the GPU name is hidden
- Tune graphics for what your device handles
It cannot
- See your files or screen contents
- Tell your exact GPU model unless the name is shared
- Work if graphics support is off
- Be sure; browsers may round or hide values
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 | Supported | 5.1 | 2011-07-20 | None |
| 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(...), gl.getSupportedExtensions(), gl.getShaderPrecisionFormat() |
| Browser compat keys | api.WebGLRenderingContext.getSupportedExtensions |
| 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 |
|---|---|---|---|---|
MAX_TEXTURE_SIZE | integer | px | 4096 to 32768 | exact |
extensions | list | None | 20 to 40 names | Not listed |
shader precision | object | bits | rangeMin, rangeMax, precision | Not listed |
Technical limits
- Randomized (farbled) by Brave
- Firefox fingerprint protection narrows
The story
What it is
About 65 graphics limits and a list of extras that differ by graphics chip and driver.
For you
You never see it. A 3D game or map asks your graphics chip what it can do and picks settings that work. The same answers, taken together, can act as a fingerprint of your graphics hardware.
For makers
Graphics apps must know the biggest texture, the shader precision and which extras exist. Trackers read the same numbers because they differ by chip and driver. Even when the name is hidden, the limits can tell devices apart.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser 3D game reads the texture size limit and picks high or medium graphics so it does not crash. | Unity WebGL games |
| maps | A web map asks which graphics features exist to draw 3D buildings smoothly. | Google Maps, Mapbox |
| creative | A browser 3D tool checks which extensions exist before turning on advanced lighting. | Figma |
| games | A cloud gaming page uses graphics capability to tune its overlay and video drawing. | GeForce NOW |
| ar-vr | A web based virtual tour scales scene detail to what the graphics chip can handle. | None named |
| security | A fraud service uses the limit list to tell real GPUs from virtual machines and emulators. | None named |
| ads | A fingerprint vendor adds the graphics profile to a device ID that survives cookie clearing. | FingerprintJS |
Risks
- Strong fingerprint
- Works even if the GPU name is hidden
What the platform says
- MDN: WebGL API. Docs describe WebGL as the way pages draw fast 2D and 3D graphics in the browser.
Good uses and abuse
Legitimate uses
- Quality tiering
Known abuse
- Hardware fingerprint
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 | 4 | Rough identifying entropy, when known |
A real example: LinkedIn
65+ parameters. Read by the LinkedIn APFC fingerprint script (48 features, alleged by BrowserGate, partly confirmed by BleepingComputer).
Related capabilities
Related
- GPU via WebGL unmasked renderer. Can see your graphics card and driver name through WebGL
Sources
How well checked: Based on official documentation.