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.
The email@example.com mailing list is a good place to ask questions or provide feedback on the API.
Chromium (SPIR-V compatible - In Progress)
|└ Dynamic Buffer Offset||👷||👷|
|└ Basic Compute||👷||👷|
|└ Texture Storage|
- Root Issue #852089, and blocking issues, are the authoritative reference. Search for known bugs before filing new bugs.
- As GPU sandboxing isn't implemented yet for the WebGPU API, it is possible to read GPU data for other processes. Avoid leaving it enabled when browsing the untrusted web.
chrome://flags/#enable-unsafe-webgpuflag must be enabled.
Firefox (SPIR-V compatible)
- textures & views
- pipeline layouts
- bind groups
Basically, Firefox is at the state of running the compute samples, and will soon be able to render, but unable to present anything to canvas yet.
All the issues and feature requests are tracked by the Graphics: WebGPU component in BugZilla.
Safari (WHLSL compatible - In Progress)
Work is in progress in Safari Technology Preview.
To enable WebGPU, first make sure the Develop menu is visible using
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.
Servo (SPIR-V compatible)
Work in progress to expose WebGPU initialization behind the "dom.webgpu.enabled" pref.
webgpu-samples for Chrome (uses GLSL via SPIR-V)
WebKit/Safari Demos (uses WSL)
hello-webgpu-compute.glitch.me: simple demo with both the SPIR-V and WSL paths