WebGPU Not Working? A Fix-It Guide

You opened a browser 3D app and got a wall instead of a viewport: "WebGPU not supported," or a blank canvas, or a warning that your GPU couldn't be reached. This is a fixable problem far more often than it looks, and the fix is usually one of four things. Here's how to find out which one, verified as of September 2026.

What does "WebGPU not supported" actually mean?

It means your browser refused to hand the page a GPU adapter. As of September 2026, that happens for four reasons: your browser is too old, hardware acceleration is switched off, your graphics driver is old or blocklisted, or your GPU vendor isn't enabled on your platform yet. Only the last one is genuinely a hardware problem.

That distinction matters, because the error text is identical in all four cases and it reads like a verdict on your computer. It usually isn't. The cheapest cause to rule out first is hardware acceleration being switched off in browser settings — a checkbox, not a graphics card.

If you want the background on what WebGPU is and why browser 3D suddenly works, we wrote a plain-English explainer for artists. This post assumes you already know and just want it running.

First, find out what your browser actually reports

Before changing anything, get the diagnosis. Two minutes, no installs.

In Chrome or Edge, open chrome://gpu (edge://gpu on Edge) and look at the Graphics Feature Status list at the top. The WebGPU row is the authoritative answer for your machine, ahead of any compatibility table including this one. You'll see one of:

• Hardware accelerated — WebGPU is working. If an app still fails, the problem is the app, not your setup.
• Software only, hardware acceleration unavailable — the browser is falling back to CPU rendering. Driver or blocklist territory, covered below.
• Disabled — usually a setting or a policy, not your hardware.

Chrome's own troubleshooting documentation treats that row as the starting point too, and further down the same page you'll find the GPU your browser actually picked — worth reading if you have both integrated and discrete graphics.

In any browser, webgpu.report probes support locally and prints your adapter's limits and features. It's the fastest cross-browser check, and it tells you what an app sees rather than what a settings page claims.

Check the secure-context rule. WebGPU is only available on https: pages and on localhost. If you're testing a site over plain http: on a local network address, navigator.gpu will be undefined no matter how good your GPU is. This trips up developers constantly and end users almost never.

Which browsers support WebGPU as of September 2026?

As of September 2026, WebGPU ships by default in Chrome and Edge 113+ on Windows, macOS and ChromeOS, in Safari 26 on macOS Tahoe, iOS 26 and iPadOS 26, and in Firefox on Windows (141+) and macOS (145+ on Apple Silicon, all Macs from 147). Linux coverage is partial and still expanding.

The per-platform picture, from the W3C GPU for the Web group's implementation status page:

Two practical takeaways. First, if you're on Chrome or Edge on Windows or macOS and WebGPU isn't working, your browser version is almost certainly not the cause — 113 shipped in May 2023. Second, if you're on Linux, your GPU vendor probably is the cause, and our Linux sculpting guide goes through that case in detail.

Safari before 26 is a special case: WebGPU existed there behind a Feature Flag in the Develop menu rather than on by default. Updating to Safari 26 on macOS Tahoe is a more reliable fix than hunting for the toggle.

Fix 1: turn hardware acceleration back on

Check this first, because it's free to check and it invalidates everything downstream: WebGPU is unavailable whenever the browser has been told not to use the GPU at all. Chrome's troubleshooting docs list it as the first thing to verify when no adapter is returned.

In Chrome, open chrome://settings/system and make sure Use graphics acceleration when available is on, then click Relaunch. Edge has the same setting at edge://settings/system. In Firefox, it's under Settings → General → Performance: uncheck "Use recommended performance settings" to reveal "Use hardware acceleration when available."

Three ways this ends up off without you doing anything:

• A troubleshooting guide for some unrelated app told you to disable it — this is stock advice for video-conferencing and screen-recording glitches.
• A GPU driver crash left the browser in a degraded state after a bad session.
• Your machine is managed, and IT turned it off centrally. More on that below.

Relaunching is mandatory, not optional. The setting doesn't take effect in the current session, which makes it easy to conclude it didn't help when it did.

Why does chrome://gpu say "software only"?

"Software only, hardware acceleration unavailable" means the browser found your GPU but declined to use it for WebGPU. As of September 2026, the two usual causes are an outdated graphics driver and Chrome's GPU blocklist, which disables acceleration for driver and hardware combinations with known crash or correctness bugs. Both are addressable.

Software rendering is a fallback, not a failure state — pages still render, they just render on the CPU. For 3D work that means the frame rate drops off a cliff, and any app doing real GPU compute becomes unusable. So it's worth fixing rather than living with.

The blocklist is a genuine safety feature, not an obstacle put there to annoy you. It exists because certain driver versions crash or render incorrectly under GPU workloads, and a crashed GPU process takes your tab with it. Overriding it is possible (below) and sometimes correct, but if you override it and things get unstable, that's the blocklist being right.

Fix 2: update your graphics driver

