Storyline: Animate or GSAP in JavaScript animations

GSAP 3.11.3 (released in September 2022) is bundled with Storyline, and its core API is exposed, allowing you to use standard GSAP methods without loading the library externally.

As of early 2026, the current GSAP version is 3.15.x, and the library is now 100% free for all users, thanks to Webflow’s support. Storyline has not been updated to this latest version, so if you want to take full advantage of GSAP’s capabilities especially its newer features and plugins you’ll need to load a more recent version via CDN or local files and register any plugins accordingly. Some of these plugins were previously paid but are now freely available, although they are not included in Storyline’s built-in version.

Even without plugins, many of which are typically used by more experienced developers, GSAP remains one of the most powerful JavaScript animation libraries available today.

It’s also important to note that GSAP cannot be used directly with objects referenced through the newer Storyline JavaScript API (e.g. object('id')), since those are not actual DOM elements. While GSAP can animate generic JavaScript objects, Storyline object references are controlled through its own API and don’t behave like standard animatable objects. For GSAP to work reliably in Storyline, you typically need to target the underlying DOM elements instead of the API object references.

Speaking of long-term use, I remember when jQuery was available in Storyline in a similar way to how GSAP is now. I had dozens of scripts that relied on it without referencing an external library. Then, when Articulate removed jQuery support, all those scripts broke and had to be rewritten to include the library via external links.

The same risk applies to GSAP. If Articulate decides to remove or change its built-in GSAP support, you could run into similar issues and end up spending time updating projects to reference GSAP externally.

The Storyline JavaScript API (including object() and related methods) and the animate command serve different purposes, and they are not direct alternatives to each other.

The animate command exposed in Storyline appears to be a simplified wrapper around the Web Animations API, which is the native browser system for handling animations. It is used internally for built-in and other motion effects because it is lightweight and integrates directly with the Storyline runtime environment. 

If you’re learning this from scratch, the Web Animations API is easier to understand for beginners but only at a basic level. What makes it "easier" is that it is very close to natural browser behavior: you tell an element what properties should look like over time, and the browser handles the animation. You don’t need a library, build system, or extra setup.

GSAP is actually easier to use for real projects, even though it may initially seem more complex. Once you understand the basics, it removes a lot of the manual work you would otherwise need to handle with native browser animations. The best place to start learning and practicing GSAP is the Creative Coding Club , which is widely regarded as one of the most comprehensive and beginner-friendly learning resources for GSAP development. 

This should give you some basic information on whether you should use either approach. I would say that practising both solutions is certainly beneficial, but for more powerful and complex animations I would always choose GSAP if I had to pick just one.

If you have any questions or need help with coding, don’t hesitate to ask—and feel free to keep this topic active so everyone can contribute and support each other’s learning progress.