If you've noticed serious 3D tools showing up inside browser tabs lately — sculpting apps, renderers, CAD tools — there's one piece of technology behind almost all of it: WebGPU. You don't need to write a line of code to benefit from it, but it helps to know what it is, because it explains what browser tools can and can't do in 2026. This guide is for artists, not web developers. No code, no jargon without a translation.
What is WebGPU?
WebGPU is a modern browser API that lets a web page talk almost directly to your computer's graphics card, for both rendering and general computation. It is the successor to WebGL, and it is the main reason serious 3D tools — including our own sculpting app Re:Form, currently in alpha — now run inside a browser tab.
Here's the translation. Your graphics card (GPU) is the chip that draws 3D scenes and, increasingly, does heavy math of all kinds. Desktop apps like Blender or ZBrush have always been able to use it fully. Web pages, historically, could not — the browser only handed them a narrow, older pathway to the GPU called WebGL.
WebGPU replaces that pathway with a wide one. It's an interface designed in the 2020s, shaped to match how modern graphics cards actually work. When people say "the browser can finally do real 3D," WebGPU is what they mean.
Two things make it matter for artists:
- Rendering — drawing your model on screen, fast, with modern techniques.
- Compute — using the GPU for arbitrary math, not just drawing. This is the big one, and it's what WebGL never had.
WebGPU vs WebGL: what actually changed
WebGL arrived in 2011, and it was built on a design that's even older — it's essentially a web version of OpenGL ES, a graphics interface from the 2000s. It did one job: draw triangles on screen. It did that job well enough to power browser games and model viewers for a decade.
But "draw triangles" is all it did. If a tool wanted to change the model — deform a mesh, run a simulation, recalculate geometry — that work had to happen on the CPU, in the page's own code. Then the updated mesh had to be shipped over to the GPU again so it could be drawn. For a small model, fine. For a sculpt with millions of triangles, that round trip happens on every frame of every brush stroke, and it's the reason old browser 3D tools felt like wading through mud past a certain polygon count.
WebGPU changes the model:
| WebGL (2011) | WebGPU (shipping now) | |
|---|---|---|
| Based on | OpenGL ES, a 2000s-era design | Modern GPU interfaces: Vulkan, Metal, Direct3D 12 |
| What the GPU does | Draws triangles | Draws triangles and runs general computation (compute shaders) |
| Where mesh edits happen | On the CPU, then re-uploaded to the GPU | Directly on the GPU — the data never leaves the card |
| Practical ceiling | Performance degrades as models grow | Multi-million-triangle editing is workable |
The row that matters most is the third one. With compute shaders, the mesh can live on the graphics card permanently. When you drag a brush across a sculpt, the deformation is calculated on the GPU, right next to where the mesh already sits. Nothing gets shuttled back and forth. The CPU just says "brush moved here" and the card does the rest.
That's the difference between a browser tool that tops out at a toy-sized model and one that can handle production-scale meshes. It's not that browsers got faster — it's that the pipeline stopped doing wasteful work.
What this means for sculpting
Full disclosure up front: we build Re:Form, so this section is a first-person case study rather than a neutral survey. But it's a concrete example of what WebGPU actually buys you as an artist.
Re:Form is a 3D sculpting app that runs in desktop browsers on WebGPU. We built the engine around one decision that WebGPU made possible: the mesh lives on the GPU, full stop. Brushes, subdivision, remeshing, sculpt layers, masking, symmetry, undo — everything operates on GPU-resident data. The engine promise we hold ourselves to is simple: stay smooth as the polygon count climbs. Strokes at millions of triangles should feel like strokes at thousands.
Under WebGL, this architecture wasn't realistic. There was no compute pathway, so every brush stroke would have meant recalculating geometry on the CPU and pushing millions of updated vertices to the card, over and over. Under WebGPU, the stroke is a GPU operation from start to finish.
There's a privacy side effect worth knowing about, too: because the mesh lives on your GPU, your sculpts save to your own machine — browser autosave plus .clay files on your disk. Re:Form isn't streaming rendered frames from a data center — the work happens on your hardware, in your browser.
To be equally plain about where things stand: Re:Form is at v0.6.4 and it's an alpha. New brushes, engine speedups, and workflow polish land all the time, but it is not a twenty-year-old package with a twenty-year-old feature list. If you want an honest feature-by-feature look at how it stacks up against the industry standard, we wrote one: Re:Form vs ZBrush. The short version is that WebGPU closes the performance gap far more than you'd expect from a browser tool, and the remaining gaps are about feature depth, not speed.
Which browsers support WebGPU?
As of July 2026, WebGPU ships by default in Chrome and Edge (since version 113 in 2023), in Safari 26 across macOS Tahoe, iOS, and iPadOS, and in Firefox (by default as of Firefox 147, January 2026). Re:Form, our alpha sculpting app, officially supports current Chrome, Edge, and Firefox on desktop today, plus Safari 26 on macOS Tahoe.
The fuller picture, dated July 2026:
- Chrome and Edge — shipping since version 113 (May 2023) on Windows, macOS, and ChromeOS. Android support arrived in Chrome 121 for most modern devices. Linux support is still rolling out and remains partial.
- Safari — WebGPU ships enabled by default in Safari 26, which covers macOS Tahoe 26, iOS 26, iPadOS 26, and visionOS 26. Earlier Safari versions don't have it on by default.
- Firefox — shipped on Windows in Firefox 141 (2025) and on Apple Silicon Macs shortly after; as of Firefox 147 (January 2026) WebGPU ships by default.
In other words: the "WebGPU is experimental" era is over. Every major browser has shipped it; the differences now are about which platforms each browser covers.
For Re:Form specifically, the officially supported list today is current Chrome, Edge, or Firefox on desktop, plus Safari 26 on macOS Tahoe — all work out of the box, nothing to download or install. If you're unsure whether your setup qualifies, the FAQ covers requirements, and the fastest test is honestly just opening the app.
Do you need an expensive GPU?
No. Re:Form, our browser sculpting app currently in alpha, requires a desktop browser with WebGPU and a reasonably modern graphics card — not a workstation card. The engine's job is to make the hardware you already own feel fast; the free plan runs the full toolset at up to roughly 12.5 million triangles.
This question comes up a lot because "GPU" tends to conjure four-figure workstation cards. But WebGPU isn't about raw horsepower — it's about efficiency. The reason old browser tools choked wasn't weak hardware; it was the CPU-to-GPU round trip described above. Remove the wasted work, and an ordinary laptop GPU has far more headroom than WebGL ever let it show.
That's the design philosophy behind Re:Form's engine: the target isn't "runs great on a flagship card," it's "stays smooth on the machine you already own as the polygon count climbs." A reasonably modern integrated or discrete GPU is enough to sculpt. More GPU gives you more comfortable headroom at higher triangle counts, but the entry bar is a normal computer, not a render rig.
Try it in 30 seconds
The nicest thing about a WebGPU app is that trying it costs nothing but a click. If you're on a desktop browser with WebGPU — Chrome, Edge, Firefox, or Safari 26 — open Re:Form and you're sculpting — no download, no install, no card required. It's the quickest way to feel what browser 3D sculpting on WebGPU is actually like, and a two-minute doodle will tell you more than any explainer.
FAQ
Is WebGPU safe to use?
Yes. WebGPU is a standard browser API, and it runs inside the same security sandbox as everything else on a web page — a site using WebGPU can't read your files or reach outside the browser's boundaries. In Re:Form's case, the sandbox cuts both ways: the sculpting itself happens entirely on your hardware. The mesh lives on your GPU, and your work saves to your own machine.
Does WebGPU work on phones and tablets?
The API does: as of July 2026, WebGPU is available in Chrome on modern Android devices and in Safari on iOS 26 and iPadOS 26. Re:Form, however, is desktop-only today — the app is built for desktop browsers, screens, and input, and does not run on phones or tablets. Mobile WebGPU exists; a mobile Re:Form is a separate question we haven't answered yet.
Is WebGPU as fast as a native desktop app?
Close, but not identical — and the gap matters less than you'd think. WebGPU adds some overhead versus a native app talking to Metal or Direct3D directly, and browsers impose safety checks native code skips. But for GPU-bound work like sculpting, where the mesh lives and computes on the card, architecture dominates: a well-built WebGPU engine outruns a poorly built native one. Re:Form is our proof-in-progress, alpha caveats included.