Old drivers are the most common cause of "software only," and driver updates are also where most blocklist entries get resolved — vendors fix the bug, the new version comes off the list.

• NVIDIA and AMD on Windows — use the vendor's own app (NVIDIA App, AMD Software) rather than Windows Update, which lags badly on GPU drivers.
• Intel integrated graphics — Intel's Driver & Support Assistant, again in preference to Windows Update. On a laptop, the OEM's driver may be older still; Intel's generic driver is usually the newer one.
• macOS — drivers ship with the OS. Updating macOS is the whole procedure.
• Linux — this is where driver version matters most and varies most by distribution. NVIDIA's proprietary driver from 2024-05 onward is the current requirement for Chrome's default-enabled path on Wayland.

Restart the browser fully after updating, then recheck chrome://gpu. A driver update that fixed nothing on paper often changes that row.

The flags worth trying, and what they cost

If the settings and driver route hasn't worked, Chrome exposes flags that override its own defaults. These are genuinely useful for evaluating whether your hardware can run WebGPU, and genuinely capable of making your browser unstable. Use them as diagnostics, and turn them back off if things get weird.

The last one deserves a note. On Windows, Chrome uses a single GPU adapter and respects the system's allocation, which on a laptop usually means the integrated chip. If you have a discrete card that the browser isn't using, that flag is the switch — though the integrated GPU is often the better call on battery.

Each flag needs a browser relaunch. Change one at a time so you know which one did the work.

What if your machine is managed by IT?

On a managed work or school laptop, hardware acceleration can be disabled centrally through Chrome's HardwareAccelerationModeEnabled policy, and no amount of clicking in settings will override it. Open chrome://policy to see what's applied to your machine. If that policy is set to disabled, the fix is a conversation with IT, not a flag.

This is worth knowing before you spend an afternoon on drivers. Managed browsers also frequently block the flags page outright, which is its own diagnostic signal — if chrome://flags won't open, you're on a locked-down profile.

It's not always a dead end. The policy is often set org-wide for reasons that have nothing to do with your use case (a fix for one bad app, inherited from an old image), and "the browser app I need for coursework requires GPU access" is a reasonable request with a specific, checkable ask attached.

What if your GPU just isn't supported yet?

If your hardware genuinely isn't on WebGPU's supported list — most commonly AMD on Linux, or an X11 NVIDIA session, as of September 2026 — no browser setting fixes that. Your options are to wait for browser support to reach your vendor, override the blocklist and accept the instability, or use a native tool.

Full disclosure: we build Re:Form, a browser sculpting app, so treat this as an interested party's advice. Re:Form handles the unsupported case by falling back to a CPU engine rather than refusing to load. Every tool still works — brushes, sculpt layers, masking, symmetry, remeshing — but stroke performance and the practical triangle ceiling both drop sharply. There's an engine badge at the bottom of the left tool rail reading GPU or CPU so you always know which one you got, and the system requirements doc has the specifics.

If the badge says CPU and you can't fix it, Blender is the honest recommendation. It's free, it's mature, it talks to your GPU through the OpenGL and Vulkan drivers your system already has, and it doesn't depend on WebGPU landing for your vendor. That's a real gap in the browser story right now, not a temporary inconvenience we're downplaying.

Once WebGPU is working

Assuming the row now reads "hardware accelerated," the payoff is that GPU-heavy apps run in a tab with nothing installed. For sculpting specifically, open Re:Form — it's in alpha at v0.7.x, it needs a free sign-in, and there's no card, no download and no watermark. The free plan is the full toolset up to roughly 12.5 million triangles with OBJ import and export; Pro at $9.99/month raises the ceiling to 50 million triangles, adds STL, GLB and FBX, and includes a commercial license.

If your hardware is on the modest side and you're wondering whether it's worth it at all, our low-end PC guide sets realistic expectations — the short version is that the entry bar is a normal computer, not a render rig. And the FAQ covers requirements in one page if you'd rather check before you click.

FAQ

How do I check if my browser supports WebGPU?

In Chrome or Edge, open chrome://gpu and read the WebGPU row in Graphics Feature Status — "Hardware accelerated" means you're set. For a cross-browser answer that works in Firefox and Safari too, load webgpu.report, which probes support locally and lists your adapter's limits. Both take under a minute and install nothing.

Does enabling the unsafe-WebGPU flag damage anything?

No, it's reversible — the flag bypasses Chrome's adapter blocklist and can be switched off again with a relaunch. What it can do is make your browser unstable, because the blocklisted driver combinations are on that list for crash and rendering bugs. Treat it as a diagnostic to find out whether your hardware works, not a permanent setting.

Why does WebGPU work in Chrome but not Firefox on my machine?

Because platform coverage differs by browser. As of September 2026, Firefox ships WebGPU by default on Windows (141+) and macOS (147+ for all Macs), but on Linux it stays behind the dom.webgpu.enabled flag in about:config. Chrome's Linux support also varies by GPU vendor. Same hardware, different rollout schedules — not a fault in your setup.