Why Your CSS Transition Feels Robotic (It's Probably the Easing Curve)

You set transition: transform 0.3s on a button, test it, and something feels off. The timing isn't wrong — 0.3 seconds is a perfectly normal duration — but the motion reads as mechanical instead of natural. Nine times out of ten, the problem isn't the duration at all. It's the default easing, or the absence of one you actually chose on purpose.

Nothing in the real world moves at a constant speed

CSS's default timing function, if you don't specify one, is ease, which is already better than nothing. But plenty of transitions get written with linear or with whatever was copy-pasted from a tutorial, and linear motion is the real culprit behind that robotic feel. A ball you drop doesn't fall at a constant speed — it accelerates. A car pulling away from a stop doesn't instantly hit cruising speed — it ramps up. Your eye is tuned to expect acceleration and deceleration from anything that moves, and a linear transition violates that expectation on every single frame. It's not a big error, but it's a consistent one, which is exactly what makes it register as "off" without most people being able to say why.

What a cubic-bezier curve is actually describing

CSS's cubic-bezier(x1, y1, x2, y2) function defines a curve with two fixed endpoints — (0,0) for the start of the transition and (1,1) for the end — and two control points you supply. The curve doesn't plot position on a graph the way you might assume; it plots progress (0 to 1) against time (0 to 1). A control point pulled up and to the left makes the animation race ahead early and coast at the end. A control point pulled down and to the right makes it start slow and accelerate hard near the finish. The two control points are what let you describe literally any acceleration curve CSS keywords can't name, which is the entire reason the function takes four numbers instead of a word.

The keyword shortcuts are curves in disguise

ease, ease-in, ease-out, and ease-in-out aren't a separate, simpler system — they're named presets that expand to specific cubic-bezier values. ease is cubic-bezier(0.25, 0.1, 0.25, 1). ease-in-out is cubic-bezier(0.42, 0, 0.58, 1). Knowing this matters because it means tweaking a keyword-based transition that still feels wrong isn't a dead end — you can start from the keyword's actual numbers and nudge them, instead of guessing blindly between four fixed options.

Match the curve to what's entering or leaving the screen

Motion design has a rule of thumb worth stealing: things that enter the screen should decelerate into place (ease-out, control points pulled toward the top-left), and things that leave the screen should accelerate away (ease-in, control points pulled toward the bottom-right). A modal that appears should slow down as it settles — that's what makes it feel like it arrived deliberately. A tooltip that disappears should speed up as it goes, because lingering on the way out reads as hesitant. Using the same symmetric ease-in-out for both entrances and exits is the second most common reason transitions feel generic, right after linear timing.

Why you can't get a bounce out of a single cubic-bezier

If you've tried to recreate a bouncy, springy effect using cubic-bezier and ended up frustrated, there's a hard mathematical reason: a cubic Bezier curve between two fixed endpoints can only change direction so many times, and a real bounce needs multiple oscillations — overshoot, settle back, overshoot again, smaller each time. You can fake a single overshoot by pushing a control point's y-value above 1 or below 0 (which cubic-bezier does allow), but a proper multi-bounce spring effect needs @keyframes with several steps, or the CSS linear() easing function, not a single cubic-bezier curve. Knowing that boundary up front saves a lot of time spent fighting the wrong tool.

If you want to see a curve's shape and its animated effect at the same time instead of guessing at four numbers, the Cubic Bezier Generator lets you drag the control points and watch a live preview, then copy the resulting function straight into your CSS.