Step-by-step guides on prompting, styles, and getting the most out of AI image generation.
Figma has unveiled a sweeping update at its Config 2026 conference that adds AI-generated motion graphics, shader support, a new code layer, and the ability to build custom AI plug-ins — changes that push the design tool well into territory once owned by dedicated animation and development environments.\n\n## Key takeaways\n\n- Figma's Config 2026 update introduces native AI motion graphics and shader tools directly on the canvas, eliminating the need to export to a separate animation app.\n- A new code layer reimagines Figma's canvas as a full-stack development surface, bringing AI agents, design assets, and code into a single workspace.\n- Designers can now create custom AI plug-ins inside Figma to automate repetitive tasks specific to their own workflows.\n- The update is positioned as a direct challenge to tools like Adobe After Effects for motion and to coding environments for front-end development.\n- According to The Verge, Figma framed the changes as helping creatives "push their ideas further" while automating tedious work.\n\n## Motion and shaders land natively in Figma\n\nThe most immediately useful addition for visual creators is native motion support. Previously, designers who wanted to animate Figma assets had to export them and bring them into After Effects, Rive, or another motion tool. The new AI motion graphics feature generates animated sequences directly on the Figma canvas, which means a creator can go from a static design to a looping animation without switching applications.\n\nShader support lands alongside motion, letting designers apply real-time GPU-driven visual effects — the kind of procedural, mathematically generated textures and distortions that have historically required code or a dedicated 3D tool. For AI-art creators who use Figma to composite or present generated images, shaders open up post-processing options that were simply unavailable in the tool before.\n\nNeither feature requires writing code to use, though the new code layer means that developers working alongside designers can now inspect and edit the underlying implementation in the same workspace.\n\n## The code layer and what it actually changes\n\nFigma describes the redesigned canvas as optimized for full-stack development. The code layer surfaces the technical implementation of design elements — components, interactions, animations — alongside the visual design, rather than hiding it behind an export or a handoff step. According to TechCrunch, AI agents are part of this layer too, meaning automated tasks like generating boilerplate, checking component consistency, or wiring up interactions can run inside Figma rather than in a separate coding environment.\n\nFor solo creators who work across design and front-end development, the practical effect is fewer context switches. For teams, it narrows the gap between what a designer produces and what a developer ships.\n\n## Custom AI plug-ins close the automation gap\n\nThe custom AI plug-in capability is the feature with the longest tail. Figma has always had a plug-in ecosystem, but the new system lets users describe a task in natural language and have AI generate a plug-in to handle it — think batch-renaming layers by content type, auto-resizing assets for multiple output formats, or applying a house style to imported AI-generated images.\n\nFor creators who regularly bring AI-generated images into Figma for layout or presentation work, this is a meaningful quality-of-life upgrade. Repetitive preparation tasks — stripping backgrounds, standardizing canvas sizes, organizing layers — are exactly the kind of work that custom plug-ins can absorb. The ability to create those plug-ins without writing JavaScript from scratch lowers the barrier considerably.\n\nIf your pipeline involves generating images with a tool like Charmloop's generator and then compositing them in Figma, the new plug-in system could automate the handoff steps that currently eat time between generation and final layout.\n\n## Where this sits in the broader creative-tool landscape\n\nFigma's move into motion and shaders puts it in more direct competition with Adobe's creative suite — at a moment when Adobe is also rolling out AI assistants across Photoshop, Premiere, and Illustrator. Both companies are racing to collapse the number of tools a creator needs in their stack.\n\nThe Config 2026 announcements don't make Figma a replacement for a dedicated AI image generator or a video production environment. But they do mean that the composition, presentation, and handoff stages of a creative workflow can now stay inside a single application — with AI handling more of the mechanical work at each stage. For creators managing complex visual projects, that consolidation has real value even before any individual feature becomes best-in-class.\n\nFigma has not announced a separate pricing tier for the new AI features; availability details are expected to follow the Config conference period. Check Charmloop's guides for workflow tips as the tools roll out.
