Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 37 ยท Interactions and Animation

Webflow Interactions and Timelines

Build Webflow interactions step by step: element and page triggers, animation timelines, start states, staggering and easing. Includes a runnable timeline stand-in.

Webflow's strongest selling point for designers is its interaction system. Instead of writing animation code, you attach a trigger to an element and then build an animation out of actions placed on a timeline. This lesson walks through the workflow in the order you would do it in the Designer, and then rebuilds the timeline idea in a small JavaScript stand-in so you can see exactly what the panel stores.

Webflow runs in the browser at webflow.com, not on this site. Menu names below follow the Designer at the time of writing and may move slightly; the concepts stay stable. The runnable code is a stand-in, not Webflow's engine.

Where interactions live

Open the Designer, select an element, and look for the Interactions panel (the lightning-bolt icon in the right-hand panel group, or the Interactions tab). There are two kinds of triggers.

  • Element triggers belong to one element: mouse click (tap), mouse hover, scroll into view, while scrolling in view, mouse move over element.
  • Page triggers belong to the whole page: page load (the page finishes loading) and while page is scrolling.

When you create a trigger, Webflow also lets you pick what to run: either an animation you have already built (and reuse), or a new one.

Building a first animation: fade and rise on scroll

  1. Select a card element and give it a class such as card.
  2. In Interactions, add an Element trigger and choose Scroll into view.
  3. Under "Start an animation" click the plus sign and name it, for instance "Card reveal".
  4. Add an Initial state (what the element looks like before it plays): opacity 0%, move Y by 40 px.
  5. Add an animation step that goes to opacity 100% and move Y 0 px over 0.6 seconds with an ease-out.
  6. Set the trigger to play once, so the card does not hide again when you scroll up.

The initial state matters. Without it, the card would be visible on load and then jump to hidden when the animation starts. Setting an initial state makes Webflow hide the element immediately.

Timelines, steps and actions

An animation in Webflow is a timeline with one or more steps. Each step has a start time, a duration and one or more actions on a target. Actions include Move, Scale, Rotate, Skew, Fade (opacity), Size, Blur, Color changes and Transitions. Steps can be:

  • Sequential: step two starts when step one ends.
  • Parallel: several steps start at the same moment.
  • Delayed: a step waits a number of seconds first.

You can also target a class instead of one element, so one animation drives every element with that class. With Stagger (sometimes presented as "Affect: Class / Siblings" plus delays), items start one after another by a small offset, which makes a row of cards feel like one wave rather than six unrelated pops.

Easing and duration cheat sheet

Situation Duration Easing
Hover feedback 150โ€“250 ms Ease-out
Content appearing 400โ€“700 ms Ease-out or Out Quart
Menu opening 250โ€“400 ms Ease-in-out
Big hero entrance 700โ€“1000 ms Out Expo

Out easings start fast and slow down, which suits things entering the screen. Longer than a second usually feels sluggish unless it is a deliberate showpiece. The next lesson, Easing and Motion Performance, looks at the math.

A stand-in timeline

The code below is a stand-in that turns a list of steps into a schedule. It does what the Interactions panel does behind the scenes: compute a start and end time for each step, add a stagger offset, and report the total duration.

JS Stand-in: compute a timeline

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Reusing and organizing interactions

Webflow lets you pick an existing animation for a new trigger, so a single "Fade up" can serve a dozen sections. Name animations by what they do ("Fade up", "Menu open"), not by where they are ("Section 3 thing"). In large projects, keep a style guide page that lists each reusable interaction and its duration and easing, so every designer on the team picks the same motion language.

Mobile and reduced motion

Interactions can be turned off per breakpoint: in the trigger settings you choose the device types it should run on (for example desktop and tablet, not mobile). To respect the visitor's reduced-motion setting, a common approach is a small custom-code snippet or class that disables the animations when prefers-reduced-motion: reduce matches. The check itself is simple:

JS Stand-in: respect reduced motion

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common mistakes

  • Forgetting the initial state, so elements flash before they animate.
  • Animating width or height (causes layout reflow). Prefer Move, Scale and Fade.
  • Scroll-into-view triggers placed so low that short pages never reach them.
  • Playing the animation every time the element re-enters the viewport when it should play once.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the initial state of a Webflow animation do?

    The initial state hides or positions the element up front, so it does not flash in its final look before animating.
  2. 2. Which is a page trigger?

    Page load and while-page-is-scrolling are page triggers; the others attach to one element.
  3. 3. What is stagger used for?

    Stagger offsets the start time of each target so a group appears as a wave.
  4. 4. Which easing suits an element entering the screen?

    Ease-out starts fast and settles gently, which feels natural for arrivals.

Summary

  • Webflow interactions combine a trigger (element or page) with an animation timeline.
  • Set an initial state so elements do not flash before animating.
  • Steps run in sequence or in parallel; stagger offsets multiple targets.
  • Reuse and name animations carefully, and turn them off where they hurt (mobile, reduced motion).
  • Prefer transform and opacity actions over size changes.

Next: Wix Animations and Scroll Effects