Shared components: GSAP interactions fail when used cross‑project; converting to local shows interactions have been stripped

Design help Animations & Interactions
1

Hey folks,

Has anyone run into shared library components losing interactions when used in another project?

Context:

  • Rebuild project has a shared component library. Components and interactions work perfectly inside the origin project.

  • When those components are used in the old we site inherited (shared library installed), interactions don’t fire at all. If I “convert to local,” the interactions are stripped entirely.

  • Tested by Support in a blank project: same result—no interactions, and converting to local removes them.

What’s failing:

  • Native Webflow interactions driven by GSAP (no custom JS for these sequences).

  • Triggers bound to component internals via attributes (to avoid class collisions), and also tested as class‑based triggers. Both work in‑project; neither fires cross‑project.

  • Multi‑step sequences (e.g., cards enter, page background transitions, then resets) run fine on origin pages but never initialize in the destination project.

  • Indicators don’t load in the old project; looks like IX data/bindings aren’t transferring or initializing.

Environment notes:

  • Old site has a heavy legacy stylesheet, but Support reproduced the failure in a blank project, so it seems not project‑specific.

  • GSAP is present across projects; the issue appears to be with interaction bindings, not script presence.

Support status:

  • Webflow Support validated the bug: components shared into other projects don’t retain working interactions; converting to local removes them.

  • They’ve escalated internally but currently have no fix or workaround.

Questions for the community:

  1. Have you seen shared library components lose IX3 GSAP when imported cross‑project?

  2. Any reliable workaround to preserve interaction bindings across projects, including after “convert to local”?

  3. Is there a rebinding or reinitialization flow that works post‑import, the interaction are even gone when pasting elements across.

  4. If you solved it, was the fix tied to class naming, attribute scoping, I’ve tried it all and they still just vanish.

Client has disabled sharing the read-only (new redesigned site is still under NDA), but nothing special or new apart from that it’s on GSAP instead of IX2. Most of the site is still just basic components of new design systems and the first few section that they now need on the old site which is getting interaction stripped out.

2 Likes
2

So I’ve had confirmation that GSAP / IX3 does not work in shared libraries across projects at this time. Webflow have also been kind enough to go and update the documentation to now reflect this so you don’t go promising things in shared libraries that don’t work. Holding thumbs for a future when this works and IX2 has been phased out.

2 Likes