Figma Weave Service Unavailable: How to Fix

When Figma Weave encounters a "Service Unavailable" error, the platform's real-time synchronization and AI-assisted design components fail to load. This issue typically stems from a localized API routing block, an active service outage on Figma’s infrastructure, or corrupted local cache files.

Because Figma Weave relies heavily on persistent WebSocket connections to sync design elements and processing states, even minor network drops can trigger persistent connection failures. Follow these steps to isolate the issue and restore your workspace.

1. Verify Figma's Live System Status

Before changing any local network or app settings, verify whether the problem is on Figma's end. Figma Weave operations run on sub-services that may experience outages independently of the main Figma design editor.

1. Open a browser and navigate to status.figma.com.
2. Look for outages listed under "Figma Design," "Figma AI," or "Real-time Collaboration."
3. Check official status feeds or third-party monitoring platforms (like Downdetector) to see if other designers are reporting regional service drops.

If a global outage is active, wait for Figma’s engineering team to deploy a server-side fix. If all systems are reported operational, proceed with the local troubleshooting steps below.

2. Force Clear the Figma App Cache

Corrupted cache files in the Figma Desktop app frequently prevent Weave components from initializing correctly, throwing generic service errors. Clearing these files forces the app to download fresh assets.

For macOS: 1. Completely close the Figma desktop application (`Cmd + Q`). 2. Open **Finder** and press `Cmd + Shift + G` to open the "Go to Folder" prompt. 3. Paste the following path: `~/Library/Application Support/Figma/` and press **Enter**. 4. Locate the directories named `Cache`, `CachedData`, and `GPUCache`. 5. Drag these folders to the Trash, empty the Trash, and restart Figma.

For Windows: 1. Close Figma completely from your taskbar or Task Manager. 2. Press `Windows Key + R` to open the Run dialog box. 3. Type `%APPDATA%\Figma` and press **Enter**. 4. Locate and delete the `Cache`, `CachedData`, and `GPUCache` folders. 5. Relaunch the Figma Desktop app.

3. Diagnose WebSocket and Protocol Blocks

Figma Weave utilizes WebSockets to maintain a live connection between your canvas and Figma's cloud servers. Strict corporate firewalls, virtual private networks (VPNs), and ad-blockers can block these protocols.

1. Temporarily Disable VPNs and Proxies: Turn off your VPN or proxy server to see if Weave reconnects. If it does, configure your VPN to bypass traffic for *.figma.com.
2. Inspect Browser Console (for Web Browser users):
3. Press F12 or right-click and select Inspect, then go to the Network tab.
4. Filter the network requests by WS (WebSockets).
5. Reload the page. Look for red/failed connections to domains like wss://*.figma.com. If these are blocked, your network firewall is stopping Weave traffic.
6. Whitelist Figma Domains: Ensure your IT administrator or local firewall rules allow traffic through port 443 for *.figma.com and *.amplitude.com.

4. Reset Local DNS Cache

Stale DNS records can route your connection to an inactive Figma edge server, resulting in a 503 or "Service Unavailable" screen.

• On Windows: Open Command Prompt as Administrator, type ipconfig /flushdns, and press Enter.
• On macOS: Open Terminal, type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, press Enter, and input your system password.

Once completed, restart your browser or the Figma app and attempt to reload the Weave tool.

When to escalate

If you have cleared your cache, verified that Figma's public status is green, and confirmed that the error occurs on both your home and mobile hotspot networks, the issue may be specific to your Figma account configuration or seat license.

Before contacting Figma Support, open the browser's developer tools (or the Figma desktop developer console via Help > Toggle Developer Tools), take a screenshot of any red console errors, and export a network HAR file. Provide these files to Figma's technical support team to expedite your ticket.