Skip to content

Implementation Status

Dzmitry Malyshau edited this page Oct 22, 2019 · 22 revisions

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 public-gpu@w3.org mailing list is a good place to ask questions or provide feedback on the API.

Implementation Status

Google Chrome (SPIR-V compatible - In Progress)

Work is in progress in Chrome Canary.

Feature/Platform Android Chrome OS Linux Mac Windows
Device 👷
Rendering 👷
└ Canvas 👷
└ Textures 👷
└ Multisampling 👷
└ Dynamic Buffer Offset 👷
Compute 👷
└ 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.
  • The chrome://flags/#enable-unsafe-webgpu flag must be enabled.

Edge

N/A

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 SafariPreferencesAdvancedShow Develop menu in menu bar. Then, in the Develop menu, make sure Experimental FeaturesWebGPU is checked. Avoid leaving it enabled when browsing the untrusted web.

Bugs can be viewed and filed here.

Samples

Articles

Frameworks

You can’t perform that action at this time.