figma weave prompt stuck on reading selection

When prompting Figma Weave to modify or extend existing artwork, the AI first analyzes the selected canvas nodes. If Weave gets stuck on "reading selection" or "analyzing context," follow these troubleshooting steps from Figma Weave Support to resolve the issue.

Quick checks

• Verify that your selection does not exceed hundreds of deeply nested vector layers.
• Confirm whether backend infrastructure is operational at /fix/figma-weave-down.
• Ensure your network connection isn't blocking WebSocket communication required for live analysis.

1. Simplify the selected node structure

Large frames containing hundreds of individual vectors, complex boolean groups, or hidden layers take a long time to parse. Group your selection into fewer top-level frames or temporarily hide non-essential background layers before generating.

1. Flatten complex vector shapes

Complex vector paths with thousands of anchor points can stall the contextual parser. Right-click intricate vectors and select Flatten (`Cmd + E` on macOS or `Ctrl + E` on Windows) to convert them into simplified single-path shapes.

1. Deselect missing or un-rendered custom fonts

If your selected frames use custom fonts that aren't fully loaded in your browser or desktop app, the parser can hang waiting for font metrics. Convert missing font layers to standard web fonts like Inter or Arial before running Weave.

1. Force restart the generation tool

Close the Weave interface, clear your canvas selection, and launch the tool again. If generation remains stuck across attempts, follow our resolution guide at /fix/figma-weave-not-generating.

1. Relaunch Figma with a cleared memory state

Save your file and restart Figma completely to release system RAM. High canvas memory usage often prevents Weave from completing selection analysis.

Still stuck?

If the context engine continually hangs on specific components, test running the prompt on a minimal copy of the frame inside a new document file.