Figma Release Notes

UPDATE

FIGMA

DESIGN

WEBSITES

You can now bring your websites onto the canvas as structured layers with the Figma Chrome extension. Copy the full page or selected elements, then paste into Figma to reference and riff on, no coding agent needed. The ability to generate designs using your design system is coming soon.

To get started, install the extension and sign in with your Figma account. This feature is currently in beta and available only on paid plans.

Learn more in the help center.

NEW RELEASE

FIGMA

DESIGN

DESIGN SYSTEMS

Check designs compares your designs against your design system, flags what's off, and suggests the correct fix in one click. Catch drift as you work, run a QA pass before handoff, and keep every file aligned to your design system with:

• Variable and style suggestions flags hard-coded color, text, radius, and spacing values and replaces them with the correct design system token.
• Accessibility suggestions flags color contrast violations and replaces them with WCAG 2.0 AA or AAA-compliant colors.
• Library mismatch detection flags tokens and components from unsubscribed libraries.
• Detached component detection flags components detached from their source library.

Check designs is available on Organization and Enterprise plans.

Learn more in the help center.

NEW RELEASE

FIGMA MAKE

PROTOTYPING

Plan mode

Plan mode is a new opt-in mode that helps you shape that direction before generation starts. Make takes a look at your project, asks a few clarifying questions, and drafts a plan you can edit, refine, and approve before anything gets built.

It's most useful for complex work—multi-section layouts, detailed specs, design imports—where getting aligned upfront leads to noticeably better results. For simpler prompts, you can skip it and build directly.

Turn it on via the dropdown in the prompt box or the /plan command. Because plan mode does extra work upfront, it uses more AI credits than a standard build—you'll see an estimate before you commit. Learn how AI credits work.

Web search & fetch

Make can now pull live context from the web mid-build. Search broadly or fetch a specific URL to ground builds in current content. Tool-call approvals let you review before anything enters your session. Learn more about building with live context.

Queued messages

Stack follow-up instructions while Make is still generating. Edit or delete them before they commit, and they'll send automatically once the current build finishes. Learn more about prompting in Make.

Learn more about Make updates in the help center.

From visual editing to contextual prompting and collaboration, Figma Make is expanding how teams can design with code.

Share Figma Make, now on your local code

Make note

These new Make features will be rolling out in beta over the coming weeks.

Today we're launching new capabilities in Figma Make—the ability to work in your production codebase without leaving Figma. In our Beta desktop app, you’ll find our first step toward bringing together freeform design, prototyping with code, and shipping to production.

Here at Figma, we don't believe you should be forced to choose between a design or code tool. You should be free to use the best tool for what's needed, whether it’s the design canvas, a prototyping playground, or production code.

Working in code today feels a lot like design did ten years ago. When Figma launched, design was offline and single-player. Today, more people are using agents to write code than ever and coding itself is changing rapidly. The quality of code output from frontier models is getting better all the time, and yet, despite so much innovation, the tools we have to work with code are very early. We're still stuck in 2016 when it comes to collaboration. IDE's and terminals just don't feel like "home" for many of us. We feel this every day and we hear it constantly from the Figma community.

“Design vs code” is a false dichotomy. Tools should not limit the ability to move between these worlds. The whole point of Figma as a platform is to give you access to the right tool at the right moment. From direct editing and contextual prompting to closer collaboration and file sharing, here's what's launching today to make that possible.

Edit your codebase visually

Make note

While we’ve made this setup process easier for non-technical users, we're working to make this process far smoother. For now, designers who already have access to their company’s codebase are best suited for this new Make functionality.

You can now make direct, visual edits and ship changes from Make by connecting to your codebase. Select elements, adjust properties, change layouts, colors, fonts, or sizing—the agent finds the relevant code and edits it so the UI reflects what you designed. This is precise editing in code with freedom to explore.

Use direct edits for changes you know you want to make.

For changes that go beyond properties—an interaction or animation—you can annotate elements on the screen, describing what you want. Annotations give the agent contextual information, and can reference many elements at once. This adds a flexible option between direct editing and standard prompting.

Use annotations for changes that alter interaction logic.

Branch, commit, and ship

Shipping production code should happen intentionally, through your team's development process. Until you open a PR, your changes are stored as local commits.

Make supports Git workflows for codebases—creating branches, reverting commits, and other operations—so your engineering team reviews your changes like any other pull request.

Create a branch directly in Make.

Preview your commit history for version control in Make.

Collaborate and build

When Make edits your local codebase those changes can be shared as files. Send a link, and once your teammate has access to your branch, they can check out your branch, see your changes, and start to build from there. You’ll see their changes and ideas, and the commit history helps you compare the before and after.

