Motion and Interaction · Step 2 · 7 min read
Duration: how long is right
Most interface motion should last between 100 and 400 milliseconds, and most of it is too slow. Where those numbers come from, the three things that change them (size, frequency, and whether something arrives or leaves), and how design systems turn them into tokens.
The right duration is the shortest one that doesn't feel like a jump. That's almost always shorter than you think. A tenth of a second changes how motion feels: at 100 ms a toggle feels like part of your finger, at 500 ms it feels like waiting for the interface. Designers tend to set animations long, because in a review you want to see them. Users don't want to see them; they want to see what changed. This lesson gives you the numbers, where they come from, and when to bend them.
What you'll be able to do after reading:
- Choose a starting duration for feedback, small and large movements
- Explain the 0.1 and 1 second limits and where they come from
- Make larger moves longer and exits shorter than entrances
- Read a design system's duration tokens and pick the right one
1. The duration ladder
- 100 ms
a checkbox, a toggle - 200 ms
a menu, a tooltip - 300 ms
a dialog, a panel - 500 ms
starts to drag - 1000 ms
a wait
transition: transform 300ms ease-out, with transition-duration changed per lane. With reduced motion on, every dot jumps, and that is the point of the setting.Play it a few times. Every dot travels the same distance with the same easing. At 100 ms it almost jumps. At 300 ms you see it move. At 1000 ms you wait for it.
NN/g's guidance gives the ranges most teams use (Page Laubheimer, Executing UX Animations: Duration and Motion Characteristics, NN/g, 2020):
- About 100 ms for simple feedback, like a checkbox or a toggle. It "feels immediate" and gives the "illusion of physically manipulating the object".
- 200 to 300 ms for bigger changes on screen, like a dialog coming into view.
- Most animations between 100 and 400 ms, with 400 ms "a very slow animation", only for big moves across large screens.
- At 500 ms, animations "start to feel like a real drag".
And the rule of thumb under all of it: look for the shortest time that isn't jarring, because "it is far more common for animations to be too long than too short".
2. Where 100 ms comes from
The numbers aren't taste. They come from how fast people perceive cause and effect. Jakob Nielsen's response-time limits, first published in 1993 and based on earlier work by Miller (1968) and by Card, Robertson and Mackinlay (CHI 1991), say:
- 0.1 second is about the limit for feeling that the system reacts instantly, that you're directly manipulating the object.
- 1 second is about the limit for your flow of thought to stay uninterrupted, even though you notice the delay.
- 10 seconds is about the limit for keeping attention on the task (Jakob Nielsen, Response Times: The 3 Important Limits, NN/g, 1993).
So feedback should start inside the first 100 ms, and a transition should be long gone well before 1 second. Everything in the ladder that matters lives between those two lines.
3. Three things that change the number
1. Size and distance. The further something travels, or the more of the screen it changes, the longer it needs to stay readable. A tooltip moving 4 px needs far less than a sheet crossing half the screen. NN/g puts it the same way: duration depends "on complexity and on how far the element is traveling" (Laubheimer, NN/g, 2020).
2. Frequency. The more often people meet it, the shorter it should be (When not to animate). A menu that opens fifty times a day gets the short end of its range.
3. Arriving or leaving. Things that enter need a little more time than things that exit: NN/g's example is a popup that takes 300 ms to appear and only 200 or 250 ms to disappear (Laubheimer, NN/g, 2020). An arrival has to be seen and understood. An exit only has to get out of the way.
ease-out, 200 ms out with ease-inIn CSS, the trick is to put the exit timing on the closed state and the entry timing on the open state. The transition uses the timing of the state it's going to. These are the exact rules the sheet above runs on:
.mo-a-sheet { transform: translateY(100%); transition: transform 200ms ease-in; }
.mo-a-demo:has(.mo-a-go:checked) .mo-a-sheet { transform: none; transition: transform 300ms ease-out; }
4. Durations in a design system
Design systems give durations names, so a team picks from a short list instead of inventing numbers. Material Design 3 has sixteen duration tokens, in four groups of four (Material Design 3, Easing and duration; values from the Material Web tokens):
| Group | Tokens | Values |
|---|---|---|
| Short | short1 to short4 |
50, 100, 150, 200 ms |
| Medium | medium1 to medium4 |
250, 300, 350, 400 ms |
| Long | long1 to long4 |
450, 500, 550, 600 ms |
| Extra long | extra-long1 to extra-long4 |
700, 800, 900, 1000 ms |
A system offers the whole range, but a product doesn't need all sixteen. Most teams do well with three or four: one for feedback (about 100 ms), one for small moves (about 200 ms), one for big ones (about 300 ms), and maybe one for full-screen transitions. Step 7 builds that set, in Motion tokens.
Write durations in milliseconds, not frames. Frames change with the device's refresh rate; milliseconds don't. NN/g asks for "durations (in milliseconds, not frames)" in every motion spec (Laubheimer, NN/g, 2020).
5. The code behind the ladder
The ladder is one rule and five overrides. This is the real CSS:
.mo-a-dot { transition: transform 300ms ease-out; }
.mo-a-d100 .mo-a-dot { transition-duration: 100ms; }
.mo-a-d200 .mo-a-dot { transition-duration: 200ms; }
.mo-a-d300 .mo-a-dot { transition-duration: 300ms; }
.mo-a-d500 .mo-a-dot { transition-duration: 500ms; }
.mo-a-d1000 .mo-a-dot { transition-duration: 1000ms; }
With reduced motion on, the dots stop animating altogether, because a demo of speed has nothing to show without movement:
@media (prefers-reduced-motion: reduce) {
.mo-a-demo .mo-a-dot, .mo-a-demo .mo-a-burger i, .mo-a-demo .mo-a-box::after { transition: none; }
}
6. Common mistakes
- Setting durations so they look good in a review, where you watch each one once.
- One duration for everything, so small things feel slow and big things feel rushed.
- Exits as slow as entrances.
- Specifying in frames, or "fast" and "slow", instead of milliseconds.
- Fixing a slow-feeling animation by changing only the easing, when the duration is the problem.
7. Vocabulary
| Term | Meaning |
|---|---|
| Duration | How long an animation lasts, from start to end, in milliseconds |
| Delay | Time before an animation starts |
| Response time | Time between an action and the system's reaction |
| Entry and exit | Motion of something arriving on screen, or leaving it |
| Duration token | A named duration in a design system, like medium2 = 300 ms |
8. Try it (no tools needed, or your phone)
- Tap a toggle in your phone's settings, then open a sheet or a dialog in any app.
- Record both with your phone's screen recorder and count the frames each one takes, as in Audit the motion in your product. At 60 frames per second, 6 frames is 100 ms and 18 frames is 300 ms.
- Did any of them run past 400 ms?
Reflection questions: Which one felt instant, and which one felt like it was showing you something? Did anything leave as slowly as it arrived?
9. If you already practise
- Shave 50 ms off your most frequent animation and see if anyone notices. Usually no one does, except that the product feels quicker.
- Set exit durations to about two thirds of entry durations as a default, and adjust from there.
- Map every duration in your product to a token. Durations that don't fit any token are either special cases worth naming or mistakes.
Checklist
Learn more
- Page Laubheimer, Executing UX Animations: Duration and Motion Characteristics (NN/g, 2020)
- Jakob Nielsen, Response Times: The 3 Important Limits (NN/g, 1993)
- Stuart Card, George Robertson and Jock Mackinlay, The information visualizer, an information workspace (CHI 1991)
- Material Design 3, Easing and duration · Material Web motion tokens
- MDN, transition-duration
Books, courses and videos to go deeper
- Designing Interface AnimationVal HeadBook · Rosenfeld Media, 2016 (Amazon)
- The Animator's Survival KitRichard WilliamsBook · Faber & Faber, 2001 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Easing curves · When not to animate · Motion tokens · CSS transitions and animations · Motion performance · Duration scale