Figma Motion adds physics-based springs: what designers should know
Figma Motion now has physics-based springs, style previews and Lottie export previews. Here is what changed and how to use it in real product work.

On November 10, Figma shipped another round of updates to Figma Motion, its animation tool that is still in open beta. The headline feature is physics-based springs: you can now set mass, stiffness and damping instead of picking a duration and an easing curve. The same update added previews for animation styles and a way to check how an animation will play as a Lottie file before you export it.
On their own, these sound like small additions. Put next to the September and October updates (custom styles, audio, text animation and Lottie export), they change what Motion is good for. It is moving from "a quick way to show an idea" towards "a place where motion decisions can be made, saved and handed off". Here is what changed, what it means in practice, and how we would start using it.
What shipped on November 10
According to Figma's product update post, the release has three parts:
- Physics-based springs. You set mass, stiffness and damping for iOS and Android animations. The duration updates to match the spring you define, and you can save a spring to your design system so it can be reused.
- Style previews. Preset animation styles now play in the animations list and on the canvas before you apply them, so you can compare options without committing to one.
- Lottie export previews. You can see how an animation will play as a Lottie file before exporting it.
Figma has not announced plan details or pricing for Motion alongside these updates, and Motion is still labelled as open beta. Treat it as something to test on real work, not something to build a whole production pipeline on yet.
Why springs matter more than they sound
Most interface animation in Figma prototypes has been defined the web way: a duration in milliseconds and an easing curve. Native mobile platforms often think about motion differently. A spring is described by physical properties, and the animation lasts as long as the physics says it should.
That gap has caused a familiar handoff problem. A designer picks "300ms, ease out", a developer rebuilds it as a spring in code, and the two never quite feel the same. Interruptions are where it shows most: a spring that gets grabbed mid-motion behaves naturally, while a fixed-duration curve can feel stiff or jumpy.
Being able to define the spring itself in Figma means the values you tune by eye are the same kind of values your iOS or Android developer works with. You are no longer translating between two models of motion.
A quick primer on mass, stiffness and damping
If you have not worked with springs before, here is the short version:
- Stiffness controls how strongly the spring pulls towards its end point. Higher stiffness feels snappier and faster.
- Damping controls how quickly the motion settles. Low damping produces bounce and overshoot; high damping settles smoothly with little or no bounce.
- Mass controls how heavy the moving object feels. More mass makes the motion slower and more deliberate.
A practical way to tune: start with no visible bounce, adjust stiffness until the speed feels right, then lower damping only if the element should feel playful. Small UI parts like toggles and chips usually want quick, well-damped springs. Larger surfaces like sheets and cards can take a little more mass.
Saving springs to your design system
The most useful part of this release for teams is that a spring can be saved to the design system. This builds on the custom animation styles Figma announced at the end of September, which let you save easing, duration and other variable-backed properties as a style and publish it to a library.
In practice, that means motion can finally be tokenised the way colour and type already are. A small, named set works better than dozens of one-off values. For example:
- Quick for toggles, checkboxes and small state changes.
- Standard for cards, menus and most transitions.
- Gentle for sheets, modals and large surfaces.
- Playful with a little bounce, used rarely and on purpose.
Figma also says these styles can be applied by the Figma agent and by coding agents connected through MCP or Skills. If your team uses those tools, named motion styles give agents something consistent to reach for instead of guessing values.
What the earlier Motion updates added
The November release sits on top of two earlier rounds that are worth knowing about if you have not opened Motion in a while:
- Custom animation styles that combine several properties into one reusable pattern.
- Audio on the timeline. You can drag an audio file onto a clip, trim, split and position it against keyframes, and export it with the animation as MP4 or WebM.
- Text animation by character, word or line, while the text layer stays editable.
- Lottie and dotLottie export, which the new export previews now make easier to check.
Together, these cover a lot of what people previously moved to a separate animation tool for: short product clips, animated headlines and lightweight Lottie assets for apps and websites.
How to use this on a real project
Here is how we would start without disrupting current work:
- Pick one flow. Choose a single interaction that matters, such as opening a bottom sheet or adding an item to a cart, and animate it in Motion with a spring.
- Tune with your developer. Sit together for twenty minutes and compare the Figma spring with the one in code. Agree on the values and write them down.
- Save the agreed springs as styles. Start with three or four, name them by purpose, and publish them to your library.
- Check Lottie output before you ship it. Use the new export preview to catch anything that does not translate before a developer finds it.
- Keep a fallback. Because Motion is in open beta, keep your current animation workflow available for client deliverables with fixed deadlines.
What to keep an eye on
A few questions are still open. Figma has not published plan availability or pricing for Motion, and beta features can change before general release. Spring values also do not always map one-to-one across platforms and libraries, so test on a real device rather than trusting the preview alone.
Motion values belong in the design system for the same reason colours do: if they live only in someone's head, every screen ends up a little different.
The short version
Physics-based springs bring Figma Motion closer to how native apps actually animate. Combined with saved styles, audio, text animation and Lottie export, it is becoming a realistic place to define and share motion decisions. Try it on one flow, agree on a small set of springs with your developers, and publish them to your library. That alone will make your product's motion more consistent than most.


