Skip to main content

Hello Figma Team,

I am encountering a critical issue with the Figma Desktop application (Windows 11 ARM64).

Since today's update, the application displays the error message: "Could not initialize WebGL".

This problem is highly likely related to the GPU/driver detection in the latest version of the app.

 

My Configuration:

 

  • OS: Windows 11 ARM64

  • Device: ASUS Vivobook S15 (Snapdragon X Elite)

  • GPU: Qualcomm Adreno X1-85 GPU

  • Adreno Driver Version: 31.0.121.1 (the latest installed via Windows Update).

 

Diagnostics and Steps Already Taken:

 

  1. WebGL works perfectly when I use Figma in my browser (Chrome/Edge).

  2. The error occurs only on the Figma Desktop application.

  3. I attempted a clean reinstall of the Figma Desktop app (uninstalled, manually deleted GPUCache and Local Storage folders in %AppData% and %LocalAppData%) without success.

  4. I also tried to force the rendering via the command line with the --use-angle=gl and --ignore-gpu-blacklist flags, but the error persists.

Hypothesis:

It is highly probable that the latest version of your internal Chromium runtime has added my specific graphics driver (31.0.121.1) to a blacklist of unstable GPUs for WebGL on the ARM architecture, thereby preventing initialization.

Could you please confirm if there is a known blocking rule for this driver in the latest Desktop app update for Windows ARM, or if a fix is planned to allow this driver to use OpenGL rendering?

Thank you for your assistance.

Hi ​@Natthan, thanks for reaching out! 
 
Since this WebGL error seems to be only showing in the desktop app and running as expected when using Figma in the browser, can you please let me know:

  1. Can you see if the issue persists if you clear the desktop app cache: Clear the Figma desktop app cache? You can do this from the Help menu selecting Troubleshooting > Reset Figma and Restart
  2. Can you confirm if the same issue occurs if you try connecting to a different network (e.g. mobile hotspot)?
Terms & ConditionsCookie settingsAccessibility statement