Platforms

WebGPU Ships in Every Major Browser Engine, Giving WebXR a GPU-Native Rendering Path

Chrome, Edge, Firefox, and Safari 26 all now ship WebGPU, closing 15 years of WebGL-era constraints and moving WebXR developers toward a shared GPU-native codebase that runs on Quest Browser, Samsung Internet, and Vision Pro.

Mainstay Communications Team · September 16, 2026 · 6 min read

In brief

Between April 2023 and September 2025, every major browser engine shipped a stable WebGPU implementation: Chrome 113, Edge 113, Firefox 141 on Windows, and Safari 26 across macOS Tahoe 26, iOS 26, iPadOS 26, and visionOS 26. Coverage is still uneven, so the W3C added WebGPU to its Interop 2026 focus areas to close the remaining cross-browser gaps, and MDN still lists the API as "Limited availability" rather than Baseline. For WebXR, the shift means native multi-view rendering and compute shaders reach Meta Quest Browser, Samsung Internet, and Safari on Vision Pro, with the shared-codebase story tightening as each engine fills in support.

Fifteen Years of WebGL, Then a New API

WebGL shipped in 2011, built on OpenGL ES 2.0, a graphics API designed before Direct3D 12, Metal, and Vulkan existed. For over a decade it was the only standards-based route to GPU acceleration in the browser. It worked, but the architecture showed its age: every draw call travels through a translation layer to reach the native GPU API, adding overhead that compounds on mobile hardware and battery-constrained XR chips.

Google first presented the concept of an explicit, modern browser graphics API in 2016. Apple formally proposed the WebGPU name and a W3C community group in February 2017. The W3C GPU for the Web Working Group coalesced contributions from Apple, Google, Intel, Microsoft, and Mozilla across roughly six years, producing a specification built to map cleanly to Vulkan, Metal, and Direct3D 12 without a translation layer.

The Browser Rollout

Google shipped WebGPU in Chrome 113 in April 2023, with Microsoft shipping it in Edge 113 the same day. Android support followed in Chrome 121 on devices running Android 12 or later with Qualcomm or ARM GPUs. Linux reached stable in Chrome 144 on Intel Gen12 and later hardware.

Mozilla reached general availability on July 15, 2025, when Firefox 141 shipped WebGPU enabled by default on Windows. The Firefox implementation rests on WGPU, a Rust library that targets Direct3D 12, Metal, and Vulkan. Mozilla's own post noted three performance areas still being addressed: unbuffered inter-process communication overhead, GPU task completion timing, and a missing importExternalTexture method for direct video decoder access. macOS Apple Silicon support followed in Firefox 145. Linux and Android remain in development.

Apple completed cross-browser coverage in September 2025 with Safari 26, shipping WebGPU on by default across macOS Tahoe 26, iOS 26, iPadOS 26, and visionOS 26. WebKit noted that WebGPU "supersedes WebGL on macOS, iOS, iPadOS, and visionOS" because it "maps better to Metal, and the underlying hardware." The feature had run in Safari Technology Preview for over a year before the stable release. WebXR itself has been enabled by default in Safari on Vision Pro since visionOS 2 in 2024, so Safari 26 pairs that existing WebXR support with a Metal-backed WebGPU pipeline on the same platform.

Not Yet Baseline, and Interop 2026 Says So

The Baseline designation marks the moment a web feature reaches the "newly available" tier: supported across all core browser engines on desktop and mobile, interoperable, and on by default. WebGPU has not crossed that line yet. As of September 2026, MDN classifies the WebGPU API as "Limited availability," noting it "does not work in some of the most widely-used browsers," and the feature does not appear on web.dev's Baseline 2026 list. Firefox still ships WebGPU disabled by default on most platforms, and desktop Safari support is recent, so full interoperability remains a work in progress.

