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 available today. To switch between versions, use the dropdown at the bottom of 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 is the default version in Webflow, though you can switch between the two at any time. This version of interactions includes built-in GSAP interactions like SplitText, Staggers, and ScrollTrigger, a horizontal timeline, an advanced easing editor, 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. 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 |
Navbar, dropdown, tab, and slider change events |
| Realtime collaboration |
Page branching |
| Actions for: repeat, stagger, split text |
Creating interactions on non-primary locales |
| Prefers reduced motion settings |
Interactions included with component exports (DevLink) |
| Granular scroll settings, new click/tap and hover settings |
|
| Advanced targeting |
|
| Customizable action presets |
|
| Component instance scoped interactions |
|
| Component canvas support |
|
Which version of interactions should I use?
Interactions with GSAP is the recommended version of Webflow interactions and the default on all new sites. In addition to a more robust feature set, Interactions with GSAP:
- Delivers smoother performance across browsers and devices
- Is the only version that will be forwards compatible with new features
- Is required for templates submitted to the Webflow Marketplace
That said, you might want to stick with Classic interactions if you need a feature not yet available in Interactions with GSAP. We're actively closing that gap — check the comparison table above to see the current state.
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