Webflow recently released a new version of native interactions: Interactions with GSAP. This article describes the differences between Interactions with GSAP and the previous version, Classic Interactions. Both versions are still available today. To switch between versions, use the dropdown at the bottom the Interactions panel.
What’s the difference between Interactions with GSAP and Classic Interactions?
Interactions with GSAP launched in summer of 2025. It is the most robust and up-to-date version of interactions, and uses the GSAP engine for creating, editing, and displaying interactions. This version includes built-in GSAP interactions like SplitText, Staggers, and ScrollTrigger, a horizontal timeline, and increased ease of reuse for interactions. Interactions with GSAP employs a trigger/target/action creation model.
Classic Interactions is the version of interactions that existed prior to Interactions with GSAP. This is the default version in Webflow, though you can switch between the two at any time. Classic Interactions employs a Page/element triggers → animations creation model.
Version comparison table for reference:
| Only in Interactions with GSAP |
Currently only in Classic Interactions |
| Horizontal timeline |
Custom eases, advanced easing |
| Realtime collaboration |
Shared libraries |
| Actions for: repeat, stagger, split text |
Navbar, dropdown, tab, and slider change events |
| Prefers reduced motion settings |
Page branching |
| Granular scroll settings, new click/tap and hover settings |
Support for Rive and Spline |
| Advanced targeting (more than just element and class) |
Creating interactions on non-primary locales |
| Customizable action presets |
Cross site copy/paste |
|
Animating variable values |
|
Interactions included with component exports (aka DevLink) |
Which version of interactions should I use?
Interactions with GSAP is the newest version of Webflow interactions. For most use cases, we recommend this version.
That said, you might want to use Classic Interactions if you require use of a feature that is not yet supported by Interactions with GSAP or if you already use Classic Interactions and want to avoid additional website bloat.
Frequently asked questions
Why doesn’t Interactions with GSAP include all the same capabilities as Classic Interactions?
We are still adding capabilities regularly –– these are coming soon! In the meantime, you can continue using Classic Interactions for anything missing from Interactions with GSAP.
Can I use both Classic Interactions and Interactions with GSAP on the same site?
Yes, but there may be site performance implications.
What are the performance implications of using multiple versions of interactions on my site?
Site performance is highly dependent on your specific use case, so we always recommend testing your site. For many, using multiple versions of interactions won’t be a problem.
However, each version of Webflow Interactions requires load in of its own resources, so the more versions of interactions you use on a site, the less performant your site will be.
The following options are ranked from best to worst expected performance:
Interactions with GSAP only
Classic Interactions only
Interactions with GSAP + Classic Interactions