The WebAssembly project's Phase 2 wasi:webgpu proposal now has a 0.3 release candidate. It adapts WebGPU's API model for portable, sandboxed GPU compute in WASI environments across Linux, Windows, macOS, Android, and the web.
The WebAssembly project has published wasi:webgpu 0.3.0-rc.2, a release candidate for bringing WebGPU-style GPU access into the WebAssembly System Interface. The proposal is currently in Phase 2. That means it has moved beyond a sketch, but it is not a finished standard.
The useful part is the direction. WebGPU has already done a large amount of difficult API design around modern graphics and compute. wasi:webgpu takes that model and expresses it for portable, sandboxed WebAssembly components, adjusting the places where the browser specification assumes JavaScript, a document, or other web-specific machinery.
Compute first, windows later
The proposal's stated targets are Linux, Windows, macOS, Android, and the web. Its use cases include server-side graphics streaming, scientific computing, simulation, AI and machine learning, image and video processing, data visualization, and rendering. In other words, the GPU work that increasingly sits beside web graphics rather than inside a visible canvas.
There is an important boundary. Window creation and displaying to a screen are explicitly out of scope. The repository points to separate work such as wasi-gfx for that layer. wasi:webgpu is therefore easier to understand as a compute and device-access proposal first, especially for headless services and portable components that need a modern GPU interface without inheriting a whole browser runtime.
Why web GPU developers should care
This does not add a new browser feature. It does suggest that WebGPU's API shape may become useful infrastructure outside the browser as well as inside it. A component that targets a shared GPU vocabulary across WASI environments could reduce the number of custom native bindings used for inference, simulation, media processing, and server rendering.
The current repository is candid about the remaining distance. Stakeholder interest and feedback still need to be documented before Phase 3, and parts of the explainer remain scaffolding. The 0.3 release candidate mainly advances package versioning, generated imports, and CI rather than unveiling a giant new API surface.
Source: WebAssembly/wasi-webgpu and the v0.3.0-rc.2 release notes.