Copy screens, pages, and components from Make and paste them into the Figma canvas as layers, where you can riff and edit with your team and Figma's agent. Figma detects those changes and prompts you to bring them back into Make, applying them in code.

From Make to Figma Design, and back.

The goal is to close the loop entirely—bring screens and elements from Make into Figma Design for your team to comment on, edit, and riff on, then bring those decisions back into code. The canvas and the codebase, in the same place. There's no right place to start. There's just the work, and the best tool for where you are in it.

Figma Make's new capabilities—including direct editing, annotations, chat, and PR creation—launch in a limited beta on May 28, 2026 and won’t consume credits during beta. We expect to announce AI credits pricing in the near future. Sign up here to request early access. If you’re eligible and selected for the beta, we’ll send you an email once you’re in. Joining the waitlist doesn’t guarantee access. This beta will only be available in our Beta desktop app for Mac users. We plan to bring these changes to other platforms soon. To learn more about these features visit our help center.

NEW RELEASE

FIGMA MAKE

AI

DESKTOP APP

DESIGN

DEVELOPMENT

Connect Make to your local codebase, and from there prompt contextually on specific elements, adjust properties through a Figma editing panel, or describe changes in chat — and an AI coding agent makes the corresponding code edits. When the result looks right, you can commit the changes and open a pull request without touching a terminal.

Key features available at closed beta launch:

• Direct editing of your product — annotate elements, adjust spacing, swap components on the live interface
• Chat-driven edits — describe changes in natural language, the agent handles the code
• Figma MCP integration — paste a frame URL or component link, the agent builds with your real design system
• Branch and PR workflow — commit and open a PR from inside Make, no terminal required
• GitHub native support — natively integrated in the UI, other Git providers can be connected via SSH
• Simple setup — Make will install dependencies, set up a dev server, and help you start making changes to your product

To get access, join the waitlist at figma.com/join-waitlist-make/.

See how Figma Make brings your codebase into Figma—and your design decisions into production.

NEW RELEASE

UPDATE

FIGMA

DESIGN

ASSETS

WEBSITES

Grid is generally available and now makes it easier to reorder columns and rows, auto-position items into empty cells, and auto-add or remove rows to fit so you spend less time on manual fixes.

• Drag to reorder columns and rows — Drag column and row tracks directly into a new position.
• Automatic positioning — Content automatically shifts to fill gaps when items are deleted.
• Automatic rows — Rows are automatically created or removed as you add or delete content.

Learn more in the help center.

Starting today, work with an agent that is built for Figma—directly on the canvas.

Designers need purpose-built tools that serve the essentials: exploration, experimentation, collaboration, and precision. Figma was built as a multiplayer canvas to make all of that possible. As teams adopt agentic tools to build products more quickly, false choices are emerging: Speed or precision? AI generation or direct manipulation? You shouldn't have to choose.

Earlier this year, we opened the Figma canvas to third-party agents so you could bring design system knowledge into your agentic workflows. Now we're going further, with a Figma agent available directly on the canvas and in the left rail.

That's why we built the Figma agent. Our goal was to create an agent fluent in Figma and native to the way teams work. That meant making Figma itself legible to a model in ways that aren't possible with third-party tools—with deep context on your components, tokens, standards, and best practices.

How do Figma's agent and MCP server work together?

Use Figma's agent when you're working on the canvas—it's built in and has additional context about your design system. Use the MCP server and use_figma to pull code onto the canvas or push designs back to code.

The result is a dedicated design agent that works beside you on the canvas, inside the same file as your team—as a true collaborator. It's fine-tuned for editing Figma files, so outputs are tailored to your design context and built for direct manipulation so you can stay in control. Unlike the MCP server, the agent lives directly on the canvas—no separate setup or context switching, so you can easily:

• Start a prompt from any design layer
• Parallel prompt to play out multiple ideas at once
• Make edits and iterate while the agent iterates, too

From exploring new directions to making bulk edits and implementing feedback, here's how Figma's agent will fit into your design workflow today.

Explore more directions

The best designs rarely come from the first idea—or the first prompt. Exploring directions, comparing approaches, and iterating is already core to how designers work. Our agent will help you cover more ground in less time.

How do Figma Make and the Figma agent fit into your workflow?

You can start in Figma Design with our agent to generate design layers to clarify intent across flows, states, copy, and structure. Then, send it to Make to generate code layers to clarify behavior. Then, embed it back in Figma Design.
Or, start in Figma Make, copy frames to Figma Design, iterate with our agent, and send it back to Make.

You can go wide: Quickly generate distinct stylistic approaches to the same problem and explore many directions at once. Compare multiple checkout flows optimized for different business goals. Ask the agent for three different information architectures.

