What it is
WebGPU is WebGL’s successor. Its adapter object reports the vendor ("apple", "intel", "nvidia"), an architecture ("metal-3", "gen-12lp"), a description, and a long table of limits and optional features — a second, independent description of the same graphics hardware.
How websites read it
const adapter = await navigator.gpu.requestAdapter();
adapter.info // { vendor: "apple", architecture: "metal-3", ... }
adapter.limits // maxTextureDimension2D, maxBufferSize, …requestAdapter() needs no permission. The info fields are coarse by design, but the limits table is large and specific enough to fingerprint driver generations.
Why it identifies you
WebGPU adds little new entropy — it describes the same chip as WebGL — but it is a second witness. Two independent APIs naming the same GPU is what a real machine looks like.
How risk-control systems use it
The comparison is simple: the WebGPU vendor must appear in the WebGL renderer string, and the limits must be plausible for it. Tools that patched WebGL years ago and never touched WebGPU are caught by exactly this gap.
Common mistakes
Spoofing WebGL only; disabling WebGPU on a Chrome version that ships it; an "apple" adapter next to an Intel renderer string.
Mango is accepting waitlist registrations. These capabilities describe its first release; client access opens with invitations.
How Mango Browser handles it
CustomAdapter vendor and architecture are derived from the same GPU record as WebGL.
Check yours
Jump to this signal in your scan results.