Prototype not loading in Google Chrome

I was able to fix it. For those who have the same problem, just go to the chrome url section and type chrome://flags and search for Choose ANGLE graphics backend and select OpenGL And it’s fixed.

I’d add one thing to the fine instructions in this thread about changing setting to OpenGL at “chrome://flags” address.

Initially, I only quit Chrome, and re-opened - to no avail. Use the “Relaunch” button that appears when you change the default value to OpenGL. Little detail - big, positive result!

Also note the granular detail regarding this Chrome setting. “Metal” value configuration is currently experimental and possibly (probably?) buggy, but config will replace the OpenGL config on Mac in the future when it is “fully released”.

So - be a bit forewarned!

This fix with the chrome://flags and OpenGL isn’t working for me. Is anyone else having this issue still?

Yes, still having the issue here as well. The solution described above didn’t work for me either.

I still have this issue. The solution above didn’t work for me either 😦

I have the same issue. The only workaround I’ve found is to load the prototype in an Incognito window, that seems to work for some reason.

When I logged into Figma, it started working again for me. I did the OpenGL thing and it didn’t work for me.

Multiple people around me are starting to experience the same thing.
Chrome as browser, incognito works fine, but not in normal mode.

@Gareth_Davies, @Patbos, if the prototype loads successfully in incognito mode, but fails to load in normal mode, then this may mean that the browser extensions that are enabled may affect the loading of the prototype. Go to the chrome://extensions page and try disabling all extensions.

I’ve been having the same problem and have disabled all my chrome extensions and it now works. I did disable all then close and reopen chrome. I tried with developer mode turn on and off in chrome extensions area. It worked with developer mode off and all extensions disabled.

In Safari and Firefox which I seldom use on my Mac it worked fine. I also works on a corporate Win machine running chrome and edge.

This is SUPER problematic… I just lost a bunch of prototype testing opportunities because my prototype wouldn’t load for testers on UserZoom - literally losing money.

Solution: clear your cookies for figma and force yourself to log back in. Don’t know why this happened, but neither the OpenGL nor browser extensions worked. Clearing all figma-related cookies did.

This is the only thing that worked for me – clearing Figma cookies. Thanks!

Same! Final design links are circulating with stakeholders. I can’t ask them to follow a series for steps to view the files. That sounds like a messy email chain they shouldn’t have to deal with.

How do you clear figma cookies without clearing all cookies?

Hey everyone I just had this problem and i tried all the stuff suggested, (chrome extensions/flags, Open GL, and incognito mode) and the only thing that worked for me was signing out of the figma app and signing back in lol

I have the same issue.
Changed Open GL settings, cleared Figna cookies, logged out and back in on app and browser… None of these worked… Any other secret weapon?

clearing figma cookies worked for me, other options did not

This worked for me

Opening in an incognito window worked for me too, thanks.

Clear cookies works for me.

I turned on chrome://flags/#enable-vulkan and now it works

You can search for “Figma” when under Chrome’s cookie settings page (search for “cookies” when under the general “Settings” in Chrome) and then it will give you the option to just delete the Figma cookies.

Hello 🙂

Thanks for your solution Cynthia, it worked for me too !

I have the same problem in Chrome and Brave.

Probably I could solve that by adjusting my settings, but shouldn´t their be a solution from Figma?

Cause I cant ask all my clients to follow those steps in there browser, just to open my prototype. They will simply not open the file than.

Is there any official Info from Figma about that bug?