Or go deep: Pick a direction and ask the agent to iterate, compare implementations, and rethink existing designs while staying aligned with your design system. The agent uses your most frequently and recently used components as a starting point, but you can also guide the outputs by choosing a specific library and @ mentioning specific tokens, variables, and components to steer it toward exactly what you need. Think of it as a key command for your design system.

As AI makes it easier to generate designs, the risk is shipping something average. Our agent is purpose-built to help you explore more directions, so you can choose the right one—then once you have, going hands-on is often faster, more natural, and token efficient than prompting your way to the ideal output. You can also build simultaneously with your team in the same workspace, without losing context.

Remix styles and generate screens that use your design systems:

Automate busywork

Flow doesn't have to stop at the canvas:
With the Figma MCP server work can move between code and Figma without losing fidelity. Start in code, bring it into Figma with our code-to-canvas capability to iterate or apply your design system, then send it back via the Figma MCP server—and everything stays in sync. Our agent fits into that handoff, helping maintain momentum as work moves between tools.

When Figma's agent works alongside you on the canvas, you don't just work faster—you can shift easily between AI assistance and hands-on manipulation. This makes it easy to work through tedious tasks that still require context and precision. Wouldn't it be great if you didn't have to manually rename variables for consistency, swap the same component across many different screens, repeat a padding change across an entire flow, or populate a large number of frames with realistic content? That's exactly what the agent is for. It handles the work that usually slows you down by automating bulk edits, applying design systems, and filling designs with realistic content at scale.

Chat with Figma to update typography across a file, replace lorem ipsum copy and imagery across a grid, set all chip components to their active state, or convert your screens to dark mode without manually adjusting fills and contrast. And if you maintain a design system, the agent is a particularly powerful ally. Use it to bulk-update descriptions, tags, and use cases across libraries, standardize naming conventions, document components with all their states and variants, and steer quality by sharing examples of your team's work.

Make precise edits in bulk and document your design system:

Do more with feedback

Design work accumulates feedback that's often scattered across comments and files: from crit notes and stakeholder reactions to open questions. Our agent helps you put that feedback to work.

Because your whole team works in the same file, the agent already has that context—so asking it to work through feedback feels less like briefing a new collaborator and more like thinking out loud with someone who’s already in the room.

Ask Figma to summarize feedback, identify themes, and turn input into next steps. You can also use it to pressure-test designs from different points of view. Wondering how a VP focused on revenue will react? Our agent can model that perspective. Working through a long comment thread? The agent can distill the back-and-forth into an actionable plan. Need to think out loud before a crit? Use our agent to sharpen your direction before sharing it with your team.

Receive, organize, and apply feedback in real time:

Figma's agent is embedded where the work already happens. There's no toggle tax, no context switching, no learning curve. You stay in Figma and your team stays in the loop. We built this with one goal: to help you work faster without compromising on quality and craft.

In the coming months, we'll focus on improving support for design systems, refining the user experience, expanding the agent's ability to search across your files, and adding ways to customize. We’re just getting started.

The Figma agent is rolling out gradually in beta over the coming weeks. During beta, the agent won't consume credits. AI credits will apply at general availability. Sign up here to request early access. If you’re eligible and selected for the beta, we’ll send you an email once you’re in. Joining the list does not guarantee access. The agent will be available for Full seat users on Professional, Organization, and Enterprise plans. Collab and Dev seats can use the agent in drafts. Starter, Education, and Government plans are not included. Learn more in our help center.

Figma's purpose-built agent is embedded where design already happens. It generates and remixes designs, automates rote work, and respects your design systems out of the box.

The Figma agent is rolling out gradually in beta over the coming weeks. During beta, the agent won't consume credits. AI credits will apply at general availability. Sign up here (figma.com/join-waitlist) to request early access. If you’re eligible and selected for the beta, we’ll send you an email once you’re in. Joining the list does not guarantee access. The agent will be available for Full seat users on Professional, Organization, and Enterprise plans. Collab and Dev seats can use the agent in drafts. Starter, Education, and Government plans are not included.

From exploring new directions to making bulk edits and implementing feedback, learn how Figma's agent fits into your design workflow. Or learn more in the help center.

NEW RELEASE

FIGMA MAKE

Skills are markdown files that outline the conventions and workflows you use repeatedly, so you get prototypes that match your standards with fewer prompts. Import existing skills or create one in Make, then call it with a slash command in any prompt.

Use a skill to bring in context you want reusable across all your Make files, like /insert-sample-data for dropping in company-approved test data. Or use one to run a repeated workflow the same way every time, like /build-from-prd paired with a Notion or Confluence connector to turn any PRD into a prototype that meets your standards.

Today, each person creates and manages their own skills. You'll soon be able to publish and share skills across your team and organization.

Learn more about custom skills in Make.