Implementation Status
This page shows the current implementation status of the WebGPU API spec in browsers. It also lists some resources (samples, demos) for enthusiastic web developers. Also note the WebGPU Shading Language spec that's hosted separately.
The public-gpu@w3.org mailing list is a good place to ask questions or provide feedback on the API.
You can also join the chat on Matrix in the "Web Graphics" Matrix Community: #webgraphics:matrix.org. The general WebGPU channel is #WebGPU:matrix.org.
Implementation Status
Chromium (Chrome, Edge, etc.)
Work is in progress in Chrome Canary and Edge Canary
| Android | Chrome OS | Linux | Mac | Windows |
|---|---|---|---|---|
| 👷 Behind a flag in Dev | 👷 Behind a flag in Canary/Dev | 👷 Behind a flag in Canary/Dev |
- For details, look at the Dawn bug tracker, bugs under Chromium root issue 852089, and in the Blink>WebGPU component. Check these before filing new bugs.
- Note Chromium currently supports SPIR-V, but support will be removed in favor of WGSL, which is under development.
- As GPU sandboxing isn't fully implemented yet for the WebGPU API, it is possible to read GPU data for other processes and tabs. Avoid leaving it enabled when browsing the untrusted web.
- The
chrome://flags/#enable-unsafe-webgpuflag must be enabled.
Firefox and Servo
These browser implementations are based on wgpu project in Rust, which in turn uses gfx-rs for rendering on top of Vulkan, D3D12, Metal, and potentially on D3D11 and OpenGL ES 3.0.
| Feature | wgpu | Firefox | Servo |
|---|---|---|---|
| Initialization |  |
|
|
| WGSL shaders | |
|
|
| Error model | |
|
|
| Resources: | |||
| - Buffers | |
|
|
| - mapping | |
|
|
| - Textures | |
|
|
| - views | |
|
|
| - block formats | |
|
|
| - Samplers | |
|
|
| Binding: | |||
| - Pipeline layouts | |
|
|
| - Bind groups | |
|
|
| - Implicit layouts | |
|
|
| Rendering: | |||
| - Passes | |
|
|
| - Pipelines | |
|
|
| - Bundles | |
|
|
| Computing: | |||
| - Passes | |
|
|
| - Pipelines | |
|
|
| Presentation: | |||
| - Fallback (slow) |  |
|
|
| - Windows | |||
| - macOS | |||
| - Linux | |||
| - Android | |||
| Validation: | |||
| - Host API | |
|
|
| - Shader API | |
|
|
| - Out of bounds | |||
| - Uniformity | |
|
Firefox
Work is in progress in Nightly, enabled by the "dom.webgpu.enabled" pref. It requires WebRender, which may be enabled by "gfx.webrender.all" pref if it's not already enabled by default. It's been shown to work on Windows 7/10, macOS, Linux (with Vulkan support), and even Android (also with Vulkan).
All the issues and feature requests are tracked by the Graphics: WebGPU component in BugZilla.
Servo
Work in progress, enabled by "dom.webgpu.enabled" pref.
Safari (In Progress)
Work is in progress in Safari Technology Preview.
To enable WebGPU, first make sure the Develop menu is visible using Safari → Preferences → Advanced → Show Develop menu in menu bar. Then, in the Develop menu, make sure Experimental Features → WebGPU is checked. Avoid leaving it enabled when browsing the untrusted web.
Bugs can be viewed and filed here.
Materials
Samples
-
webgpu-samples for Chrome and Firefox (uses WGSL, or GLSL via SPIR-V)
-
wgpu-rs samples for Firefox and Chrome (uses GLSL via SPIR-V), compiled from Rust
-
WebKit/Safari Demos (uses WSL)
-
hello-webgpu-compute.glitch.me: simple demo with both the SPIR-V and WSL paths
Demos
Articles
Frameworks
-
Babylon.js (uses SPIR-V)
- WebGPU documentation
- Performance comparison demo of WebGL Forest vs WebGPU Forest (uses SPIR-V)