That gap is exactly what the W3C flagged. The Interop 2026 effort, a joint project run by Apple, Google, Igalia, Microsoft, and Mozilla with additional work from Bocoup, added WebGPU as one of its focus areas after a proposal noted that despite multi-year development, "there are still interoperability gaps that can lead to site breakage and developer friction." The WebGPU Conformance Test Suite serves as the shared test baseline across implementations.

Chrome and Firefox converge on a shared C header, webgpu.h, through their respective implementations: Google's Dawn (C++, shipping in Chrome) and Mozilla's WGPU (Rust, shipping in Firefox). Both map to the same underlying GPU API surface.

What WebXR Gets

WebXR stereoscopic rendering has always needed two camera passes per frame. WebGL can approximate a single-pass approach using the OVR_multiview2 extension, but extension support is inconsistent across mobile GPU drivers, and the approach routes dispatch through JavaScript rather than the GPU itself. WebGPU exposes native multi-view rendering directly, and compute shaders allow GPU-driven culling without the JavaScript-to-GPU round trip that WebGL requires.

The W3C Immersive Web Working Group has been formalizing how the two APIs connect through the WebXR-WebGPU Binding Module, an editors' draft (dated June 15, 2026) that defines how XR composition layers render through a WebGPU pipeline. Meta shipped experimental WebGPU and WebXR depth projection support in Quest Browser version 146.0 on April 21, 2026. Subsequent Quest Browser updates extended WebGPU support to space-warp layers (version 149.1, July 27, 2026) and added experimental foveation support (version 150.1, August 28, 2026). Chrome shipped experimental support behind flags earlier in 2025.

Samsung Internet ships WebGPU on Android 12 and later devices with Qualcomm or ARM GPUs, covering the Samsung Galaxy XR headset that launched in October 2025 on Android XR. Samsung Internet already supports the full WebXR API set including passthrough AR and plane detection.

Safari on visionOS 26 routes both WebGPU and WebXR through the same pipeline on Apple Vision Pro. WebXR sessions on Vision Pro use a gaze-and-pinch interaction model that maps to the platform's standard input model, requiring no hand-raising or controller pairing.

Framework Adoption

Three.js moved first among major open-source libraries. Its WebGPURenderer shipped in release r171 on November 29, 2024, with the renderer auto-detecting the browser's backend: WebGPU if present, WebGL 2 as fallback. The upgrade path for an existing Three.js project is a one-line import change. Three.js pulls millions of downloads per week from npm, which makes adoption friction an industry-wide metric.

Babylon.js has run a WebGPU-capable engine path since version 5.0 in 2022. Version 8.0, released March 2025, extended full WebGPU support with both WGSL and GLSL shader paths and the most comprehensive WebXR support of any open-source 3D framework.

PlayCanvas is WebGL2-first with a maturing WebGPU path. Unity carries an experimental WebGPU backend in Unity 6, behind a flag, targeting developer preview rather than production deployment.

Global WebGPU coverage now sits near 87% of tracked browser usage per caniuse, with the remaining gap concentrated in Firefox's default-off platforms and older Safari. The r171 change matters because it drops the Three.js migration cost to a single import line, so a large share of the WebGL install base can move to WebGPU without a rewrite.

What Still Isn't Done

Firefox's WebXR implementation has been paused since Mozilla shut down Firefox Reality in 2020. WebXR sessions run on Chrome, Edge, Quest Browser, Samsung Internet, and Safari on visionOS, but Firefox remains a non-participant in the headset-browser stack. That gap sits alongside the broader WebGPU interoperability work, and it narrows the "write once, run everywhere" claim for developers targeting headset browsers specifically.

The WebXR-WebGPU Binding spec itself is still an editors' draft. Chrome's implementation is experimental and flag-gated. Meta's Quest Browser support, while shipping in production builds, carries the "experimental" label in its release notes. A ratified W3C binding spec is the outstanding piece before the single-codebase argument fully closes.

Sources

Companies mentioned

Mainstay Digital · Spatial and 3D visualization for industrial companies

Back to Newsroom