How long should a UI animation take?
Most UI animations should last 100 to 500 ms. Durations for feedback, modals and page changes, when to use ease-out, and what I use on this site.
· Updated · 3 min read

Most UI animations should last between 100 and 500 milliseconds. Small feedback, such as a toggle or a checkbox, needs about 100 ms. A larger change, such as a modal or a screen change, fits 200 to 300 ms. Past about 500 ms, an animation starts to feel like a delay.
The numbers come from the Nielsen Norman Group's article on animation duration. Below I add the easing advice from the same article, a few rules for different cases, and the values I use on this site.
Durations by type#
| What animates | Duration | Note |
|---|---|---|
| Most UI animation | 100 to 500 ms | The article's general range |
| Simple feedback (checkbox, toggle) | about 100 ms | The result should feel instant |
| A substantial change (modal, screen) | 200 to 300 ms | The article's suggestion for a bigger change |
| Large movement across a big screen | up to 400 ms | 400 ms is slow, so keep it for big moves |
| Upper limit | about 500 ms | Beyond that, "animations start to feel like a real drag" |
The article (from 2020) adds a warning: it is far more common for animations to be too long than too short.
Rules that change the number#
- Distance. The further an element travels, the longer it needs, and the smoother it has to be.
- Enter and exit. Things that appear usually need a slightly longer duration than things that disappear. A popup could take 300 ms to appear and 200 to 250 ms to go.
- Frequency. The more often an animation plays, the shorter and subtler it should be. A hover effect that you see many times a session should be short.
- Test small changes. Moving from 250 to 300 ms can feel very different.
Easing#
The same article says completely linear motion looks unnatural.
- Use ease-out for most animations. It starts quickly and slows down, which lets the eye predict where the element will stop.
- Ease-in is sometimes used for exits, so that the object speeds up as it leaves.
- Be careful with ease-in and ease-in-out, because a slow start can feel unresponsive.
In CSS that means ease-out or a custom curve. If you want a curve between the keywords, an editor such as my Easing Editor lets you drag a cubic-bezier and see it on four lanes at once. For springs and bounces, see CSS spring and bounce with linear().
What I use on this site#
These are my own choices, not a recommendation from the article:
| Where | Value |
|---|---|
| Small UI changes (hover, colour) | 200 ms |
| Larger UI changes | 400 ms |
| A section revealing on load | 800 ms |
| Page exit | 300 ms |
| Page entrance | 620 ms, starting 220 ms in |
| Hover intent before an ad expands (in a demo) | about half a second |
| Lab card poster zoom on hover | 900 ms |
The page entrance, the reveal and the card zoom are longer than the 500 ms limit. That is a trade-off I chose for a portfolio, where the motion is part of what I am showing. For a tool or a form, I would stay inside the limit. Every one of them has a reduced-motion path.
Reduced motion#
The article says to respect users who have set their browser or device to reduce motion, by removing animations. The CSS media query is prefers-reduced-motion: reduce, and MDN notes that scaling and panning large objects can trigger discomfort for people with vestibular disorders. On this site, reduced motion turns the page transition into a 180 ms fade.
A note on testing#
I did not test these durations with users. The numbers are guidelines from one source, and the Nielsen Norman Group says to test. Its page does not give separate values for desktop, mobile or wearables.