These samples use WebGPU with Emscripten pthreads (SharedArrayBuffer).
Both a WebGPU-capable browser and cross-origin isolation are required.
| Browser | Desktop | Android | iOS / iPadOS | Notes |
|---|---|---|---|---|
| Chrome / Chromium | ✓ Supported | ✓ Supported | ✗ Not supported | WebGPU enabled by default since Chrome 113 (May 2023). |
| Microsoft Edge | ✓ Supported | ✓ Supported | ✗ Not supported | WebGPU enabled by default since Edge 113. |
| Safari | ✓ Supported | — | ✓ Supported | WebGPU enabled by default since Safari 18 (macOS Sequoia / iOS 18, Sep 2024). |
| Firefox | ⚑ Behind flag | ✗ Not supported | ✗ Not supported | Behind dom.webgpu.enabled flag. Not recommended for production use yet. |
| Samsung Internet | — | ◑ Partial | — | WebGPU support in progress; availability depends on the Chromium base version. |
The samples use Emscripten pthreads, which requires
SharedArrayBuffer. This API is only available when the
page is cross-origin isolated. This site handles that
automatically via a service worker — no action needed on supported browsers.
WebGPU is enabled by default in Chrome 113+ and Edge 113+. No configuration needed.
chrome://gpu and verify that WebGPU shows Enabled.WebGPU shipped in Safari 18 (macOS Sequoia 15, iOS 18, September 2024).
WebGPU is available on Chrome for Android (version 121+) on Vulkan-capable devices.
chrome://gpu — your device may not support Vulkan.WebGPU is implemented but gated behind an about:config flag. Expect rough edges.
about:config and accept the warning.dom.webgpu.enabled and set it to true.gfx.webrender.all if samples fail.If a sample crashes, renders incorrectly, or fails to launch on a supported browser, please file a bug with your browser version, OS, and GPU.
Report a WebGPU sample bug ↗