WebGPU now ships in every major browser. Here's what still doesn't have it

Yes, you can use WebGPU in production in 2026, as long as you keep a fallback. Chrome, Edge, Firefox and Safari all ship it by default, but support still depends on the operating system and, in some cases, the GPU.

This page breaks down where it works, where it doesn't, and how to plan for the gap. The platform details come from the WebGPU implementation status page maintained by the W3C GPU for the Web group, and from the browsers' own release notes.

Where WebGPU ships by default

Safari was the last big piece. WebKit's Safari 26.0 release notes, published 15 September 2025, confirmed WebGPU on macOS, iOS, iPadOS and visionOS.

Where it's still missing or behind a flag

At the time of writing, the implementation status page lists these gaps:

• Firefox on Linux: on by default in Nightly; Mozilla expects to ship it in 2026.
• Firefox on Android: behind a flag, with work expected in 2026.
• Chrome on Windows ARM64: behind a flag.
• Chrome on Linux with other GPUs: behind a flag and command-line switches.
• Some Android GPUs: for example Samsung Xclipse, listed as in progress.

On top of that come older devices and OS versions. Safari's support starts at version 26, so an iPhone that can't update to iOS 26 won't get WebGPU. That's the long tail you plan for.

What this means for designers and front-end developers

The practical rule: treat WebGPU as an enhancement, not a requirement.

1. Check for support, don't guess from the browser name. Check navigator.gpu and whether requestAdapter() returns an adapter. A browser can expose the API and still fail to give you a GPU adapter.
2. Use tools that fall back for you. Three.js's WebGPURenderer uses WebGPU when it can and falls back to WebGL 2 when it can't. Writing shaders in TSL means one version for both.
3. Design the fallback, too. For decorative effects the right fallback is often a static image or a CSS gradient, not a second renderer. Decide what the page looks like without the GPU effect before you build it.
4. Test on a real phone. Mobile GPUs, thermal throttling and battery drain are where GPU-heavy pages go wrong.

async function hasWebGPU() {
  if (!("gpu" in navigator)) return false;
  try {
    return (await navigator.gpu.requestAdapter()) !== null;
  } catch {
    return false;
  }
}

Should you pick WebGPU or WebGL for a new project?

If you're weighing libraries, see shader libraries for the web in 2026.

Sources

• WebGPU implementation status, gpuweb wiki
• WebKit features in Safari 26.0
• Three.js WebGPURenderer docs