Figma pricing in 2026: what UK design teams pay now — and whether the Dev seat is worth it

Twelve pounds an editor a month sounds gentle — until you remember that Figma stopped selling you one kind of seat. Since the company overhauled its pricing in March 2025, splitting every login into Full, Dev or Collab tiers, the real cost of running a UK design team isn’t the headline number any more. It’s how many of each seat you’re quietly paying for, and whether the £9-ish Dev seat in the middle earns its place at all.

I’ve spent the past week pulling apart what that restructure actually means for a British studio in 2026, because the marketing page won’t tell you the bit that matters: where the money leaks. Here’s where I got stuck — and, more usefully, where I think you can claw some of it back before your next renewal.

What changed in March 2025

The old Figma was simple to the point of being expensive — one “editor” price, and everyone who needed to touch a file paid it. The 2025 reshuffle broke that into three roles. There’s a Full seat for people who design and edit, a Dev seat for engineers who inspect, measure and export but don’t push pixels around, and a Collab seat for the stakeholders who only ever view and comment. Across plans, list prices now span roughly €3 to €90 a month per seat depending on which tier and which plan you land on.

On paper it’s fairer, and if your team is honest about who does what, it can genuinely cost you less than the old flat editor price did. In practice, though, it’s a sorting exercise — and Figma is betting most teams sort badly, leaving people on Full seats who only ever needed to look. The default when someone joins is rarely the cheapest seat that would do the job, so the savings only land if you go looking for them.

What a UK team actually pays now

Take the Professional plan on annual billing, which is where most agencies and in-house teams sit. The current rates work out at €16 a month for a Full seat, €12 for a Dev seat — that one bundles 500 AI credits — and just €3 for a Collab seat. Figma quotes in dollars and euros, so the sterling figure moves with the exchange rate, but UK buyers are looking at around £12 per editor per month on Professional, annual billing, and roughly £45 per editor per month once you step up to the Organization plan.

Put real numbers on it and the point lands faster. Picture a ten-person product studio: six designers who genuinely move pixels, two developers who live in the files, and two account or client-side people who only ever comment. On the old single-editor model you’d have paid an editor rate for all ten, or fudged it by sharing logins. On the new split, that’s six Full seats, two Dev seats and two near-token Collab seats — and the two viewers stop being full-price line items overnight. The savings are real, but only if you actually downgrade those last two; leave them on Full “for now” and you’ve handed back the entire benefit of the restructure.

That £12-to-£45 jump is the number I’d circle in red. The leap isn’t about adding designers — it’s about buying the controls (SSO, centralised admin, design-system branching) that a bigger team eventually can’t run without. A four-person studio doesn’t need any of it. A forty-person one will be quietly forced into it the first time someone asks for single sign-on or proper access management, and the per-seat price nearly quadruples on the way through. If you’re a growing UK team, that step-up is the cost you should be budgeting for now, not the headline £12 — because once you cross it, every seat you own gets dearer at the same time.

Is the Dev seat worth it?

This is the question every engineering lead is actually asking, and the honest answer is: it depends entirely on how often your developers open Figma. The seat is pitched at people who live in Dev Mode daily — inspecting a design system, diffing one version against the last, pulling clean specs and assets without nagging a designer. For an internal team building a real product, that’s genuinely useful, and at £9-ish a head it’s the cheapest editing line on the bill.

But SpecPeek’s breakdown of Dev Mode makes the counter-case well, and I think it’s right: for freelancers and agencies whose developers dip into a file a handful of times a sprint, a paid Dev seat is overkill. View-only access, or a lighter third-party inspector, covers the same ground for less. The cost itself isn’t fixed either — depending on plan it runs anywhere from $12 to $35 a month per developer, with the higher tiers loading on more AI credits you may never spend. So before you buy one per engineer, ask a blunt question: do they open Figma most working days, or just when a handover lands? If it’s the latter, you’re paying a subscription for an occasional glance.

And watch the small print. Figma’s own support pages warn that extra charges can appear mid-cycle when someone takes an action that upgrades their seat — a viewer who edits one frame can tip into a billable editor without anyone deciding to spend the money. On the new role-based model that trap is easier to fall into, not harder, because the line between “looking” and “editing” is now exactly the line between two prices. If you hand out Collab seats to keep costs down, make sure your stakeholders know that tidying a single component will quietly cost you.

Scale, and the discount nobody volunteers

If you’re past about fifty seats, the list price stops being the real price. Vendr’s benchmarks show teams at that size negotiating 15 to 30 per cent off, with median annual Figma spend landing near $27,630. That discount is never offered up front — you have to ask, ideally at renewal, ideally with a competitor’s quote open in another tab. A UK team taking the sticker price at fifty-plus seats is leaving a meaningful sum on the table every year, and procurement teams treat that as money found rather than money saved.

The lever that actually moves the number is timing. Walk into a renewal having already audited which seats are real and which are dormant, and you’re negotiating from a position of “we know exactly what we use” rather than “please don’t put the price up.” Annual commitment, a clean seat count, and a credible alternative in your back pocket are what unlock the back half of that 15-to-30 per cent range.

The seats I’d buy, and the one I’d cut

Here’s where I land. Buy Full seats only for people who genuinely move pixels — be ruthless about it, because every “just in case” editor is the most expensive seat you own. Hand every stakeholder a £3 Collab seat without a second thought; it’s the best value Figma sells, and it kills the habit of over-provisioning. The Dev seat is the real judgement call: pay for it if your engineers open Figma most days and lean on Dev Mode to ship, and skip it if they’re occasional visitors who’d be just as happy with view-only or a cheaper inspector.

What would change my mind on the whole thing is the AI credits. Right now they read like padding on the Dev tier. If Figma turns those 500 credits into something a developer reaches for daily, the £9 seat stops being a maybe and becomes the obvious buy. Until then, audit your seats before renewal, push for the volume discount the moment you’re eligible, and treat the new pricing for what it is — not a price cut, but a quiet invitation to keep paying Full money for people who only ever needed to watch.