With WebGPU officially Baseline since January — stable and on by default in Chrome, Edge, Firefox, and Safari 26 across desktop and iOS — the story in web graphics has shifted from “when can we use it” to “who has migrated and what did they get.” For the enormous share of web 3D built on Three.js, the answer to the first half is increasingly “almost anyone who wants to”: since r171, swapping WebGLRenderer for WebGPURenderer is designed to be a one-line change, with automatic fallback to WebGL 2 on older browsers.
Watch: Three.js: Introduction to WebGPU and TSL (YouTube)
What a real migration actually returned
The payoff numbers coming out of production migrations are not subtle. Segments.ai, a 3D segmentation platform, moved its LiDAR point-cloud labeling tool from WebGL to WebGPU and reported a 100× performance improvement — the kind of jump that comes from WebGPU’s compute shaders and modern resource management rather than incremental rendering optimization. More broadly, draw-call-heavy scenes are seeing the 2–10× improvements that were promised when WebGPU shipped across browsers, which for creative work translates directly into particle counts, instance counts, and post-processing budgets.
TSL is what makes the migration survivable
The one-line renderer swap works because of the layer underneath it: TSL (Three.js Shading Language), the JavaScript-based shader system that compiles to both WGSL for WebGPU and GLSL for WebGL. Shaders written in TSL don’t care which renderer runs them — meaning a project’s shader investment survives the migration intact, and the WebGL fallback path isn’t a separate codebase to maintain. It’s the same write-once philosophy p5.js is pursuing with p5.strands, arriving at the same conclusion from a different direction: the shader language layer, not the renderer, is where portability has to live.
And it’s showing up in physical space, not just browsers
The technology’s reach past the browser tab is real too: Waves of Connection, an interactive installation at Expo 2025 Osaka, let visitors control Hokusai’s Great Wave with their bodies — running on this same web stack, logging over 10,000 interactions across a seven-day run. For installation artists, that’s the quiet significance of the WebGPU transition: the performance ceiling of “it’s just a web page” now overlaps with what used to require a native build, while keeping the web’s deployment model — covered from the XR angle in this site’s WebXR tutorial — of shipping a URL instead of an installer.