
- 650K → 1M · Figma plugin users, up 54%
- 2.07 → 3.18 · Animations saved per user, up 54%
- 20,000 → under 50 · Monthly render failures, down 99.7%
- 0 → 20% · Share of all exports that use Figma Motion
A plugin for making motion inside Figma
LottieFiles for Figma turns designs made in Figma into Lottie animations that ship in real products. I owned the plugin's whole motion creation experience, and grew it from a tool for finding and exporting assets into a creative tool for making motion and catching problems right inside Figma.
I designed the plugin's UX end to end, including new Lottie specs, Figma integrations, and the links out to the dashboard and Lottie Creator. Since 2026 I have also been contributing to the product in code.
Designers were already drawing motion with frames
In 2024, Figma users were already expressing motion with multiple frames and prototype connections. But production-ready motion meant learning keyframes from scratch in a separate tool like After Effects. For most designers, that wall was too high.
The LottieFiles plugin was loved because it removed that wall. It read the changes across selected frames, generated motion and exported it as Lottie, so people could build an animation the way they build a prototype flow. I wanted to keep that way of working and extend the plugin so that Figma alone could produce Lottie animations good enough to ship in a real product.
The obstacle: 20,000 render failures a month

Looking closer, many users were failing to convert their designs. As they edited freely, layer hierarchies drifted between frames, or Figma features Lottie didn't support crept in. Users were hitting more than 20,000 unexplained failure screens every month.
To learn exactly when rendering failed, I collected recurring cases across dozens of online and in-person community sessions and enterprise onboardings. Then I asked the team two questions.
- Can we make exports succeed more reliably?
- If a failure is inevitable, can we at least explain it clearly?
The goal was not to hide errors. It was to cut unexplained failures and turn most errors into problems users could fix themselves.
Turning failures into guidance
With the engineers, I reviewed what was technically possible and wrote the checks into a spec with samples. The checks covered layer structure and also Figma effects Lottie doesn't support, such as inner shadows. Wherever a partial render was possible, a warning banner showed the issue so users could fix it themselves.
Feature checker release notesWidening what can render: new features, one click away

Once failures turned into guidance, the next step was widening what could move to Lottie at all. As Lottie and Figma gained Figma Motion, interactions, variables, themes and components, I folded each one into the flow people already knew instead of adding a button.
When Figma announced Figma Motion, LottieFiles quickly followed with support, and Figma Motion now accounts for 20% of all exports, alongside motion presets, prototypes and other methods. Anything that couldn't move to Lottie was flagged right away by the feature checker, with a jump to the layer to fix. As support grew, users never had to relearn the plugin.
Where it stands: under 50 failures, 1 million users
Right after the feature checker shipped in December 2025, failures fell steadily, and the monthly average has stayed under 50 since. Now, when a file has unsupported features or layer mismatches, users get guidance on what to fix instead of an unexplained failure screen.
Designs made in Figma now become production-ready animations through the plugin. Over my time on the plugin, from 2024 to now, it grew from 650,000 to 1 million users, and saves per user rose from 2.07 to 3.18.
