Code layers entered open beta on 15 October and are free on paid plans until 4 November. After that, one build costs at least 250 credits against a 3,000 credit monthly allowance, so a Professional seat funds at most 12.
Figma's new code layers are free on paid plans only until 4 November. After that, every build draws on a fixed monthly pool of AI credits. A design seat becomes a metered seat.
In Figma's own words, code layers "will use AI credits", with creating and editing "free through November 4, 2026" on paid plans. From 5 November, a prototype built in code uses the same credits as every other task the Figma agent performs.
The free window lets design teams learn how fast code layers burn credits. It also lets Figma learn how much of that usage customers will accept once the meter runs on real budgets.
In Dylan Field's launch post, code layers and guidelines enter open beta. Specs arrives on web, desktop and mobile for paid plans, and the Figma agent is generally available on the canvas.
Figma also added 20 new MCP partner integrations. Code sources stay in closed beta on paid plans, and Payload in Figma Make rolls out over the coming weeks.
The waiver is narrow. Figma's help centre says only code layer generation and editing tasks are free, and only on paid plans. Anything else the agent does in the same session is already charged. The free part is a slice of each working session, not the whole of it.
After 4 November, "all code layer tasks will use AI credits like other agentic AI features". Creating a code layer requires a Full seat. The people allowed to build are therefore the people whose allowance gets drawn down.
The rate card shows the scale. Figma's credit page lists "create a code layer from these frames" at 250 credits or more. Variations off an existing code layer cost 315 or more, and an update from extracted designs costs 175 or more.
A Full seat carries 3,000 credits a month on Professional, 3,500 on Organization and 4,250 on Enterprise. Credits reset monthly, do not roll over and cannot be shared between seats. A light month for one designer does nothing for a heavy month for another.
Divide the Professional allowance of 3,000 by the 250 floor rate and a seat covers at most 12 builds a month. Organization manages 14 and Enterprise 17. A team of ten designers on Professional holds 30,000 credits a month, enough for 120 builds at the floor rate, and every unspent credit expires at the reset.
Those counts are ceilings. The 250 is a minimum, and Figma says consumption varies with model, complexity and context. The counts also assume the seat does nothing else with its credits.
Maximum number of 250 credit code layer tasks a single Full seat can run per month on its included AI credits: Professional 12, Organization 14 and Enterprise 17.
View data
| Paid plan, Full seat | Tasks of 250 credits per month |
|---|---|
| Professional (3,000 credits) | 12 |
| Organization (3,500 credits) | 14 |
| Enterprise (4,250 credits) | 17 |
That assumption fails quickly because the same pool pays for other tools. Figma Make, where generating an app from scratch starts at 100 credits, draws on it. So does the agent, which charges 100 or more to summarise a canvas and 300 or more for a five screen mobile checkout flow.
A single code layer build at 250 is therefore close to the price of a full generated flow. A designer who uses all three tools in a week draws from one tank. The 3,000 credits have to cover the whole month.
A build is also rarely the end of the work. Prototypes are iterative, and the customer cases Figma publishes are about exactly that. Merkle reports 30% faster iteration and 50% less documentation, and a Checkout.com designer says a client demo came together about 50% faster.
Speed and repeat edits are the behaviour that consumes credits. One create plus one variation costs 565 credits, so a 3,000 credit seat funds about five such pairs a month. A team that edits as freely as the demos suggest runs out in the first week.
Teams can buy more. Admins can purchase additional AI credits through subscription or pay as you go billing, and can set limits per user. Twelve builds may be plenty for a designer who mostly works in frames.
For heavy users, a seat budgeted as a fixed licence now carries a variable line beside it. The price per credit appears only inside the admin purchase flow, so the cost of topping up cannot be sized from the public pages.
The free window also serves Figma. It gets more teams building in code and gives the company 20 days of data on what a build really consumes. The credit page already says its approximations "may evolve over time".
For a design operations lead on a Professional or Organization plan, the window is a measurement job. Figma says users can see the credits a prompt consumed by hovering over the AI credits icon after each run. There are 20 days to log those numbers on a real project.
Use that time to set per person limits before 5 November. Decide which designers hold Full seats for code layers. Free credits invite looser prompting, so a baseline taken now will understate what the same team spends once each prompt costs something.
The first monthly reset after 4 November will answer the question. Admin dashboards show usage and the reset date for each seat. Professional and Organization teams will then see whether their builds have consumed the allowance.
At 250 credits or more per build against 3,000 credits a seat, Figma can extend the window, raise the allowances or sell more credit packs.