Unable to run any Figma module all of a sudden

Hi ​@Nikhil Bhushan ,

I understand that you’re suddenly seeing a WebAssembly.Instantiate() error across Figma products and are unable to continue working on your Figma Make project.

First, could you let us know whether this happens in the browser, the desktop app, or both?

To start troubleshooting, please try the following:

• Close any unused Figma tabs.

  • Force-quit and restart your browser or the Figma desktop app.

If the issue continues, WebAssembly error often indicates a problem with how Figma is being loaded. In some cases, this can be caused by network restrictions or browser settings.

To troubleshoot further, could you please try the following:

• Make sure your browser and the Figma desktop app are up to date, and try temporarily disabling any browser extensions to see if the issue persists.
• Try accessing Figma from a different network (for example, using a mobile hotspot) to check whether the issue continues.
• If you’re using a firewall, proxy, or VPN, we recommend checking with your IT or systems administrator to ensure that:
  • Port 443 is unblocked
  • *.figma.com is added to any VPN, proxy, firewall, or antivirus allowlists, as described here: Adjust your network settings
     

You may also find this article helpful: Connection or server error 403

If the issue still persists after trying the steps above, please submit a bug report via Contact support from the (?) icon in your Figma Make file. The chatbot will guide you through opening a report with our team so they can investigate further and assist you directly.

You can also refer to this guide for what to include in your report: What to share in a bug report to Figma Support

Thanks,

I am running in the chrome browser on my corporate windows laptop. It is available via my organizations authenticated account and VPN connection and nothing changed with my access or the network/VPN/firewall. Things were working one minute and stopped the next, and haven’t resolved despite trying all the typical things - clearing cookies, site setting, restarting laptop etc. At a complete loss here.

Looks like the IT department was able to identify the issue and fix it. Thanks for the help looking into it.

Glad to hear it’s fixed — thanks for the update!