Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
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.
Google Chrome (SPIR-V compatible - In Progress)
Work is in progress in Chrome Canary.
|└ 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)
Work is in progress to provide a secure DOM interface to wgpu-native via IPC in Gecko.
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.
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