Skip to Content
Platform.Ontology

WebGL parameters and extensions

Reads the GPU vendor and model string, hardware limits and the list of supported WebGL extensions.

Used to track youGraphics and fingerprintingWebGLWeb browsersWhen the page loads

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

BrowserStatusFirst versionReleasedNote
ChromeSupported92011-02-03None
EdgeSupported122015-07-29None
FirefoxSupported42011-03-22None
SafariPartial5.12011-07-20Debug renderer returns generic 'Apple GPU' on Apple silicon since about Safari 15
Safari on iPhoneSupported82014-09-17None
Chrome on AndroidSupported252013-02-27None
Samsung InternetSupported1.52013-09-25None

How a site asks for it

APIgl.getParameter(); getSupportedExtensions(); WEBGL_debug_renderer_info; getContextAttributes()
Browser compat keysapi.WebGLRenderingContext.getParameter
api.WEBGL_debug_renderer_info
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Create a WebGL context on a hidden canvas
  2. Call getParameter on 60 or more constants
  3. Enumerate extensions
  4. 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

FieldTypeUnitRangePrecision
MAX_TEXTURE_SIZEintegerpx4096 to 32768exact
MAX_VERTEX_UNIFORM_VECTORSintegerNone128 to 4096exact
UNMASKED_RENDERER_WEBGLstringNoneGPU stringfull model on Chrome and Firefox desktop
extensionslistNone30 to 40 namesexact

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

TypeExampleApps
gamesA 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
creativeA 3D editor in the browser checks which features exist, then turns on or off shadows and effects.Figma, Spline
mapsA web map checks for float textures so it can draw smooth terrain on newer chips.Google Earth
securityA fraud tool compares the list to known real devices and spots a virtual machine.None named
adsA tracker hashes the long extension list into an ID, since few devices match exactly.None named
analyticsA visitor counting tool counts how many users have older graphics chips so a site knows what to support.None named
developerA 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

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits6Rough identifying entropy, when known

History

  • 2017-01, paper: Cao et al. NDSS 2017 cross-browser fingerprinting via GPU features

Sources

How well checked: Based on official documentation.

On this page