Motion makes an interface feel responsive when it explains what changed — a button that reacts to hover, a panel that slides in from where it was opened, a skeleton screen that shows content is on its way. The animation tools here let you design that motion visually and copy pure CSS, with no JavaScript animation library required.

Build keyframe animations on a timeline with the Animation Generator and Keyframe Builder, or create simple state changes with the Transition Generator. Shape the feel of any motion with the Cubic Bezier editor. Ready-made generators cover the most common needs: hover effects for buttons, cards and images; loading spinners; skeleton loaders; animated text effects; and scroll-triggered reveals with the IntersectionObserver code included.

Guide

Rules for smooth, accessible animation

1

Animate transform and opacity where possible — they run on the compositor and avoid layout recalculation.

2

Keep UI transitions short: 150–300ms for hovers and toggles, up to about 500ms for larger panels.

3

Use ease-out for elements entering the screen and ease-in for elements leaving it.

4

Wrap non-essential motion in @media (prefers-reduced-motion: no-preference) to respect user settings.

5

Avoid animating width, height, top or left on large elements; use transform: scale() or translate() instead.

FAQ

Frequently asked questions

What is the difference between a transition and an animation?

A transition runs once when a property changes between two states, such as on hover. A keyframe animation can have many steps, loop, run automatically and play in reverse.

Why does my CSS animation look janky?

Animating properties that trigger layout (width, height, margin, top) forces the browser to recalculate the page every frame. Switching to transform and opacity usually fixes it.

How do I respect users who prefer less motion?

Use the prefers-reduced-motion media query to disable or simplify animations. Operating systems expose this as an accessibility setting.