Figma brings video and deeper AI to the canvas
Figma is rolling out video playback directly on the design canvas and reintroduced Weave to add node-based AI workflows for images, video and 3D so designers can move mockups closer to final assets. That means you can keep review and iteration inside Figma while using on-canvas AI agents and image tools in FigJam, Slides and Buzz to produce and edit assets without switching apps. These features are arriving this week and are promoted as ways to keep designers focused and in control of AI-driven production. (x.com) (x.com)
Figma is turning its design file into a place where video can play, pause, go full screen, change speed, and keep sound controls right on the canvas instead of forcing teams to export a clip or open another app. Figma added those controls to Figma Design and Figma Draw on April 7, 2026, after already offering similar playback in FigJam and Figma Slides. (figma.com) That sounds small until you remember what a Figma file usually is: a flat mockup full of rectangles, images, and comments that only pretends to be a finished product. If the thing you are designing includes motion, a static frame is like reviewing a movie by looking at one screenshot. (figma.com) Figma’s own engineers described the problem while building playback for Figma Buzz: users needed to move around the canvas, compare multiple assets, and keep a video playing even after deselecting its frame. That is a very different job from dropping a video into a slide deck, because the designer is inspecting motion while still editing the layout around it. (figma.com) The second piece of this launch is Weave, which Figma introduced after acquiring Weavy in late 2025 and rebranding it as Figma Weave. Figma said at the time that Weave would bring image, video, animation, motion design, and visual effects generation and editing into the Figma platform. (figma.com) Weave works like a patch bay in a recording studio: one box generates an image, another changes the lighting, another turns that result into motion, and the whole chain stays visible on a canvas. Figma’s help documentation says the system combines multiple artificial intelligence models with editing tools so each step is documented and reproducible instead of disappearing into a chat log. (figma.com) That matters because the old workflow for a campaign mockup could bounce between a chatbot, an image generator, a video tool, and Photoshop before anything came back to the design file. Figma Weave’s pitch is that the prompt, the edits, and the final asset can live in one place, with reusable workflow templates published through Figma Community. (figma.com 1) (figma.com 2) Figma has been widening that “one place” idea for months. On March 24, 2026, it opened the canvas to artificial intelligence agents that can design directly in Figma and use “skills” that carry a team’s context and design intent. (figma.com) It also pushed further into developer handoff, with a Claude Code integration that can capture a working interface from a browser and convert it into editable frames on the Figma canvas. Figma’s description of that tool draws a sharp line: code is good at converging on one working state, while the canvas is good at showing the whole experience and all its branches at once. (figma.com) Put those pieces together and the strategy is clearer: Figma does not just want to be the place where teams sketch a screen before the real work starts. It wants the mockup, the moving asset, the artificial intelligence workflow, and even parts of the coded product to stay inside the same browser tab. (figma.com 1) (figma.com 2) The risk is that every extra feature makes the canvas busier, which is exactly why Figma keeps framing these tools around visible controls and editable steps. Video playback is rolling out this week in Design and Draw, and Weave’s public materials keep repeating the same promise: generation is faster when the designer can still see every lever. (figma.com 1) (figma.com 2)
