Turning on WebGPU
Local Translate AI runs its translation model on your graphics card through WebGPU. If your browser cannot reach the GPU, the app will say so — and this page is how you fix it.
Checking this browser…
The short version, in order of how often it is the answer:
- Update your graphics driver from the card maker — not from Windows Update.
- Turn WebGPU on in your browser (one setting, see your browser below).
- Check
chrome://gpuand look for “Hardware accelerated” on the WebGPU line.
By browser
Chrome and Edge
On by default on Windows, macOS and ChromeOS since Chrome 113, on Android 12+ with
Qualcomm or ARM graphics since 121, and on Linux it is still rolling out (see the Linux
section). To see where you stand, open chrome://gpu (or
edge://gpu) and look at the WebGPU line:
“Hardware accelerated” means it works.
If it says disabled, or mentions a blocklist:
-
Open
chrome://flags/#enable-unsafe-webgpu, set it to Enabled, and restart the browser. -
Still blocked? Also enable
chrome://flags/#ignore-gpu-blocklist. Chrome keeps a list of driver versions it does not trust, and capable cards end up on it.
The flag is called “unsafe” because it skips extra validation of GPU commands, not because it is dangerous. It is the normal switch for hardware Google has not certified — though on a managed work machine the setting may be locked by policy.
Firefox
Firefox has WebGPU on by default on Windows (since 141) and on Apple-silicon Macs (since 145). It is off by default on Linux, on Intel-based Macs, and on Android.
- Type
about:configin the address bar and accept the warning. - Search for
dom.webgpu.enabledand set it to true. - Restart Firefox.
If that is not enough, try setting gfx.webgpu.force-enabled to
true as well. Firefox Nightly has all of this on already.
On platforms where Mozilla ships it switched off, it is also less tested — on an Intel Mac in particular, Chrome, Edge or Safari are the more reliable choices. If Firefox becomes unstable after forcing it on, turn the pref back off.
Safari
Safari 26 on macOS 26 has WebGPU on by default — nothing to do. On older macOS versions, including with Safari 26 installed, it stays off unless you enable it:
- Open Settings → Advanced and tick “Show features for web developers”.
- In the menu bar, go to Develop → Feature Flags.
- Find WebGPU, tick it, and reload the page.
Safari 17 and 18 need the same Feature Flags toggle. If “Develop” does not appear, the setting in step 1 was not applied. If your Mac runs an OS older than macOS 26 and you would rather not fiddle with flags, use Chrome or Edge instead.
By system
Windows
WebGPU is on by default in Chrome, Edge and Firefox on Windows. When it is missing, it is almost always one of these four things:
-
An out-of-date or generic graphics driver. This is the usual culprit.
Open
chrome://gpuand look at the “Graphics Feature Status”; if you see Microsoft Basic Render Driver, Windows has no real driver loaded. Install one from the card maker directly — NVIDIA App, AMD Software: Adrenalin Edition, or the Intel Driver & Support Assistant. Windows Update often offers an old, generic driver instead of the real one. - You are on Remote Desktop or a virtual machine. A remote session only exposes a basic display adapter, so there is no GPU to use — WebGPU disappears or falls back to slow software rendering. It works normally when you run it on the machine itself.
- A laptop with two GPUs. The browser may be running on the integrated chip. Go to Settings → System → Display → Graphics, add or find your browser, and set it to High performance. The same can be forced in the NVIDIA Control Panel under “Manage 3D settings → Program Settings”.
- Chrome’s blocklist of a driver version. Fixable with the flags in the Chrome section above.
Recent Chrome versions stop quietly falling back to software rendering for unsupported
hardware, so a card that is too old now shows up as “unavailable” rather than “slow”. If
chrome://gpu lists your card but WebGPU is still refused, it is almost
certainly the blocklist — use the flag.
macOS
Apple-silicon Macs (M1 and later): everything works out of the box.
- Chrome and Edge — on since version 113.
- Safari — on by default on macOS 26.
- Firefox — on by default since version 145.
Intel Macs: it depends on the browser.
- Chrome and Edge work — they have supported Intel Macs since 113.
- Safari works on macOS 26, or through Feature Flags on older macOS.
-
Firefox does not. Mozilla has only shipped WebGPU for Apple-silicon
Macs; on Intel it stays behind the
dom.webgpu.enabledpref and is not finished. If that is your setup, use Chrome, Edge or Safari.
Whatever the Mac, keep the browser up to date — the WebGPU implementations have been changing quickly, and an older Chrome or Firefox can predate the version that works.
Linux
WebGPU needs a working Vulkan driver, and on Linux that is where things usually go wrong. For NVIDIA cards the proprietary driver is required — the open-source Nouveau driver cannot do it, and no browser flag will change that.
Confirm the driver can see the card:
nvidia-smi
If that prints a table, you are fine. If it prints an error, fix the driver before going further. Two common ones:
- “Failed to initialize NVML: Driver/library version mismatch” — the driver was updated underneath a running system. Reboot; that is all it usually needs.
- No driver at all — install the proprietary one from your distribution (Ubuntu: Additional Drivers), then reboot.
Browser support is still arriving platform by platform. Chrome enabled it by default for
Intel Gen12+ in version 144 and, on Wayland, for NVIDIA with driver 535 and newer in 147.
On X11 with NVIDIA you generally need the flags above, or launching the browser with
--enable-unsafe-webgpu --use-angle=vulkan --enable-features=Vulkan. Firefox
needs the about:config pref from its section.
Still not working?
-
WebGPU needs a secure page:
https://orlocalhost. It is never available over plainhttp://on a real domain. - A software renderer (SwiftShader, llvmpipe) can look like “available” while being far too slow to translate with. The check above warns you when it spots one.
- After changing a setting, close every window of that browser and open it again.
- Very new hardware can land on Chrome’s blocklist before the driver is certified — the flags in the Chrome section are the workaround, and it tends to be sorted out in a later browser release.
Browser settings move around between versions. If a flag has been renamed, the browser’s own documentation is the tiebreaker — the shape of the fix is almost always “update the driver, then enable the WebGPU flag”.