0
100
200
300
400
500
600
700
800
900
1000
1100
0
100
200
300
400
500
600
700
800
900
1000
1100
Guide · Troubleshooting

How to Fix "Can't Open File: WebGL Isn't Supported" in Figma

Figma shows the WebGL error when your browser can't give it hardware graphics. Figma needs WebGL 1.0 or later to draw the canvas, so the fix is almost always to turn on graphics (hardware) acceleration in your browser, restart it, and confirm WebGL works at get.webgl.org. In Microsoft Edge, also turn off Strict tracking prevention for figma.com.

If that doesn't do it, update the browser. Figma supports Chrome 120+, Firefox 128 ESR+, Safari 17.4+ and Edge 121+, stable releases only.

Updated Sep 24, 20264 min read
On this page

This error has one of the most-viewed threads on Figma's forum: "I can't open because WebGL isn't supported" sits at around 104k views.

6 steps

Quick steps

1

Test WebGL

Open get.webgl.org or webglreport.com in the same browser. If WebGL shows as unavailable or disabled, the browser is the problem, not the Figma file.

2

Turn on graphics acceleration

In Chrome, go to Settings > System and switch on "Use graphics acceleration when available". Other browsers have a similar hardware acceleration option in their settings.

3

Relaunch the browser

The setting only applies after a full restart. Close every window of the browser, then open it again.

4

Fix Edge tracking prevention

In Edge, turn off Strict tracking prevention for figma.com, then reload the file.

5

Update the browser

Check you're on Chrome 120+, Firefox 128 ESR+, Safari 17.4+ or Edge 121+. Beta and nightly builds aren't supported.

6

Test WebGL again and reload Figma

When the test page renders, reopen the Figma file.

01

What WebGL is and why Figma needs it

WebGL is the browser feature that lets a web page use your graphics card. Figma renders the whole canvas with it, so without WebGL the file can't open at all. WebGL 1.0 is the minimum. Shader effects need WebGPU, so a browser that runs Figma fine can still fail to show shaders.

The error appears before the file loads, so the file itself is almost never the cause. The same file will open on another computer or in another browser where WebGL works. That makes the fix a browser job: get WebGL working, and every Figma file opens again.

02

Why the WebGL error happens

1. Hardware acceleration is off

This is the usual cause. Browsers fall back to software rendering when acceleration is off, and that often means no WebGL. In Chrome the switch is Settings > System > Use graphics acceleration when available. Turn it on and relaunch.

If Chrome still reports WebGL as disabled, Figma's help center lists one optional extra: open chrome://flags, find Override software rendering list, set it to Enabled and relaunch. Only do this if the normal setting didn't work, and turn it back off if Chrome becomes unstable.

2. Edge is blocking it

Microsoft Edge's Strict tracking prevention can stop Figma from loading properly. Turn it off for figma.com and reload the tab.

3. The browser is too old or not supported

Figma supports the stable releases of Chrome 120+, Firefox 128 ESR+, Safari 17.4+ and Edge 121+. On Firefox, update to 128 ESR or later and check that hardware acceleration is on in its performance settings. On Safari, update macOS if Safari itself is below 17.4.

4. An extension is interfering

Figma's troubleshooting checklist mentions Chrome extensions that block WebGL. Open Figma in a private or guest window with extensions off. If the file opens there, turn extensions back on one at a time to find the culprit.

Quick test: open the same file in a second supported browser. If it works there, the problem is the first browser's settings, not your computer or the file.

5. Graphics acceleration is locked on a work computer

On a company-managed laptop, the browser's acceleration setting may be greyed out and marked as managed by your organisation. You can't change it yourself in that case. Ask IT to allow graphics acceleration, or to let you install the Figma desktop app.

03

How to check that WebGL works

Figma's help center points to two test pages. get.webgl.org shows whether your browser supports WebGL and has it turned on. webglreport.com goes further and shows which WebGL versions are available. Run the test in the same browser, and the same profile, that you use for Figma. If the test fails, no Figma setting will fix it: the change has to happen in the browser.

04

Figma not working in Chrome: quick checklist

  • Chrome is version 120 or later, on the stable channel.
  • Settings > System > Use graphics acceleration when available is on, and Chrome has been relaunched.
  • get.webgl.org passes in the same Chrome profile.
  • The file opens in a guest window with no extensions.
  • status.figma.com shows no incident.
05

Figma not showing anything, but no WebGL error?

A grey or blank canvas with no message can have other causes: a Figma outage, a desktop app cache problem, or a file that has run out of memory. Start with Figma not working: every fix in order. If you use the desktop app, clearing the Figma cache fixes most blank white screens, and if one heavy file freezes while others open, see how to make Figma less laggy.

FAQ

Frequently asked questions

How do I enable WebGL for Figma in Chrome?

Go to Settings > System, turn on "Use graphics acceleration when available", and relaunch Chrome. Check it worked at get.webgl.org. If WebGL is still off, Figma's help center suggests enabling "Override software rendering list" in chrome://flags.

Why is Figma not working in Chrome?

The most common reason is graphics acceleration being off, which disables WebGL. Other causes are a Chrome version below 120, an extension blocking WebGL, or a Figma outage, which you can check at status.figma.com.

Why won't Figma work on Firefox?

Figma needs Firefox 128 ESR or later with WebGL available. Update Firefox, make sure hardware acceleration is on, and test WebGL at get.webgl.org.

What version of WebGL does Figma need?

WebGL 1.0 or later. Shader effects additionally need WebGPU.

Keep learning

More in Troubleshooting

All guides in Troubleshooting