Skip to Content
Platform.Ontology

GPU via WebGL unmasked renderer

Reads the graphics card and driver name through WebGL.

Gets silentlyDevice detailsHardwareWeb browsersWhen the page loadsWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported332014-02-20None
EdgeSupported122015-07-29None
FirefoxSupported532017-04-19None
SafariSupported9.12016-03-21Generic Apple GPU string since Safari 15
Safari on iPhoneSupported9.32016-03-21None
Chrome on AndroidSupported332014-02-26None
Samsung InternetSupported2.02014-10-17None

How a site asks for it

APIgl.getParameter(UNMASKED_VENDOR_WEBGL / UNMASKED_RENDERER_WEBGL) via WEBGL_debug_renderer_info
Browser compat keysapi.WEBGL_debug_renderer_info
api.WebGLRenderingContext.getParameter
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
UNMASKED_RENDERER_WEBGLstringNonefree text, about 300 known valuesGPU model plus backend
UNMASKED_VENDOR_WEBGLstringNoneGoogle Inc. (NVIDIA) etc.Not listed
VENDOR, RENDERERstringNonemasked WebKit WebGL valuesNot 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

TypeExampleApps
gamesA browser game sees an RTX card and starts on ultra graphics, while a weak integrated chip gets low settings.None named
gamesA cloud gaming site picks a different video decoder path for a known buggy graphics driver.Xbox Cloud Gaming, GeForce NOW
securityA bot defence service flags a visit that reports SwiftShader, which is how many headless servers draw graphics.DataDome
developerA support team reads the graphics name from a bug report to match a known driver bug.Sentry
adsAn advertiser treats a high end graphics chip as a sign of a gaming PC and shows hardware ads.None named
creativeA browser 3D design tool turns off heavy effects on integrated graphics.None named
analyticsA 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

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits5Rough 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

Sources

How well checked: Based on official documentation.

On this page