figma weave generating clipped content inside frames

Generated screens and UI components from Figma Weave can sometimes look incomplete because text blocks, buttons, or child containers are cropped off past the outer frame boundaries. This happens when Weave builds fixed-height containers with the Clip content setting turned on by default.

Quick checks

• Inspect the parent generated frame in the right sidebar to see if Clip content is checked.
• Verify whether generation stopped abruptly before calculating layout bounds via /fix/figma-weave-not-generating.
• Check if canvas zoom settings or scroll bounds are concealing elements outside the visible viewport.

1. Uncheck Clip Content on parent containers: Select the main generated frame on your canvas. In the right sidebar under the Frame header, uncheck the Clip content box to immediately reveal all hidden layer elements.
2. Change vertical frame height to Hug contents: Select the outer frame and update its vertical sizing from a fixed height value to `Hug contents`. The container will automatically expand downward to encompass all child elements.
3. Check for missing canvas tools or UI overlays: If clipping occurs because the generation interface froze mid-build, follow /fix/figma-weave-missing-in-figma to restore the Weave interface and re-generate the section.
4. Add vertical overflow directives to prompts: Refine your prompt instructions by adding explicit visibility commands, such as "ensure complete vertical visibility for all list items" or "allow dynamic height expansion without clipping".
5. Inspect nested Auto Layout padding and margins: Large internal padding values can push child items outside frame bounds. Reduce padding in the Auto Layout panel to pull elements back into view.

Still stuck?

If clipped content persists across new blank files, test generating smaller section chunks rather than full page layouts to isolate frame calculation errors. Figma Weave Support is an independent troubleshooting resource and is not affiliated with Figma.