Skip to main content
Question

Figma Shaders Require WebGPU Support on HP Chromebook

  • August 12, 2026
  • 3 replies
  • 10 views
AncaElly

Hello, Figma Support. 

 

I'm having an issue with Figma shaders beta. I try to use the pattern reflection shader, I get the error "Shaders require WebGPU support. Click to learn more." I'm using an HP Chromebook with Chrome OS version 150.0.7871.23.

 

Chrome reports WebGPU as hardware-accelerated, but the error persists in new files. So my hardware may not be compatible. Could you please confirm whether shaders are supported on this device or if there's a workaround?

P.S. On Chrome OS, it is impossible to install custom fonts at the operating system level, which prevents us from using any external fonts in Figma that aren't already included by default. Since local OS installation isn't an option on this platform, are there any plans on your roadmap to bring a workaround, direct font manager, or native support for Chrome OS (and Linux) users in the future?
 

3 replies

Jaycee Lewis
Figmate

Hey hey ​@AncaElly 🤩 Thanks for your post — the version info helps.

Shaders need WebGPU running in full (non-compatibility) mode. chrome://gpu will still show "WebGPU: Hardware accelerated" when Chrome has fallen back to compatibility mode. Open chrome://gpu and search the page for "compatibility" — if you see WebGPU listed in compatibility mode, that's your answer, and it's a GPU/driver limitation on the device rather than something to fix in Figma. Would you mind pasting the GPU line from that page? 

On fonts: correct, ChromeOS and Linux can't install fonts at the OS level, so the Figma font installer doesn't run there. You have Google Fonts and SF Pro/SF Compact by default. Two things that do work today:

  • If you're on an Organization or Enterprise plan, an admin can upload font files directly to your workspace and everyone gets them in the browser, Chromebook included
  • Otherwise, anyone on Windows or macOS in your file can load the font locally and it'll render for you

Talk soon! — Jaycee

 

Chiorcau Anca Elena

Hi, Jaycee. Thanks

 for the suggestion. I checked chrome://gpu as you recommended.

 

WebGPU is reported as “Hardware accelerated,” and I searched the page for “compatibility.” I couldn’t find any indication that WebGPU is running in compatibility mode. The only match I found was related to an EGL/ANGLE WebGL compatibility extension.

 

I also found this under “Problems Detected”:

 

“Disable WebGPU on VK via GL interop”

and under disabled features:

“webgpu_on_vk_via_gl_interop”

 

I’ve attached screenshots of these sections. Could you please let me know whether this disabled feature could be the reason shaders aren’t working on my Chromebook, or if there is another specific GPU line from chrome://gpu that you would like me to provide?

 

Thank you!

Jaycee Lewis
Figmate

Hey there. Thanks for the screenshots. This is an issue on the Chrome-side of things and not something Figma has control over. 

The longer more technical answer is: your device is hitting webgpu_on_vk_via_gl_interop, a Chrome blocklist entry (crbug 442791440). Note Vulkan: Disabled just above it. On your Intel Chromebook, WebGPU's only route to the GPU is the Vulkan-via-GL-interop path, and Chrome has that path switched off. 

Without an official update from the Chrome team or finding an adapter here webgpureport.org there isn’t anything that Figma support can address with this Chrome-based blocker. I’ll share this as feedback with our team. Best — Jaycee

Terms & ConditionsAccessibility statement