Figma review 2026: Make, Sites, the design agent, and Anima

Figma in 2026 is the canvas, a prototype, and a publish button. Make and Sites are useful for a clickable draft or a short campaign. They are not the marketing site you run ads on. We still design in Figma and still ship Next.js. Anima is the Figma-to-code tool we open when someone needs to inspect React, not imagine it.

A founder sent a Figma Make URL on a Tuesday and asked if we could “just publish that.”

The page moved. The type was close. The form posted nowhere a person would find it. There was no CMS a marketer could touch on Thursday, no tracking a Monday number could sit with, and no file an agent could cite without inventing the company. It was a good afternoon. It was not a site.

This review is from a studio that opens Figma every week and ships Next.js. We are not a Figma partner. We do not sell Anima seats. Prices below are from figma.com/pricing and animaapp.com/pricing on 15 August 2026. Confirm the monthly versus annual toggle before you buy.

What is Figma in 2026?

Open the pricing page. Design is one row. Make, Draw, Dev Mode, FigJam, Slides, Motion, Sites, and Buzz sit next to it. A Full seat is all of them. A Dev seat is Dev Mode, FigJam, Slides, and Buzz. A Collab seat is FigJam, Slides, and Buzz.

The file is still the brief. The new products are a prototype you can tap, a page you can publish, a timeline, and an agent that will push pixels if you let it.

Config 2026 ran 23–25 June. Dylan Field’s recap named six things: code layers, Figma Motion, shader fills and effects, generative plugins, Weave tools, and the Figma agent. His own line: AI lowered the floor. It did not raise the ceiling.

What that list means when someone pays us:

The publish button does not decide which of these is allowed to reach a customer. You do.

How much does Figma cost in 2026?

Figures below are from figma.com/pricing on 15 August 2026. Organization and Enterprise are billed annually. Professional shows $16 for a Full seat on the page we opened; confirm the monthly versus annual toggle on the day you buy. Viewers on a paid plan can still comment without a seat.

Dev, Collab, and View seats, and everyone on Starter, get 500 AI credits a month. Extra credits are an add-on. Read their help article before you plan a Make week around the pack. We do not assume leftover credits survive the month.

Two facts from the same pricing FAQ that change the bill:

• Figma Sites and Figma Motion are in beta on Full seats. You cannot put Sites on a Dev seat and hope.
• The Figma agent does not consume credits in beta. When it leaves beta, standard credit usage applies. Budget for that before you build a process on free prompts.

Make, Sites, Draw, Dev Mode, FigJam, Slides, and Buzz sit on the Full seat. You cannot buy Sites as a separate product. That is the honest way to read “how much does Figma Sites cost”: it costs a Full seat, plus whatever the published domain and the CMS actually need.

We have never put a production brand site on Starter. Professional is the first plan we will run a handoff on — Dev Mode, Code Connect, and the MCP server (200 tool calls a day on the page we opened). Organization is what you pay when two teams are already fighting over a library.

What is Figma Make, and should you publish it?

Make takes a prompt, or a frame you already drew, and builds something you can click. You can hook Supabase, publish a URL, put a password on it. In late July they added a properties panel, so you can correct the object instead of prompting it again. Figma’s own walkthrough is the one we send first.

They posted the properties-panel update themselves. That is the right use: the prototype becomes a thing you can correct, not only a thing you can prompt again.

Use it when a stakeholder will not read a prototype link, or when you want to feel a flow before you argue about type. The first pass is allowed to be ugly. You are going to throw it away.

Do not use it for the week after launch. There is no CMS you would hand to a Thursday intern. There is no ads landing you would point spend at. There is no file layer an answer engine can cite without inventing you. The published URL is a demo.

Designers have been saying this in public. The useful thread is not “Make is bad.” It is “what is the point if I cannot take the thing back into the file I actually ship.”

We use Make the way we use a paper sketch. The client can tap it. Then we open Design and do the work. If a founder wants the Make URL on the internet as the company, we say no. That is the same refusal as AI-generated sites that look the same.

What is Figma Sites, and is it a website?

Sites is a beta on Full seats. Blocks, breakpoints, a CMS, video, a password, a Figma subdomain or a custom domain, and code layers so you can write or prompt interactivity on the canvas. Config put code layers first because Figma wants code next to vectors, not in another department.

