WebGPU: Browser Support, Features, Limitations

What is WebGPU?

WebGPU is a JavaScript API from the W3C GPU for the Web Working Group that gives web pages low-level access to the system graphics card through Vulkan, Metal, or Direct3D 12. The entry point is navigator.gpu. It handles rendering, compute shaders, and machine-learning workloads on the same page.

Which browsers does WebGPU support?

WebGPU now ships by default in every major browser engine. The exact version, operating system, and GPU still vary, especially on Linux and on older Apple devices.

What are the key features of WebGPU?

WebGPU is built for modern GPU programming with first-class support for compute, low CPU overhead, and a single shading language across platforms.

• Cross-platform GPU access: WebGPU runs on top of Vulkan, Metal, and Direct3D 12, so the same JavaScript and shader code reaches every supported desktop and mobile GPU.
• WGSL shading language: WebGPU Shading Language is a Rust-style shading language that compiles to SPIR-V, MSL, or HLSL inside the browser, so authors write shaders once.
• First-class compute shaders: WebGPU exposes compute pipelines alongside render pipelines, which makes machine-learning inference, image processing, and physics simulations practical in the browser.
• Lower CPU overhead than WebGL: Command encoders and bind groups batch GPU work, cutting per-draw-call CPU cost and freeing the main thread for application logic.
• GPGPU machine learning: ONNX Runtime Web, transformers.js, and TensorFlow.js use WebGPU as a fast inference backend for in-browser AI workloads.
• Multi-pass frames: One frame can mix render passes, compute passes, and copy operations with explicit synchronization, which simplifies modern engine designs.
• Secure context only: WebGPU is gated behind HTTPS and a secure origin, which keeps GPU access aligned with other powerful web APIs.

How do you check if a browser supports WebGPU?

Feature detection takes two minutes inside any browser, with no SDK or build step. Open the DevTools console on the page you are testing and run the snippet below.

• Open DevTools console: Press F12 or right-click and choose Inspect, then switch to the Console tab.
• Probe navigator.gpu: Type navigator.gpu and press Enter. A truthy GPU object means the browser exposes WebGPU; undefined means no support.
• Request a GPU adapter: Run await navigator.gpu.requestAdapter(). A returned adapter confirms a working GPU backend; null means the API is exposed but the GPU is blocked.
• Read the adapter info: Inspect adapter.info to see the vendor, architecture, and driver. This tells you which underlying GPU is in use.
• Wrap it in feature detection: Paste the snippet below into the console, or ship it inside your page behind a feature flag.

async function checkWebGPU() {
    if (!navigator.gpu) {
        console.log("WebGPU is not exposed in this browser.");
        return false;
    }
    const adapter = await navigator.gpu.requestAdapter();
    if (!adapter) {
        console.log("WebGPU is exposed, but no GPU adapter was returned.");
        return false;
    }
    const device = await adapter.requestDevice();
    console.log("WebGPU is ready. Adapter info:", adapter.info ?? "info unavailable");
    return device;
}

checkWebGPU();

If the console reports no adapter, check chrome://gpu, the GPU vendor, and the operating system; on Linux Chrome and pre-26 Safari, the API is gated by a flag.

What are the known issues with WebGPU?

WebGPU now ships in every major browser, but cross-platform delivery still has rough edges around Linux, older Apple silicon, and mobile GPUs.

• Linux is flag-gated in Chrome and Edge: Chromium treats Linux WebGPU as experimental and keeps it behind chrome://flags/#enable-unsafe-webgpu, so Linux users have to opt in.
• Firefox lags on Linux, Android, and Intel Macs: Firefox 141 ships on Windows and Firefox 145 adds Apple silicon Macs, but Linux, Android, and Intel-based Macs still wait.
• Safari needs macOS Tahoe 26 or iOS 26: Older macOS, iOS, iPadOS, and visionOS releases install Safari but ship WebGPU off by default, so anyone on a previous OS gets no GPU at all.
• Chrome on Android needs a modern GPU: Chrome 121 enables WebGPU on Android 12 and later, but only for Qualcomm and ARM GPUs; older Android devices fall back to no support.
• WGSL ecosystem is younger than GLSL: GLSL has 20-plus years of tooling, samples, and tutorials. WGSL is catching up, but engine and editor support is still uneven.
• GPU driver bugs surface unevenly: Buggy drivers crash WebGPU at the adapter step. Chromium maintains a blocklist that disables WebGPU on known-bad driver and GPU pairs.
• Limited WebView reach: Android WebView and iOS WKWebView do not ship WebGPU on by default, so hybrid apps still need a fallback to WebGL or native code.

In my experience, the trickiest production failure is shipping a WebGPU page to a mixed Apple fleet. macOS Tahoe 26 turns WebGPU on across Apple silicon, but Intel Macs and any device on macOS Sonoma or earlier silently miss it. Always feature-detect navigator.gpu and ship a WebGL 2 fallback inside the same render path.

Citations

All WebGPU version numbers and platform notes in this guide come from these primary sources:

• W3C WebGPU Specification: w3.org/TR/webgpu
• W3C WGSL Specification: w3.org/TR/WGSL
• MDN Web Docs - WebGPU API: developer.mozilla.org/en-US/docs/Web/API/WebGPU_API
• Wikipedia - WebGPU: en.wikipedia.org/wiki/WebGPU
• Chrome for Developers - Overview of WebGPU: developer.chrome.com/docs/web-platform/webgpu/overview
• web.dev - WebGPU is now supported in major browsers: web.dev/blog/webgpu-supported-major-browsers
• WebKit Blog - WebGPU in Safari Technology Preview: webkit.org/blog/17175/webgpu-now-available-for-testing-in-safari-technology-preview
• GPU for the Web Working Group - Implementation Status: github.com/gpuweb/gpuweb/wiki/Implementation-Status
• W3C - GPU for the Web Community Group: w3.org/community/gpu