API, adapter and device
The results distinguish an absent API, an unavailable adapter, a failed device request and an actual successful computation. Secure context requirements, browser policies and driver choices can affect each stage.
BrowserCheck · Browser environment diagnostics
WebGPU Test
Check WebGPU API, adapter and device availability, features and limits, and run a small compute shader with verified buffer readback.
An exposed navigator.gpu is only the first step. This test requests an adapter and a device, runs a one-invocation compute shader and verifies that the returned buffer contains the expected value. It releases its temporary device and buffers after the run.
Results in this browser
Running local checks…
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
What is tested and how to read it
Adapter information
Vendor, architecture, device and description are shown only when exposed. Blank identifiers remain unavailable. The fallback flag is reported when the implementation provides it; a missing flag is not treated as proof of hardware rendering.
Features and limits
Features and limits describe the adapter's available capabilities. This minimal test requests a default device with no optional features, so the listed adapter limits are not a promise that every value is enabled on that device.
Compute and readback
The shader writes the integer 42 into a storage buffer; the test copies and maps it for verification. A reported software fallback is shown as available with limitations. No benchmark score is calculated.
Test limitations
- A passing compute check is a baseline, not a guarantee that an application's optional features, resource sizes or graphics pipeline will work.
- No adapter does not necessarily mean the browser never supports WebGPU. Current settings and hardware can prevent one from being selected.
- WebGL is tested separately. Its availability can provide a fallback option for applications that implement one, but WebGL does not implement WebGPU.
Next steps
- Start with the compute result, then compare the application's required features and limits with the adapter observations.
- When the API is exposed but the test fails, record the failure stage in a support report and review browser, driver and application requirements.
Frequently asked questions
Why does my browser expose WebGPU but fail this test?
The API may exist even when no suitable adapter is selected, device creation fails, or a shader or buffer operation cannot complete. This page distinguishes those stages.
Does Available mean every WebGPU application will run?
It means only this small default-device computation passed. Applications may need additional features, larger resources or a functioning canvas render pipeline.
Does this test send GPU information to a server?
The probe runs locally. Its shareable summary contains statuses and excludes adapter identifiers, detailed limits and fingerprint values.