What is new
MDN calls WebGPU the successor to WebGL: better compatibility with modern GPUs, support for general-purpose GPU computation (GPGPU), faster operations and access to more advanced features [1]. No further features are planned for OpenGL and therefore WebGL [1].
- Shader language: WebGPU shaders are written in WGSL, the WebGPU Shading Language [1][3].
- Computation: besides drawing, compute work is first-class, for particles, simulation or generating geometry on the GPU [1].
- Security: the API is only available in secure contexts (HTTPS) [1].
State of support
The specification is published by the W3C as a Candidate Recommendation Draft [2]. Apple brings WebGPU to Safari 26 on macOS, iOS, iPadOS and visionOS [4]. As of November 2026 MDN does not yet list WebGPU as "Baseline", because it is missing from some widely used browsers [1]. Every application should therefore check whether WebGPU is available.
What it means for configurators
three.js offers a WebGPU renderer that uses WebGPU when the browser supports it and otherwise falls back to WebGL 2 [5]. That allows a gradual move. For a typical product configurator with one model, materials and variants, WebGL is usually sufficient today. WebGPU pays off more with very many objects, demanding effects or computation on the GPU.
A sensible order for most manufacturers: first a clean model and fast loading, then the question of the graphics interface.
Our example configurators currently use WebGL. The pillar page 3D configurator shows how the technology choice fits into a project.