It is also not Next.js.

A marketing site that has to take ads, an agent, large photography, and a file the models can read still wants a stack you own. We wrote the longer comparison in Next.js vs Webflow vs Framer. Sites sits closer to Framer: visual, fast, published from the design tool. Fine for a campaign, a passworded review, a one-pager that has to exist on Friday.

The community has been asking the same question since it launched. Have you published one. Would you.

Sites can be the review. It is not Eternal. That site had to feel like a room on the first scroll. That is a directed Next.js build, not a published Figma file. If your sales team will not send the URL, publishing it from Sites will not fix the copy.

What does the Figma design agent actually do?

The agent is a chat on the canvas. It drafts and remixes frames, renames layers, writes shader fills, packages skills, and talks to connectors Figma listed — Notion, Slack, GitHub, Atlassian. Chats are visible to teammates unless you hide them. Tammy Taabassum and Rodrigo Davies walk through the jobs it is for.

In beta it does not burn credits. That will change. Do not build a weekly process on a free meter.

What we let it do: rename layers. Draft a first layout from a written brief. Generate a motion start we will then sit with. Build a one-off plugin we would never have written.

What we do not let it do: the homepage. The offer. The sentence a stranger has to understand in four seconds. We wrote that test in the homepage test. Taste is still a person in the file.

Config also shipped generative plugins and Weave tools through the same agent. Describe a tool, get a control. Describe a style transfer, get a workflow you can run again. Useful. Still a draft until someone with an eye says yes.

An agent on the canvas is not an agent on the inbox. The Figma agent designs. The support agent files a case. If you came here because someone said “we need an AI agent,” those are different products. We covered the second job in chatbot vs AI agent.

What is Figma Motion, and do you still need After Effects?

Motion is a beta on Full seats. A timeline on the canvas. Keyframes, presets, component-level motion that travels with the instance, export to MP4, GIF, WebM, or SVG, and inspect in Dev Mode as CSS, JSON, or React. MCP-compatible, so a coding agent can take the animated frame.

Figma’s own Motion-in-Motion post is the short demo we send.

The longer walkthrough, with Kelly and Priscilla Choi, is the one we send a motion designer.

We use Motion when the motion has to live in the design system: a button, a card, a hover every page will inherit. We leave Figma when the hero is a film. After Effects, a director, or a still. Do not animate a brand into a template.

Where does Anima sit if Figma already writes code?

Anima is the Figma-to-code plugin and the Playground around it. Paste a Figma link, or open the plugin, and it writes React, HTML, Vue, Tailwind. You can hand a Playground link, a code package, or a snippet. Their site calls it design-aware code, not a screenshot with a <div> soup behind it. Nick Babich’s walkthrough is still the clearest public demo of the loop.

Anima’s own claim, on the pricing page we opened, is 1.5 million Figma users. Treat that as theirs. What we can verify is the product: a plugin that has been in this job for years, plus a Playground that now takes a prompt, a screenshot, or a public file.

They posted the image-to-code loop in July. That is the honest pitch — fidelity from a picture, not a chat that invents a layout.

Designers have been asking, in public, whether anyone uses Playground on a real project or only on a Friday demo. That is the right question.

How much does Anima cost?

From animaapp.com/pricing on 15 August 2026. Their page mixes euros and dollars. We quote what it showed.

A code generation is each export, import, clone, prompt, or MCP call that produces code. That is their definition. The free plan is a trial of the loop, not a production seat.

Anima also ships Buddy, a Figma plugin that writes into the canvas — HTML, screenshots, Claude artefacts, live sites, turned into editable layers. Their July update said you can point Buddy at a ChatGPT subscription and skip Anima credits. Useful if the job is “get this into Figma.” Different from “get this out of Figma as React we will own.”

Figma Make vs Anima vs a developer

Make produces a prototype you can click. Anima produces code you can open. A developer produces a site you can run ads against, put an agent on, and still edit in a year.

We open Anima when the file is real and someone needs to see the React, not imagine it. We do not paste Anima’s output into production and walk away. Auto-layout that was sloppy in Figma is sloppy in the repo. Dev Mode plus a person is still the handoff we trust for web work.

Where does Figma fall short?

