How to Fix Figma Weave Stuck on Loading Screen

When Figma Weave gets stuck on a loading screen, it typically indicates a communication breakdown between the local Figma client and the backend generation servers. Because Figma Weave relies on continuous API handshakes to parse design systems and return structural code, a minor network blip or corrupted local cache can cause the interface to hang indefinitely with a spinning wheel.

Follow these sequential troubleshooting steps to isolate the issue and restore functionality.

1. Verify Figma's Service Status

Before troubleshooting your local setup, confirm that Figma's servers are not experiencing a system-wide outage or API degradation.

• Visit the official Figma Status page to check if there are active incidents affecting plugins, widgets, or general API performance.
• Look specifically for issues related to "Figma AI," "Plugins and Widgets," or "External Integrations."
• If an active outage is reported, wait for Figma's infrastructure team to resolve the incident. Your loading screen will clear automatically once services are restored.

2. Hard Refresh the Figma Client

Stale cache files in the browser or the desktop client can prevent Figma Weave from initializing its scripts. A hard refresh forces the environment to reload all resources from scratch.

If using a Web Browser: * **Mac:** Press `Cmd` + `Shift` + `R` (or hold `Shift` and click the browser's Reload button). * **Windows:** Press `Ctrl` + `F5` (or `Ctrl` + `Shift` + `R`).

If using the Figma Desktop App: * **Mac:** Navigate to the top menu and select **Figma** > **Preferences** > **Clear Cache and Reload**. * **Windows:** Click the Figma menu toggle (top-left logo), navigate to **Preferences** > **Clear Cache and Reload**.

3. Clear Local Client Cache Files

If a standard reload does not bypass the stuck loading screen, the desktop application’s underlying cache folder may be corrupted. You can safely delete these directory files manually.

On macOS: 1. Close the Figma Desktop App completely. 2. Open **Finder** and press `Cmd` + `Shift` + `G` to open the "Go to Folder" prompt. 3. Paste the following path and press Enter: `~/Library/Application Support/Figma` 4. Select all files and folders inside this directory and move them to the Trash. 5. Restart Figma and attempt to launch Weave.

On Windows: 1. Close the Figma Desktop App. 2. Press `Windows Key` + `R` to open the Run dialog box. 3. Type `%APPDATA%\Figma` and click **OK**. 4. Locate and delete all files inside this directory. 5. Reopen Figma, log back into your account, and load the plugin.

4. Test in an Incognito Window

Browser extensions (such as aggressive ad-blockers, script blockers, or privacy-focused add-ons) can block the background WebSocket connections that Figma Weave uses.

1. Open your browser in Incognito/Private Browsing mode.
2. Log into your Figma account.
3. Launch the Figma Weave interface.
4. If Weave loads instantly, the block is caused by an active browser extension. Temporarily disable extensions one-by-one—specifically those managing scripts, cookies, or tracking—until you locate the culprit.

5. Review Firewall and VPN Settings

Corporate networks, VPNs, and local firewalls often flag the high-frequency API traffic generated by AI tools.

• Disable VPNs: If you are connected to a personal or corporate VPN, disconnect temporarily to see if the loading screen clears.
• Inspect Developer Tools: Press F12 (or Cmd + Option + I on Mac) to open the browser console. Look for red connection errors, particularly those displaying ERR_CONNECTION_TIMED_OUT or 403 Forbidden pointing to Weave or Figma API domains. If these exist, your network is actively blocking the integration.
• Whitelist Endpoints: If you are on a managed corporate network, request that your IT administrator whitelist Figma's primary domains alongside any dedicated Weave API endpoints.

When to Escalate

If you have cleared your cache, verified that Figma services are operational, and confirmed the issue occurs across multiple networks, you may be facing a specific account-level lock or a localized server-side error. Contact your team's IT administrator or reach out to Figma Support with a copy of your Console Log export (obtained from the developer tools panel during the stuck loading sequence).