
Webflow development: Rive, Lottie and three.js alongside GSAP scrolling
Webflow animation and interactions
Animation for Webflow sites that explains the product instead of decorating it: Webflow interactions for simple motion, GSAP for scroll and timing, Lottie and Rive for illustration, and three.js for 3D, loaded only when visible so the first screen stays fast.
Built with motion


The right tool for each job
Hover states, reveals and simple scroll effects, editable in the Designer.
Scroll-driven sequences and precise timing.
Vector illustrations exported from compatible tools; file size and rendering cost depend on the animation.
Interactive illustrations that react to the visitor.
3D scenes, loaded only when they come into view.
Built in from the start
FAQ
It can, so each piece of motion is checked on a phone before it is approved. Heavy pieces load only when they are visible, which keeps the first screen fast. Motion is kept to what explains the page, and everything still works with reduced motion turned on.
Page text and images stay editable in Webflow, and so do Webflow interactions set up with clearly named settings. A rendered sequence, Rive state machine or Lottie illustration may need its original source file and the tool that made it, and custom code needs its notes. I explain what your team can change at handover.
I choose by the behaviour the page needs and who has to maintain it. Webflow interactions suit reveals, scroll and hover effects that an editor can see and adjust in the Designer. Custom code suits precise timing or behaviour Webflow does not offer. Length alone does not decide it.
Agree what the animation explains and what visitors see before it loads or when reduced motion is requested. Test keyboard use, content readability and the cost on a representative phone. Text may remain editable while animation source files or code require specialist changes.
Choose the page that helps with your next decision.