WebGPU, the browser graphics API designed to replace WebGL, has now reached baseline status across every major browser — Chrome, Edge, Safari 26, and Firefox on supported platforms. That milestone, years in the making, reshapes what developers can assume about users' browsers when they reach for a 3D graphics library.
Three.js didn't wait for baseline. The library switched its default renderer to WebGPU in r163, and r186 (released September 8, 2026) refined that implementation with SunLight, cascaded shadow maps, and extended material support. On devices without WebGPU, Three.js falls back to WebGL 2 automatically. You don't have to opt in; you don't have to feature-detect. The official WebGPU renderer docs cover the transition path.
Why does WebGPU matter over WebGL? The short version: WebGL is built on top of OpenGL, a 1992-era API with decades of accumulated workarounds. WebGPU is built on Metal (Apple), Vulkan (Linux/Android), and D3D12 (Windows) — and exposes compute shaders, explicit memory management, and pipeline state that maps directly to how modern GPUs actually work. The performance ceiling is higher and the CPU overhead is lower.
The practical difference shows up in scenes that would have been too expensive for the browser: dense particle systems, real-time global illumination, large voxel worlds, physics simulations running on the GPU. Work that required a native app or a severely compromised port is now deliverable in a browser tab.
For most Three.js projects, the migration cost is low. Swap WebGLRenderer for WebGPURenderer and let the library handle the fallback. Most materials and scene graph code carries over unchanged. The community is already moving — the Three.js forum is seeing regular WebGPU demos: grass rendering, city simulations, large-scale browser games that would have been off-limits six months ago.
The r187 development branch adds WebGPU Compatibility Mode, which extends support to older hardware that can't run a full WebGPU stack. The window where "WebGPU is the new thing" is closing. It's becoming just the thing — and Three.js is where most web developers will land when they get there.