Skip to content
All fingerprint checks
Render & GPU

Every extension WebGL hands out is one it advertises

Pim· Clearcote Research 2 min readCheck id webgl-gettable-is-advertised

No extension that getExtension() returns is missing from getSupportedExtensions(). Prefixed aliases and flag-gated drafts are not asked for (severity: warn).

What a detector infers

In Chrome, getSupportedExtensions() and getExtension() read the same set: an extension the context can hand out is one it lists, and one it does not list returns null. A spoof that makes a context look like a different GPU usually does it by trimming the advertised list, because removing names is easy and adding real capability is not. But getExtension still reaches the real backend, so the hidden extensions stay one call away.

The probe asks for every name in the WebGL extension registry and counts those that come back non-null while missing from the advertised list. Measured on stock Chrome on Windows (Direct3D 11) and on Linux (SwiftShader): none. A list-filtering spoof written for the test left three extensions gettable but unlisted — the failing side is simulated rather than a captured tool. Vendor-prefixed aliases and draft extensions gated behind flags are not asked for.

This is the mirror of webgl-extensions-vs-driver: that row fails an advertised extension the driver cannot back (a padded list), this one fails a working extension the list hides (a trimmed one).

How to resolve it

Advertise exactly what the context can do. Trimming getSupportedExtensions() to imitate another GPU leaves getExtension() answering for the real one; present a GPU whose own driver has the extension set being shown.

What is WebGL fingerprinting?

Nearby checks in Render & GPU

See all 64 checks in Render & GPU
Who builds this test

Clearcote is a browser built for fingerprint coherence

It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.

This audit takes no position on how Clearcote scores on Render & GPU checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.

See the other checks in Render & GPU — the family webgl-gettable-is-advertised belongs to.