Exit animations never actually play
The child was removed in the same render as the AnimatePresence update, or the key was reused, so the exit transition is cancelled before the browser paints a single frame.
Exits run end to end
Animating with Framer Motion?
Framer Motion makes animation easy right up to the point where a layout animation snaps between routes, AnimatePresence refuses to run the exit, or a page that respected reduced motion yesterday ignores it today. The library is powerful and does a lot behind the scenes, which is why the fix usually lives in the parent component, the keys, or the CSS, not where the symptom shows up. We work the stack until each transition does what the designer meant.
What it is
Framer Motion is the production animation library for React, maintained by the team behind the Framer design tool. It provides a motion primitive, layout animations, variants, gestures, drag, scroll-linked animation, and AnimatePresence for mount and unmount transitions, all with a declarative API that fits into the React component model.
By 2026 it is the default choice when a React app needs more than CSS transitions. The library has evolved to handle server components, reduced-motion preferences, and interoperability with the native View Transitions API, while keeping the original mental model of motion elements and animate props intact.
The honest version
No technology is all upside. This is where Framer Motion earns its place and where it tends to cause trouble.
Sound familiar?
The Framer Motion problems that bring people to us, and what you have once each one is fixed.
The child was removed in the same render as the AnimatePresence update, or the key was reused, so the exit transition is cancelled before the browser paints a single frame.
Exits run end to end
Two motion components with the same layoutId mounted at once, so the library animates between them and users see a thumbnail fly to a sibling instead of the hero image.
LayoutIds unique per transition
Height or width going to auto is not interpolable, so the animation snaps. The fix is usually a measured value or a layout animation that handles the transition for you.
Values interpolate smoothly
A variant animates regardless of prefers-reduced-motion because the hook was not used or the variant does not have a reduced counterpart. Users who set the system preference see motion anyway.
Reduced motion honored across the app
An initial prop computed from window, or a motion component rendered in a server boundary without a client wrapper. React tears the HTML apart and re-renders, which users see as a flicker.
Server and client agree on first paint
A gesture that unmounts its own constraint ref mid drag, usually because the parent list re-ordered items while the drag was still in flight.
Drag survives parent renders
A route transition where the new page animates in on the initial render, flashing all the motion children. The initial={false} prop or a ref gate controls when mount transitions are allowed.
Only intended mounts animate
A value interpolation that divided by zero, or a motion value hooked up to a state that briefly went undefined. The browser reports a transform error and the element flashes at its origin.
Motion values guarded against NaN
What we do
Call us for one broken exit animation, or hand us the entire motion layer.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Usually a layout animation triggered on an element whose parent re-rendered, a motion component with position static, or two components sharing a layoutId by accident. The devtools help, but the fix is almost always a parent-level change rather than tuning the animation prop.
Three common causes: children without a unique key, a mode mismatch where popLayout was expected but wait was set, or the child unmounting from the tree in the same render as the parent condition flip. Fix any one and the exit usually comes back.
Import the m component instead of motion, feed features through LazyMotion, and consider CSS transitions for one-off interactions. The library is fine on an app-wide scale; the problem is usually a marketing page importing the full motion object for one fade in.
Partially. It sets transition durations to zero when the preference is on, but variants that do big transforms, parallax effects or drag feedback still need an explicit guard with useReducedMotion. We audit for that case specifically because it is the most common accessibility regression.
Yes, but every motion component must live inside a client boundary. The usual pattern is a thin client wrapper that re-exports motion primitives, which keeps the server tree clean and prevents hydration mismatches from motion props.
The initial look is free. Share the animation that is misbehaving, point us at the design intent, and we return a price before any work gets started.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: