Read directly from this browser's WebGPU adapter: your files and inputs never leave your device.
Related tools
- WebAssembly Feature CheckTest which post-MVP WebAssembly proposals, like SIMD, threads, and garbage collection, your current browser actually supports.
- WASM InspectorRead a WebAssembly module's sections, imports, exports, and post-MVP features in your browser.
- Glob Pattern TesterCheck file paths against a glob pattern and see which ones match.
- Speculation Rules BuilderBuild and validate prerender and prefetch rule sets for the Speculation Rules API.
- MCP InspectorBrowse an MCP server's tools and schemas, read its responses, and build test calls.
- JSONPath QueryRun a JSONPath expression against pasted JSON and see every match and its path.
What it does
Reads your browser's WebGPU adapter and reports what it is, what it supports, and how much of everything it allows: vendor, architecture, device description, every supported feature, the preferred canvas format, and the numeric limits (texture size, buffer size, compute workgroup dimensions, and more).
How to use it
Open this page in a browser with WebGPU. It requests a GPU adapter automatically and lists everything it reports. Switch the limits option from key limits to all limits to see every value the adapter exposes, not just the handful developers check first.
Why this one
chrome://gpu buries the same information behind an unstructured dump built for bug reports, not for reading. This page pulls the same adapter data into a labeled, copyable list, works in any WebGPU browser, and never sends what it finds anywhere: your files and inputs never leave your device.
FAQ
- What is WebGPU?
- WebGPU is a browser API for talking directly to the GPU, for both graphics rendering and general purpose compute. It replaces the older, more limited WebGL for modern GPU workloads.
- Why does my browser say not available?
- WebGPU needs a Chromium based browser (Chrome, Edge, or a recent Firefox/Safari build) with the feature enabled, plus a GPU and driver combination the browser is willing to trust. Older hardware, disabled hardware acceleration, or a browser flag can all cause this.
- What are limits for?
- Limits are the maximum sizes and counts an adapter guarantees, such as the largest texture dimension or how many bindings a shader can use per bind group. A WebGPU app checks them before allocating resources so it never requests more than the device supports.
Keyboard shortcuts: press ? anywhere on this page to see them.