Figma Builds Animation Into the Canvas With Motion

At its Config conference in San Francisco this week, Figma launched Motion, a timeline-based animation tool built directly into the design canvas. It began rolling out on June 24 in open beta, and it is available on every plan, free accounts included, according to the company's Config 2026 recap.

Until now, adding real motion to a Figma design usually meant one of two things. You exported the work to a separate animation tool, or you described the intended behaviour to an engineer and hoped it survived the handoff. Motion folds that step back into the place where the design already lives. Designers get a proper animation timeline with keyframes, easing presets, bezier curves, and spring physics, and the results sit alongside the static layers they already work with.

The AI part

The feature that will draw the most attention is agent-generated motion. A designer can describe the animation they want in plain language and have Figma propose the keyframes, rather than building every transition by hand. It is the same pattern showing up across creative software this year, where the tool drafts a first version and the human edits rather than starts from a blank canvas. We saw a similar move when xAI added native audio to Grok Imagine earlier this month.

Practical details matter here, and Figma has covered the obvious ones. Motion works with existing design systems, supports Dev Mode for handoff, and exports to CSS, JSON, React, MP4, GIF, WebM, and animated SVG. That export list is the tell. Figma is positioning Motion not as a toy for mockups but as something that produces assets a team can actually ship.

Why it lands now

Animation has long been the awkward gap between a polished static design and a finished interface. Coverage from CMSWire and others framed Motion as part of a wider Config push to close the distance between design and code, alongside new code layers and shader tools. Whether designers adopt it depends on the small things, how predictable the spring physics feel and how clean the exported code is. Those are the details that decide if a tool becomes part of the daily workflow or stays a demo. For now, it is in everyone's hands to try.