Figma Dev seat vs Collab seat: what each costs and who needs Dev Mode

A Figma Dev seat costs $12 per person per month on Professional billed annually. A Collab seat costs $3. The $9 difference buys exactly one thing that matters: full Dev Mode instead of basic inspection. If someone opens designs to pull specs, measurements, variables or code, they need the Dev seat. If they only join FigJam boards, build Slides and leave comments, the Collab seat does the same job for a quarter of the money.

That sounds simple, and on the pricing page it is. In practice it is the seat decision teams get wrong most often, in both directions. Engineers get downgraded to save money and lose the handoff tooling they depend on. Product managers and marketers get put on Full seats nobody audits, at five times the price of the seat they actually needed.

Figma seat prices and what each one opens

Read across the Dev and Collab rows and you can see how narrow the gap is. Both seats give full editing in FigJam, Figma Slides and Figma Buzz. Both give view and comment access in Figma Design files. Both carry 500 AI credits a month. Dev Mode is the only line where they differ, which is why the decision is genuinely a single question rather than a feature comparison.

What is the difference between a Dev seat and a Collab seat?

Full Dev Mode. Figma documents the Dev seat as having full access to Dev Mode, Figma Slides, FigJam and Figma Buzz, plus view and comment access in Design files. It documents the Collab seat identically except for Dev Mode, where the wording is no access, basic inspection only. Everything else about the two seats is the same.

Basic inspection is not nothing. A Collab seat holder can open a design and read off colors, fonts and rough dimensions, which is enough to answer whether the button is blue. Full Dev Mode is a different tool: the dedicated handoff view with ready-for-development statuses, generated code for the component under the cursor, variables and tokens resolved to their real values, annotations, measurements between any two layers, and the plugin and MCP surface that connects Figma to an editor or a design system pipeline.

Which engineers actually need a Dev seat?

Anyone whose work starts by opening a design file. That is front-end engineers, mobile engineers, and design-systems engineers, without exception. If implementing a screen means reading spacing values, matching a token, or checking which components are marked ready, basic inspection turns a ten-minute task into a thread of questions aimed at a designer.

The people who usually do not need one are backend and infrastructure engineers, QA, and engineering managers. A backend engineer consuming an API contract has no reason to open Dev Mode. A QA engineer comparing a build against a spec often can work from the shared prototype and comments. An engineering manager reviewing scope needs to see the work, not measure it. All three sit fine on a Collab seat at $3, or on a free View seat if they never need to edit a FigJam board.

The honest test is not seniority or job title. Ask who opened Dev Mode in the last thirty days. Figma admins on Organization and Enterprise can see activity, and on smaller teams the answer is usually obvious if you just ask. Everyone who did needs a Dev seat. Everyone who did not is a candidate for a downgrade at renewal.

A worked seat plan for a 20-person product team

Take a typical setup: 4 designers, 6 front-end engineers, 3 backend engineers, 2 QA, 3 product managers, 1 marketer, 1 founder. Here is what the same team costs on Professional under two approaches.

That is $1,848 a year, roughly 48 percent, for a change that removes nothing anyone was using. The gap widens sharply on the bigger plans, because the Collab seat barely moves while the Full seat does not. On Organization the same 20 people cost $13,200 a year on Full seats against $3,960 matched. On Enterprise it is $21,600 against $5,880.

Two details make the model less tidy than the arithmetic suggests. First, seat changes are an admin action, and the billing rule is that moving someone to a seat type you already have unassigned costs nothing, while moving them to a type you do not have means buying a new seat. Second, a downgrade mid-term frees a seat rather than refunding one, so the saving lands at renewal. Run the audit four to six weeks before the contract date, not after it.

Can a Collab seat open Dev Mode at all?

It can see basic inspection, which Figma treats as distinct from Dev Mode itself. The distinction is deliberate and it is where most of the confusion comes from. The Dev Mode toggle is visible to a Collab seat holder, so the seat does not feel blocked in an obvious way. What is missing shows up gradually: no ready-for-development statuses, no generated code panel, no resolved variables, no annotations, no MCP server access.

Figma's own community forum carries recurring threads about this, with titles like collaboration seat limitations after upgrade and misleading collab seat limitations, alongside people asking why they lost access to design tools. The pattern in those threads is consistent: somebody bought the cheap seat expecting the expensive one, discovered the gap during a sprint, and had to buy again. Reading the seat definitions before the purchase is a five-minute job that avoids it.

Does everyone need a paid seat to see the work?

No, and this is the part most seat plans miss. Figma states that on a paid plan you can let others view and comment on your files without purchasing extra seats, and it sells a View seat at $0 that covers view and comment access in Figma Design, Figma Slides and FigJam.

So an executive who wants to watch the design evolve, a customer-success lead who comments on copy, or a contractor reviewing a handoff costs nothing at all. The paid ladder only begins when someone needs to edit a FigJam board, build a Slides deck, or produce Buzz assets. That is the point where $3 becomes the right answer, and it is a long way below the $16 most companies default to.

Where the seat decision stops helping

Getting the mix right is real money, and it takes an afternoon. What it does not change is the quality of what ends up on the board. Dev Mode is a handoff problem; the harder problem upstream is that the workshop which decided what to build produced six variations on whatever the loudest person said first. A $90 seat and a $3 seat produce identical walls when the room is anchored.

That is the gap Brainstormer is built for. Type the challenge and six standing personas argue it from their own angle, so around twenty genuinely different directions land in about thirty seconds, each tagged with the persona behind it. The Skeptic names the risks before a stakeholder does, and the Customer argues from outside the building. The same run lifts a shortlist of the three strongest with the reasoning written out and names one winner. Grouping into themes and scoring against your own criteria stay your judgment call.

Pricing runs per outcome rather than per seat: Solo $10 a month billed yearly, Pro $24.50, Team $64.50 per account, all with unlimited brainstorms. Keep FigJam for the board, since a Collab seat already includes it. Once the design is settled and the engineers have the Dev seats they need, getting the build onto a server without downtime is the next problem in the chain, and it is a different tool again.

How to run the audit this week

• Export the member list from Figma admin with current seat types. On Professional this is a short list you can read in one screen.
• Mark everyone who opened Dev Mode in the last 30 days. Those people keep a Dev or Full seat. Nobody else needs one.
• Mark everyone who edited a Design file. Those people keep a Full seat. Editing Design is the only thing the Full seat uniquely buys.
• Everyone left goes to Collab at $3, or to a free View seat if they have never created a FigJam board or a Slides deck.
• Schedule the change for four to six weeks before renewal, since a downgrade frees a seat rather than refunding it.

If you want the fuller picture of the cheap end of the ladder, our Figma Collab seat vs Full seat page covers what the $3 seat opens and where it stops, and the FigJam pricing page covers what the whiteboard itself costs on each tier. For the cross-vendor view, Miro vs FigJam is the comparison that usually decides it, since the answer mostly depends on what your company already pays for.