Skip to main content
Question

Connections snapping to sections instead of frames

  • June 1, 2026
  • 1 reply
  • 7 views
Geno Samin

Hi, I'm experiencing an issue with prototyping that seem to have appeared recently and wondering if others have run into the same.

Connections snapping to sections instead of frames

When I drag a connection from one frame to another, it keeps connecting to a section rather than the frame itself. I understand Figma supports sections as prototype destinations intentionally, but it makes it really hard to target a specific frame precisely.

When I try to set the destination manually via the dropdown instead, the frame doesn't show up in the list at all — only the section does. So I can't work around it that way either.

Is there a reliable way to force the connection to land on the frame and not the section wrapper?

    1 reply

    djv
    Figmate
    • djv
    • Community Support
    • June 1, 2026

    Hey ​@Geno Samin, thanks for reaching out about this! 
     

    I understand why this behavior is frustrating, but what you're experiencing is actually intentional. Connectors snap to the outermost container they intersect, and since sections are top-level, they take priority over the frames nested inside them. Here’s Figma's Help Center article on using sections in prototyping. 

     

    That said, here are two workarounds to get your connection landing on the correct frame:

    1. Use the modifier key override

    • Click and hold the connector's endpoint, then press Cmd (Mac) or Ctrl (Windows). This suppresses the automatic snapping to the section and lets you place the anchor point precisely on the frame you want.

    2. Temporarily move the frame

    • Drag your target frame completely outside the section onto the open canvas, snap your connection to it, then drag it back into the section. The connection should hold.

     

    As for the dropdown not showing frames, that's a known limitation when frames are nested inside sections in prototype mode. The modifier key method above is currently the best fix. Give these a try and let me know if either works for your setup!

    Terms & ConditionsAccessibility statement