Figma launches Motion with timeline editing and MP4, WebM, GIF export

• Figma shipped figma's Motion launch post as a beta animation tool that keeps design and motion in the same file, while LinusEkenstam's keynote post says the new timeline is collaborative and built directly into the canvas.
• Export is the immediate practical hook: LinusEkenstam's export post says Motion can ship to code, MP4, WebM, and GIF, and LinusEkenstam's code handoff clip shows a design-to-code path from Motion into app code.
• Figma framed Motion as part of a bigger canvas expansion, with zoink's recap grouping code, Weave, shaders, agent-built tools, and animation into one surface.
• Early designer reaction focused on tool consolidation, with tranmautritam's AEUX post saying Motion could replace at least one After Effects bridge, while tranmautritam's Config reaction described the drop as native creative tools landing directly on canvas.
• Motion did not ship alone: figma's Config roundup bundled it with Code Layers, Weave tools, generative plugins, and shader effects, which makes this feel more like a canvas platform expansion than a single feature release.

You can watch the Config 2026 launch video, open the Motion beta page, check Figma's Weave tools beta page, and compare it with the shader effects beta page. One keynote thread even showed LinusEkenstam's code handoff clip jumping from Motion toward generated code, while tranmautritam's plugin post zeroed in on generative plugins for workflow speed.

Figma's core pitch is simple: animation now lives inside the design file. figma's design-and-animate post framed it as designing and animating in the same file, and LinusEkenstam's keynote post added the details creative teams actually care about, a timeline primitive and collaboration.

The interesting part is not that Figma added keyframes. It is that the company chose to make motion a native canvas object instead of another sidecar workflow. zoink's Config framing said the event was about new materials and new tools, and Motion is the clearest example of both ideas landing in one feature.

The export matrix is where Motion stops being a demo. According to LinusEkenstam's export post, animations can go out as code, MP4, WebM, and GIF, with more formats planned.

That creates two very different use cases inside the same tool:

• UI motion that needs to survive handoff into product code, as shown in LinusEkenstam's code handoff clip
• Marketing and launch assets that need rendered media files, as listed by LinusEkenstam's export post

Figma also pushed that second angle hard. figma's launch-film post joked that the entire Motion launch film should be announced as made in Motion, which is a neat way to signal the product is aimed at both interface motion and polished promo work.

Motion landed inside a much larger Config package. zoink's recap said everything announced, code, motion, shaders, and your own tools, now lives together in the canvas, while figma's roundup listed the full set.

The stack Figma showed breaks down into five parts:

• Motion for animation, per zoink's recap
• Code Layers for exploring with code, per zoink's recap and figma's Config roundup
• Weave tools for on-canvas generation, per figma's Weave tools post
• Generative plugins, per figma's Config roundup
• Shader effects and fills, per figma's shader effects post

That bundle is why the keynote felt bigger than a motion-feature ship. zoink's Config framing described the theme as new materials and new tools, and Motion makes more sense when read as one piece of that broader canvas rewrite.

The most useful early reactions were about subtraction. tranmautritam's AEUX post said Motion might remove the need for AEUX, and tranmautritam's Config reaction said tools that used to live across several apps were now native on canvas.

A few patterns showed up fast:

• Motion can absorb common UI animation work that previously left Figma, according to tranmautritam's AEUX post
• The agent can make small jigs and repetitive helpers, according to LinusEkenstam's agent thread clip
• Generative plugins became an immediate workflow target, with tranmautritam's plugin post saying they wanted custom plugins to speed up specific tasks

That is Christmas come early for design-system and prototyping nerds. Not because one tool replaces every specialist app, but because Figma is clearly attacking the annoying seams between layout, motion, code, and repeatable utility work.

Availability was unusually broad across the Config set. figma's Motion beta post said Motion was available now in beta, while figma's Weave tools post and figma's shader effects post each pointed to their own beta pages the same day.

The rollout snapshot from the evidence looks like this:

• Motion: beta now, per figma's Motion beta post
• Weave tools: 20-plus tools in the design canvas, per figma's Weave tools post
• Shader effects and fills: beta now, per figma's shader effects post
• Generative plugins: announced in the Config bundle, per figma's Config roundup

That last point matters because Motion is easier to understand when you see what shipped beside it. Figma did not just add a timeline. It also put animation next to shaders, code surfaces, agent-built utilities, and generative tools in the same workspace.