Docs

Licensing

Two separate questions, often confused with each other: what you may do with the code here, and what the libraries it depends on require.

The component code

Every component on this site is MIT licensed. Installing writes files into your repository and the relationship ends there — no runtime, no package, no phone-home. Use it commercially, edit it beyond recognition, ship it. No attribution is required. A link back is welcome and never obligatory.

What you cannot get from here is a warranty. Every component is written to handle its own edge cases and clean up after itself, and each one states its acceptance criterion — but it is your production, so test it in your production.

GSAP

Some components use GSAP, and its licensing changed in a way worth being precise about. Since April 2025, following Webflow’s acquisition of GreenSock, GSAP is free for commercial use — including the plugins that used to require a paid Club membership, among them SplitText, MorphSVG, DrawSVG and ScrollSmoother. They all ship inside the gsap package on npm. Nothing here needs a subscription.

The standard license does carry one restriction. It prohibits implementing GSAP in tools that let users build visual animations without code in a way that competes with Webflow’s own visual animation building. Kinetichands you source code to edit rather than a no-code animation builder, which is a different kind of product — but if what you are building is closer to that description than to a codebase, read the license yourself rather than taking this paragraph’s word for it.

One rule follows from all this and is enforced in CI: GSAP source is never copied into this registry. The license grants use, not redistribution, and says nothing explicit about bundling GSAP inside another library. So components declare gsap as a dependency and the CLI installs it from npm under its own terms.

Most components have no dependency at all. Each component page lists exactly what it pulls in, and the cost badge tells you before you install.

No assets

Nothing in the registry is a binary. No fonts, no images, no video, no Lottie JSON — textures are generated procedurally and media is taken as a prop. That keeps every install text-only and means you can never inherit someone else’s licensed artwork by accident. It is checked on every build.

Techniques versus expression

Motion techniques are shared craft. A scroll-scrubbed cylinder of images, a magnetic cursor target, a pinned horizontal track — these are methods, and methods get reused constantly across the web. Every implementation here is written from scratch, and the licence above covers it.

What a licence never covers is content. The photographs, copy, typefaces and layout you put into one of these components are a separate question from the component itself, and shipping someone else’s media through your build does not become fine because the code around it is MIT. Take the mechanism; bring your own content.