Skip to content

Figma to website guide

What Is Figma Dev Mode, and Do You Need It?

Dev Mode is Figma's developer view for inspecting designs and generating code context. It needs a paid plan with a Full or Dev seat, and it does not build or host a website.

Figment editorial teamPublished Updated

Publishing from Figma with Figment

The Figment plugin turns page frames in a Figma Design file into a hosted website.

Free planfigment.so address, Figment badge$0
Paid plansYour own domain, no badgeSee plans

Hosted publishing, not a code download.

Figma Dev Mode is a developer-focused view for inspecting a design and pulling out implementation details: measurements, code snippets, component metadata, and a connection point for coding agents. It does not build, host or publish a website. A developer, or a coding agent working from what Dev Mode exposes, still has to write and deploy the site code. It requires a paid Figma plan and either a Full or a Dev seat.

What does Dev Mode do?

Dev Mode inspects layers, generates code snippets, marks work as ready, connects components to code, and exposes an MCP server for agents.

Inspect designs. The Inspect panel shows layer names, types, when a layer was last updated, and a way to compare design changes over time, plus component and variant metadata for anything built as part of a component (Figma Learn, "Guide to Dev Mode").

Generate code snippets. Toggling the panel to Code view produces an autogenerated snippet for the selection. You can "select the language and units to view in the canvas and generated code, as well as extend the functionality of code snippets with codegen plugins" (same source).

Mark work "ready for development." Designers can flag frames, components, instances and sections as ready. Figma's documentation notes that "objects on the canvas marked as ready appear under Ready for development in the Dev Mode layers panel" (same source), a way to signal what is done without a separate task tracker.

Code Connect. Figma describes it as "a bridge between your codebase and Figma's Dev Mode, connecting components in your repositories directly to components in your design files," which also gives the Figma MCP server "direct references to your actual code" (Figma Learn, "Code Connect"). It is "Available on the Organization and Enterprise plans" and "Requires a Full or Dev seat" (same source).

The Figma MCP server. This connects Dev Mode to an outside coding agent rather than only a human developer. Figma's guide says the MCP server lets an agent "explore and implement designs quickly and accurately" by extracting "design context and code from your Figma designs, FigJam, and Make files," generating code from selected frames, and using Code Connect to stay consistent with real components (Figma Learn, "Guide to the Figma MCP server"). There are two versions: a remote server available "on all seats and plans," and a desktop server that needs "a Dev or Full seat" on "all paid plans" (same source). Enable the desktop server inside Dev Mode: toggle to Dev Mode and turn on "Enable desktop MCP server" in the inspect panel. You also need an editor or agent that supports MCP, such as VS Code, Cursor, Windsurf, Claude Code or Codex.

Which plans and seats get Dev Mode?

Dev Mode needs a paid plan with a Full or Dev seat. The free Starter plan has none.

Plan or seatDev Mode access
Starter (free) planNone: "Dev Mode is not available on the Starter plan"
Full seat, any paid planFull access to Dev Mode, plus every other Figma product
Dev seat, any paid planFull access to Dev Mode, FigJam, Figma Slides, and Figma Buzz, plus view and comment access in Figma Design files
Collab seatView and comment access, with "basic inspection on Dev Mode" only, not full Dev Mode
Free viewer / View seatBasic inspection, no seat purchase required

Sources: figma.com/pricing and Figma Learn, "Dev Mode for admins". Figma updates seat structures as plans change, so check the current pricing page rather than relying on this table indefinitely.

If you do not have a Full or Dev seat, you are not locked out entirely. Figma's admin documentation says "users can make requests to access Dev Mode if their current seat doesn't provide Dev Mode access," and "admins can use seat approval settings to manage incoming seat requests."

Can Dev Mode publish a website?

No. Dev Mode does not publish or host anything. Even with the MCP server wired to a coding agent, its job stops at giving that agent or a human developer accurate context about the design: measurements, structure, and real component code where Code Connect is set up. Writing the site, reviewing the result and deploying it happen outside Figma, in whatever codebase and hosting you use.

Getting a page of HTML out of Figma is a different question. Our guide to exporting Figma to HTML covers Dev Mode's Inspect panel as one of five routes from a Figma file to a working page, and why it works best as "a spec reader" rather than something you assemble a whole page from. This post covers Dev Mode as a product: what it is for, who gets it, and where its job ends.

Do I need Dev Mode?

You need it if a developer or coding agent will write real code from this design. Dev Mode is built for that handoff, and Code Connect makes it more accurate if your team already maintains a design system in code. To scope what an agent connected through MCP may touch, the narrow-access principle in How Do I Give an AI Agent Limited Access to My Website? applies here too.

You do not need it if nobody is writing code and you only need the design published as a working site. Figma Sites is Figma's own hosted publishing product. Publishing the Figma file directly through a plugin, as the Figment plugin does, is another route. Neither needs Dev Mode. Figment publishes finished Figma Design files as a hosted site (hosted publishing, not a code download, and no CMS); the Free plan uses a figment.so address with a Figment badge, and Pro ($49 a month, or $39 a month billed yearly) adds up to 10 custom domains. See pricing.

What if I only need to read values, not write code?

A View or Collab seat still gets basic inspection, enough to check colors, spacing and dimensions on a layer without full Dev Mode's code snippets or Code Connect. If that is not enough, ask a teammate with a Full seat to mark the relevant frames "ready for development," or ask an admin about a seat request or upgrade before assuming you must buy a seat.

What should I check before relying on Dev Mode for a build?

  • Your Figma plan and seat type include Dev Mode. Starter does not, and Collab and View seats get basic inspection only.
  • Finished frames and components are marked "ready for development," so a developer or agent is not working from a stale draft.
  • Code Connect is set up if you have a design system in code and want snippets to reflect it. It needs Organization or Enterprise plus a Full or Dev seat.
  • If you use the MCP server, you are on an MCP-capable editor or agent, and you have scoped what it may touch.
  • You are not expecting Dev Mode itself to produce a finished, deployed website. That step happens afterward, in code.