Memorisely
Motion Design

Spring animations explained

Stiffness, damping and bounce, and when springs feel better than fixed durations.

Zander Whitehurst

7 min read

Most people learn UI motion through durations and easing curves. You pick a timing, choose a cubic bezier and the animation runs from start to finish exactly as planned. It is a great model, and it covers a lot of ground. But there is another way to describe motion that often feels more natural, especially for interactive interfaces: springs.

Spring animations are based on physics rather than time. Instead of saying "move this over 300ms with this curve", you describe the physical properties of a spring and let the motion emerge. The result is movement that feels organic, responds beautifully to interruption and works naturally with gestures.

What a spring animation actually is

Imagine attaching an element to its destination with an invisible spring. When you change the target, the spring pulls the element towards it. Depending on how the spring is set up, the element might glide smoothly into place, overshoot slightly and settle back or wobble a few times before coming to rest.

The key difference from a duration based animation is that there is no fixed end time. The animation finishes when the spring settles. That sounds like a small detail, but it changes how motion behaves in some important ways, which we will come to shortly.

The three core properties

Most spring systems, including Motion for React, describe a spring with three physical properties.

Stiffness. How strong the spring is. A stiff spring pulls hard and moves the element quickly towards its target. A loose spring pulls gently and feels slower and softer. Higher stiffness means snappier motion.

Damping. How much resistance the spring has, like friction or moving through liquid. Low damping lets the spring oscillate, bouncing back and forth before it settles. High damping smooths that out, so the element eases into place without overshooting. Too much damping and the motion feels sluggish.

Mass. How heavy the element is. A heavier mass takes longer to get moving and longer to stop, making the animation feel weightier and slower. In practice, many teams leave mass at its default of 1 and tune stiffness and damping instead.

These three interact. A high stiffness with low damping gives a fast, bouncy feel. A high stiffness with high damping gives a fast, crisp feel with no wobble. A low stiffness with high damping gives a slow, gentle drift.

Two properties do most of the work, and their combination decides how a spring feels.

Bounce and duration

Tuning stiffness, damping and mass directly can feel abstract, especially for designers used to thinking in milliseconds. That is why Motion also offers a simpler model based on two values: duration and bounce.

With this approach you set roughly how long the spring should take and how bouncy it should be. A bounce of 0 means no overshoot at all, a smooth settle into place. A bounce of 0.25 adds a gentle, noticeable overshoot. Values above about 0.4 start to feel playful and cartoonish.

For most product interfaces, a small bounce or none at all is the right choice. Bounce is fun, but it draws attention to itself. Save the bouncier settings for moments that deserve a bit of personality, like a success state or a playful onboarding step.

Most product UI sits at the low end, with higher bounce saved for moments of personality.

When springs beat durations

Duration based animations are excellent for predictable, one off transitions, like a tooltip fading in or a page cross fading. Springs shine in situations that are more dynamic:

  • Interruptible interactions. When users can change their mind mid animation, such as toggling a panel open and closed quickly.
  • Gestures. Dragging, swiping and flicking, where motion needs to continue naturally from the user's hand.
  • Layout changes. Items reordering, expanding or resizing, where the distance travelled varies from case to case.
  • Physical metaphors. Sheets, cards and drawers that should feel like real objects with weight.

If an animation will always run from the same start to the same end without interruption, a duration and easing curve is often simpler. If the user can affect it while it is happening, reach for a spring.

Interruptibility

This is where springs really earn their place. Imagine a drawer that slides open over 300ms. Halfway through, the user changes their mind and closes it. With a duration based animation, the system has to decide what to do. Often it starts a fresh 300ms animation from the current position, which looks odd because the drawer suddenly reverses at a constant planned speed, ignoring the momentum it had.

A spring handles this naturally. It carries its current velocity into the new target. The drawer decelerates, changes direction and heads back smoothly, exactly as a physical object would. That continuity makes interfaces feel far more responsive. Users never feel like they have to wait for the interface to finish before it will listen to them.

A spring carries its current velocity into the new target, so changing your mind feels natural.

Gestures and velocity

Springs are especially powerful with gestures. When someone flicks a card or releases a bottom sheet, their finger has velocity. A good animation should pick up that velocity and continue from it.

With a duration based animation, you lose that information. The card starts its animation from a standstill, as if the flick never happened. With a spring, the release velocity feeds straight into the motion. A hard flick sends the sheet flying to its open position. A gentle release lets it settle softly. The interface feels connected to the user's hand.

This is why native mobile platforms lean so heavily on spring physics.

Using springs in Motion for React

Motion for React, formerly known as Framer Motion, makes springs straightforward. In fact, it uses springs by default for physical properties like x, y and scale. You can tune them through the transition prop:

<motion.div
  layout
  drag="x"
  dragConstraints={{ left: 0, right: 0 }}
  animate={{ scale: isOpen ? 1 : 0.96 }}
  transition={{ type: "spring", stiffness: 400, damping: 30 }}
/>

Here the element uses a fairly stiff, well damped spring, which gives a snappy movement with no wobble. When the user drags and releases it, Motion carries the drag velocity into the spring as it returns to its constraints. The layout prop means size and position changes also animate with the same spring.

If you prefer thinking in time, you can write transition={{ type: "spring", duration: 0.4, bounce: 0.15 }} instead. Both approaches produce real spring motion. Pick whichever your team finds easier to reason about, and stick with it.

A few starting points:

  1. Snappy UI feedback. Stiffness around 400 to 500, damping around 30 to 40.
  2. Gentle layout changes. Stiffness around 200 to 300, damping around 25 to 30.
  3. Playful moments. A bounce of around 0.3, used sparingly.

Treat these as named tokens in your motion system, such as spring-snappy and spring-gentle, so everyone uses the same presets.

Named spring presets give the whole team the same snappy, gentle and playful motion.

Watch out for the pitfalls

Springs are not a cure for everything. Because they have no fixed end time, they can be harder to coordinate with other animations. A very loose spring can take much longer to settle than you expect, leaving tiny movements visible after the main motion has finished. And too much bounce can quickly make a serious product feel like a toy.

Remember reduced motion too. Users who prefer reduced motion should not get bouncy springs. Motion provides a useReducedMotion hook, so you can swap springs for simple fades when needed.

Feeling it for yourself

The first time I really understood springs was while building a bottom sheet for a mobile prototype. I had spent an hour tweaking durations and curves, and it never quite felt right. Every time I flicked it, it ignored how hard I had flicked. I switched to a spring with a little damping, and suddenly it felt like a physical object under my thumb. I have shown that exact before and after to students many times since, and the reaction is always the same. People do not need to understand the maths. They feel the difference immediately.

That is the best way to learn springs. Open a playground, change stiffness and damping, and drag things around. If you want structured guidance building gesture driven, spring based interactions, the AI Motion Design bootcamp covers springs in Motion for React in depth. Once you start thinking in springs, durations will feel like only half the picture.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all