Clone this wiki locally
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 email@example.com mailing list is a good place to ask questions or provide feedback on the API.
WebGPU has begun shipping to Mac/Windows/ChromeOS in Chrome 113 and Edge 113! As always, developers should develop against Chrome Canary or Edge Canary. Increased reach, other platforms, and bug fixes are ongoing.1
|👷 Behind a flag2||113||👷 Behind a flag2,3||113||113|
1 For details, look at the Dawn bug tracker and in the
Chromium bug tracker Blink>WebGPU component.
Search these before filing new bugs.
chrome://flags/#enable-unsafe-webgpu flag must be enabled on these platforms (not
enable-webgpu-developer-features). This flag is only available in Dev/Canary channels.
3 Linux experimental support also requires launching the browser with
These browser implementations are based on wgpu project in Rust.
- WGSL shaders
- overridable constants
- behavioral analysis
- uniformity analysis (present currently, but not up to spec)
- buffer mapping
- core features:
- render bundles
- error model
- error scopes
- graceful device lost handling
|present surface sharing|
|bounds checks||✔️||✔️ (not needed)||✔️ (missing vertex pulling)|
In Nightly Firefox builds, WebGPU is enabled on Windows and Linux. For macOS and Android, users need to set the
dom.webgpu.enabled pref to
Work in progress, enabled by "dom.webgpu.enabled" pref.
Work is in progress in Safari Technology Preview.
webgpu-samples for Chrome and Firefox (uses WGSL, or GLSL via SPIR-V)
WebKit/Safari Demos (uses WSL)
hello-webgpu-compute.glitch.me: simple demo with both the SPIR-V and WSL paths
- Spookyball - 3D version of "Breakout", Halloween theme.
- WebGPU Playground - a student project at Imperial College London. feedback