Make is not a CMS. The Thursday intern cannot change the offer without opening a prompt. If marketing lives in the site, buy Webflow, Framer, or a Next.js CMS. We said that in the stack note.

Sites is a beta. Custom domains and a CMS are on the page. Production performance, redirects, the file layer an answer engine reads: that is still a site you own. Do not move the company there because the publish button is close.

Credits are a second invoice. Make, image tools, Weave, and (later) the agent all pull from the same pack. A Full Professional seat is 3,000 a month. A Make week will notice. Buy the add-on, or stop generating.

Code layers are not a repository. Config is right that code is a material. A material on the canvas is not a pull request, a preview deploy, or a Core Web Vital. We still ship the site.

Anima will not save a messy file. Auto-layout that was decorative, unnamed layers, absolute positions — the plugin writes what it sees. Clean the file. Then export. Then have a person read the React.

Prompted Make, prompted Sites, and prompted Anima will look like each other if nobody directs the work. We wrote that in why AI-generated websites look the same. Hire for taste, or keep the twenty dollars and live with the template.

Who should stay on Figma — and who should publish somewhere else?

Stay on Figma if you design products or brand sites with more than one person in the file. Professional is the floor. Organization is the floor when two teams share a library.

Use Make if a stakeholder needs to click before they will approve type. Use Sites if the thing dies in six weeks and nobody will run ads at it. Use Anima if a developer needs to see the React this afternoon.

Publish somewhere else if the site is the company. Ads. An agent. Photography that has to feel like a room. A file stack the models can cite. That is web work, not a Figma publish.

Who should not buy more Figma: a founder who wants the Make URL to be the brand. A team that will not name their layers. A marketer who needs to edit every Thursday and will not open Figma. Send them to Webflow.

How we would run Figma on a real brief

1. Open the existing file. If there is no file, we make one. We do not start in Make.
2. Write the three lines a stranger has to understand. Homepage first. The four-second test still holds.
3. Let Make draft one flow, if the client needs to click. Password it. Do not connect a domain.
4. Build the system in Design. Components, variables, a mobile frame that is not an afterthought.
5. Motion only where the system needs it. A button, not a film.
6. Dev Mode, then Anima if someone needs to see the React today. Then a person writes the site.
7. Ship Next.js. Tracking. CMS. The file an answer engine can read. The Make URL comes down.

If day seven is still “can we just publish the prototype,” we stop. If day seven is a file a developer can inspect and a homepage a stranger can finish, we keep going.

Frequently asked questions

Is Figma still the right design tool in 2026?

Yes, if you design with other people and the file is the brief. The 2026 products — Make, Sites, Motion, the agent — sit on top of that file. They do not replace it. We still open Figma first.

How much does Figma cost per month?

On 15 August 2026 a Professional Full seat was listed at $16 a month plus 3,000 AI credits. Dev is $12, Collab is $3. Organization Full is $55, billed annually. Enterprise Full is $90, billed annually. Starter is free with 150 credits a day, up to 500 a month. Check figma.com/pricing.

Can I build a website in Figma now?

You can publish from Make or from Sites. That is a hosted prototype or a visual site. It is not the same job as a Next.js marketing site with ads, an agent, and a CMS a marketer owns. We publish campaigns from the design tool. We ship the brand site.

Does the Figma design agent use AI credits?

Not in beta. Figma’s pricing FAQ says prompts and actions are free until general availability, then standard credit usage applies. Plan for the meter before you turn the agent into a weekly process.

What is Anima, and do I need it if I have Figma Make?

Anima is a Figma-to-code plugin and a Playground. Make is a prompt-to-prototype. Use Make to click. Use Anima to inspect React or HTML from a real file. Use a developer to ship. Anima’s free plan is 5 chats, 5 imports, and 5 generations a day. Pro was listed at €40 a seat a month, billed annually.

Does Figma Sites replace Framer or Webflow?

No. Sites is a beta on Full seats with blocks, a CMS, and a custom domain. Framer is still the short campaign. Webflow is still the site a marketer edits every day. Next.js is still the site that is the product. We said that in the stack note.

Should we hire a studio or publish from Figma?

If all you need is a page that exists, publish from Sites or Framer and keep the money. If the site has to take ads, an agent, photography, and a stranger in four seconds, hire the studio. We design in Figma. We ship the site. Send the file to hello@simplexdigital.agency.