Linear
No easing at all: the element moves at one speed from start to end. Useful as a baseline, and for a progress bar that must not lie.
Pikkola Motion Lab, tool No. 53
Two control points decide whether a menu snaps, floats or overshoots. Drag them on a real cubic-bezier, watch four properties move beside a baseline, then copy the same curve into CSS, Tailwind or Framer Motion.
The studio
Drag a handle or type a value. Both lanes start together and share a clock, so the gap between them is exactly the easing you chose.
cubic-bezier(0.34, 1.56, 0.64, 1)
x stays between 0 and 1, because it is a moment inside the duration. y is progress: it may pass 1 or drop below 0, and the shaded area shows when it does.
Tab to a handle and use the arrow keys. One press moves 0.01, with Shift 0.1.
at 0%: yours 0.00, baseline 0.00
Both lanes run at 60fps in this tab. Nothing is recorded and nothing is uploaded.
Fourteen starts
Each card opens in the studio with its numbers already set. A marked card leaves the box on purpose: that is where the bounce comes from.
No easing at all: the element moves at one speed from start to end. Useful as a baseline, and for a progress bar that must not lie.
The browser default. A quick start, a long settle, and the shape most pages already feel like.
Material's standard curve, for an element that stays on screen and changes state.
Starts at full speed and slows the whole way in, for something arriving from off screen.
Starts slow and leaves at full speed, for something dismissed or sliding out.
One overshoot, then a settle. The motion Apple uses for sheets and toggles.
A gentler spring: it passes the end by 0.3 and returns without a wobble.
The largest overshoot here, 0.78 past the end. Small objects at 400ms or less.
Almost nothing in the middle: it holds, then arrives. A switch with two states feels like this.
Winds up backwards before it leaves. Keep it on small elements, or it reads as a mistake.
Very fast leaving the start, then a long glide. Good for large panels.
A symmetric in-out with a strong middle, for a full screen change.
The quietest in-out: close to linear, with softer corners.
Accelerates late and stops dead, like something thrown and caught.
How it reads
A cubic-bezier is two dimensions in one line of code. Time runs along x, progress runs along y, and the two never mix.
01
x runs left to right from 0 to 1 and stays inside the box, because a moment cannot be negative or past the end. y starts at 0 and ends at 1. At x = 0.5 the curve already tells you how much of the distance is covered.
02
CSS allows y outside 0 and 1. At 1.56 the element travels past its destination and comes back. Below 0 it winds up before it leaves. The shaded strip at the top and bottom of the graph is the space where that happens.
03
cubic-bezier() takes x1, y1, x2, y2. The first pair is the handle leaving the start, the second is the handle arriving at the end. Move one and the middle of the motion changes while both endpoints stay where they are.
| Number | What it decides | Typical |
|---|---|---|
| x1 | How quickly the motion leaves the start. Larger holds it still for longer. | 0.2 to 0.4 |
| y1 | Where it is early on. Above 0.1 it has already moved; below 0 it goes backwards first. | 0 to 1.56 |
| x2 | When it settles. Smaller arrives earlier and eases out for longer. | 0.2 to 0.8 |
| y2 | Where it arrives from. Below 1 it climbs the last part; above 1 it lands from above. | 0.9 to 1.1 |
| duration | Not one of the four, but read with them: the same curve at 150ms and 900ms is two different gestures. | 150 to 2000ms |
x is a fraction of the duration. A negative or past the end moment would mean the animation starts before it was asked to or keeps going after it finished. Browsers clamp x to the box, and so does this editor. y has no such limit, because progress can overshoot.
It overshoots once. A real spring bounces several times, which four numbers cannot describe. The Apple-like preset gives the single overshoot most interfaces need. For a repeated bounce, use a keyframe animation or a spring library, which is a different kind of curve.
The lanes start together and share a clock, not a position. At any moment each one shows how far its curve has carried it. Pause the preview and scrub the timeline to see the pair at the same instant.
Short and close to linear: ease at 120 to 160ms, or 0.2, 0, 0.2, 1 for a slightly softer start. Save the long curves and the overshoot for something that appears, enters or travels across the screen.
The timing is identical, but the eye is not. Scale reads faster than opacity at the same duration, and rotation reads faster than translation. The four lanes exist so you can judge that on your own screen instead of taking it on trust.
No. The curve, the presets and the code run in this tab, the content policy sets connect-src to none, and the only thing kept is your language, theme and last curve in this browser.