Keyframery's motion is written with modern CSS: linear() easings, @starting-style, anchor positioning and sibling-index(). Here is what each move relies on.
Part of Keyframery, the open-source animated components for UI SDK
Keyframery has no JavaScript animation engine. The motion is modern CSS, so what you see depends on what the browser supports.
Tested in Chrome
Keyframery is developed and tested in current Chrome. Other browsers have not been tested component by component yet. UI SDK's behaviour (keyboard, focus, opening and closing) does not depend on any of the CSS below, but check the components you use in the browsers you support before you ship.
What the moves rely on
| CSS feature | Used for |
|---|---|
linear() easing | Every spring and pop |
@property | Stretch (tabs, segmented control, navigation menu), animated star fills |
@starting-style | Entrances, drawn checks |
| Anchor positioning | Glide: the single highlight in menus, lists, radios, toolbars and calendars |
sibling-index() | Cascade: the delay between rows |
Individual transforms (translate, scale, rotate) | Most moves |
The links go to MDN, which lists current browser support for each feature.
Framework support
React 19 and Tailwind CSS v4 are required. Next.js, Vite and React Router are covered in Installation.
Accessibility
Keyframery keeps UI SDK's keyboard, focus and screen-reader behaviour intact, and stops moving when reduced motion is on.
Troubleshooting
Fixes for what most often goes wrong: an unknown registry, a serif font after shadcn init, Next.js stopping on Date.now(), and motion that doesn't play.