Skip to main content
vinicius.tinte
vinicius.tinte
New Member
August 14, 2026
Question

Figma Design System Component Loses All Interactions When Moved to Another File

Every time I move or import a component from my Design System into another Figma file, it loses all of its interactions — including click, hover, pressed states, overlays, and other prototype interactions.

The component itself, variants, and properties are still there, but the interactions are completely lost or stop working as expected.

Has anyone experienced this issue? Is there a specific Figma setting, Library configuration, or limitation that could cause prototype interactions to be lost when moving a component between files?

I'd really appreciate any insights or suggestions on how to prevent this from happening.

2 replies

Bartosz_Ammer
New Member
October 7, 2026

I'm experiencing similar issues when working with library components. Placing a published component in another project results in atom instances inside to reset to their default states. Also the atom interaction is not working.
I can still see all component properties and can switch between them. Even the atom interaction is present, but it's not working in any other file apart from the library project.
The infuriating part is that all of this was working before so I know it was set up correctly, and broken with an update about month ago.

    Celine_
    Figmate
    Celine_
    Community Support
    October 7, 2026

    Hey both, Celine from the Community Support team at Figma here, thanks for sharing these reports.

    From what I understand, you’re both describing issues with component interactions outside the source file (either interactions disappearing or remaining visible but no longer working, with nested instances resetting to their default states.) Since this doesn’t appear to be working as expected, I’d like our support team to take a closer look at both examples.

    First, please try making a small change to one affected component in the source library . For example, hiding and then unhiding a layer, and republishing the library. Then accept the library update in the affected file and test the interactions again.

    If the issue persists, submit directly a bug report through the Support Hub: click Start a chat, type “Report a bug, Contact an agent”, press Enter, and follow the prompts.

    In the form, include links to your source library and an affected file, plus a short recording showing what works in the source file and what happens in the other file. Please also grant Can View access to both files to support-share@figma.com so our team can reproduce the behavior and investigate further. Thank you!

      Terms & ConditionsAccessibility statement