WebGPU Troubleshooting

What to do when Moda says WebGPU is unavailable, with browser-specific steps and source links.

Moda uses WebGPU for canvas rendering. If Moda says WebGPU is unavailable, the problem is usually not your account. It is usually one of these:

Your browser can see navigator.gpu, but cannot get a working GPU adapter on this computer
Graphics acceleration is turned off in the browser
The GPU is blocklisted by the browser
The machine is using remote desktop, a VM, or an older graphics setup that does not expose WebGPU reliably

Start here

Before trying browser-specific steps:

Fully close the browser and open it again
Make sure your browser is updated
If you are on a work laptop, VM, or remote desktop session, try a normal local desktop session instead

Chrome

Chrome should support WebGPU by default on supported desktop systems.

If Moda says WebGPU is unavailable in Chrome

Open chrome://settings/system
Make sure Use graphics acceleration when available is turned on
Click Relaunch
Open chrome://gpu
Find the line labeled WebGPU

If chrome://gpu says WebGPU: Hardware accelerated, reload Moda.

If chrome://gpu says WebGPU is disabled or blocklisted:

Open chrome://flags/#enable-unsafe-webgpu
Set it to Enabled
Open chrome://flags/#ignore-gpu-blocklist
Set it to Enabled
Relaunch Chrome

On Linux, Chrome's official troubleshooting guide also says you may need:

Open chrome://flags/#enable-vulkan
Set it to Enabled
Relaunch Chrome

Do not turn on lots of unrelated experimental flags. Those are usually not needed.

Edge

Edge follows the Chromium WebGPU stack closely, so the Chrome-style troubleshooting steps are usually the right place to start.

If Moda says WebGPU is unavailable in Edge

Open edge://settings/system
Make sure Use graphics acceleration when available is turned on
Click Restart
Open edge://gpu
Find the line labeled WebGPU

If WebGPU is disabled or blocklisted:

Open edge://flags/#enable-unsafe-webgpu
Set it to Enabled
Open edge://flags/#ignore-gpu-blocklist
Set it to Enabled
Restart Edge

On Linux, also try:

Open edge://flags/#enable-vulkan
Set it to Enabled
Restart Edge

Safari on macOS

Safari 26 and later ship WebGPU. Older Safari versions may still require enabling a feature flag.

If WebGPU is unavailable in Safari

Update macOS and Safari if updates are available
Open Safari -> Settings -> Advanced
Turn on Show features for web developers
Open Safari -> Settings -> Feature Flags
If WebGPU appears there, turn it on
Fully quit and reopen Safari

Safari, Chrome, or Edge on iPhone and iPad

On iPhone and iPad, browser behavior is more complicated because Chrome and Edge do not use the same browser engine they use on desktop.

If WebGPU is unavailable:

Open the Settings app
Go to Apps -> Safari -> Advanced -> Feature Flags
On some iOS versions, Safari may appear directly in Settings instead of under Apps
If WebGPU appears there, turn it on
Fully quit and reopen the browser

If your browser or iOS version still does not expose WebGPU, try Moda on a desktop browser instead.

Firefox

Firefox support is less predictable across devices, OS versions, and GPU drivers.

Best-effort Firefox steps

Open about:config
Accept the warning if prompted
Search for dom.webgpu.enabled
Set it to true
Restart Firefox

If WebGPU is still unavailable:

Open about:config
Search for gfx.webgpu.ignore-blocklist
Set it to true
Restart Firefox

If it still does not work

Try these next:

Update your graphics driver, especially on Windows or Linux
Try a different supported desktop browser
Try the same browser outside remote desktop or virtualization
If this is a locked-down work machine, browser or GPU policy may be preventing WebGPU

Moda checks more than "are you using Chrome?" The browser also has to provide a working WebGPU adapter on your current machine. That is why WebGPU can work on one computer and fail on another, even in the same browser.

Sources

These steps are based on browser vendor documentation where available:

For Firefox, Mozilla does not currently provide an equivalent end-user troubleshooting page that matches Chrome's level of detail, so the Firefox section above is best-effort guidance.