Layovelle

WebGPU Troubleshooting

Documentation

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

Start here

Before trying browser-specific steps:
  1. Fully close the browser and open it again
  2. Make sure your browser is updated
  3. 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 Layovelle says WebGPU is unavailable in Chrome

  1. Open chrome://settings/system
  2. Make sure Use graphics acceleration when available is turned on
  3. Click Relaunch
  4. Open chrome://gpu
  5. Find the line labeled WebGPU
If chrome://gpu says WebGPU: Hardware accelerated, reload Layovelle. If chrome://gpu says WebGPU is disabled or blocklisted:
  1. Open chrome://flags/#enable-unsafe-webgpu
  2. Set it to Enabled
  3. Open chrome://flags/#ignore-gpu-blocklist
  4. Set it to Enabled
  5. Relaunch Chrome

On Linux, also check Vulkan

On Linux, Chrome runs WebGPU through Vulkan. WebGPU will not work if Vulkan is off — even when chrome://gpu shows “WebGPU: Hardware accelerated”. So on Linux, check the Vulkan line in chrome://gpu too, not just the WebGPU line. If the Vulkan line is not enabled:
  1. Open chrome://flags/#enable-vulkan
  2. Set it to Enabled
  3. Relaunch Chrome
  4. Reopen chrome://gpu and confirm the Vulkan line is now enabled
If Vulkan will not turn on, your graphics driver is usually the cause — update it (for example Mesa on Fedora/Ubuntu) and try again. 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 Layovelle says WebGPU is unavailable in Edge

  1. Open edge://settings/system
  2. Make sure Use graphics acceleration when available is turned on
  3. Click Restart
  4. Open edge://gpu
  5. Find the line labeled WebGPU
If WebGPU is disabled or blocklisted:
  1. Open edge://flags/#enable-unsafe-webgpu
  2. Set it to Enabled
  3. Open edge://flags/#ignore-gpu-blocklist
  4. Set it to Enabled
  5. Restart Edge
On Linux, Edge runs WebGPU through Vulkan, so check the Vulkan line in edge://gpu too — WebGPU will not work if Vulkan is off, even when the WebGPU line shows “Hardware accelerated”. If Vulkan is not enabled:
  1. Open edge://flags/#enable-vulkan
  2. Set it to Enabled
  3. Restart Edge
  4. Reopen edge://gpu and confirm the Vulkan line is now enabled

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

  1. Update macOS and Safari if updates are available
  2. Open Safari -> Settings -> Advanced
  3. Turn on Show features for web developers
  4. Open Safari -> Settings -> Feature Flags
  5. If WebGPU appears there, turn it on
  6. 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:
  1. Open the Settings app
  2. Go to Apps -> Safari -> Advanced -> Feature Flags
  3. On some iOS versions, Safari may appear directly in Settings instead of under Apps
  4. If WebGPU appears there, turn it on
  5. Fully quit and reopen the browser
If your browser or iOS version still does not expose WebGPU, try Layovelle on a desktop browser instead.

Firefox

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

Best-effort Firefox steps

  1. Open about:config
  2. Accept the warning if prompted
  3. Search for dom.webgpu.enabled
  4. Set it to true
  5. Restart Firefox
If WebGPU is still unavailable:
  1. Open about:config
  2. Search for gfx.webgpu.ignore-blocklist
  3. Set it to true
  4. Restart Firefox

If it still does not work

Try these next:

Why this happens

Layovelle 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.