ByFigma Specs is a new markdown-based document type that Figma launched in October 2026, and it lives directly on the design canvas instead of in a separate app. Unlike a plain .md file sitting in a repo, a Figma Spec can embed FigJam boards, frames, and canvas nodes, and Figma’s AI agents can read it and reply to comments left on it. For design and product teams who have watched context scatter across Notion, Google Docs, and Slack threads, Figma Specs is Figma’s attempt to put the brief back next to the work it describes.
This guide covers what Figma Specs actually does, how to create one, who can access it today, how it stacks up against the markdown files and Notion docs teams already use, and where it currently falls short.
What Is Figma Specs?
Figma Specs is a document format built around Markdown, designed to sit on the same canvas as the designs, prototypes, and FigJam boards it describes. Figma announced Figma Specs in mid-October 2026 alongside an expansion of Code Layers, the feature that turns a design layer into an interactive, code-backed element.
The thinking behind Figma Specs is straightforward. A requirements doc written in Notion or a stray README in a repo quickly drifts out of sync with the actual design file. Someone updates a component, forgets to update the doc, and three weeks later a new hire is reading instructions that no longer match what’s on screen. Figma’s pitch is that if the spec lives on the canvas, next to the frames it is written about, it is far less likely to go stale, and an AI agent working on that canvas can read the spec the same way a teammate would.
A Figma Spec is not a static page. It behaves like any other object on the canvas: you can resize it, move it next to the frame it documents, and link out to other files or nodes. Comments on a Spec are visible to Figma’s agents, so when someone leaves feedback, an agent assigned to that file can act on it directly, without a human relaying the instruction into a chat window first.
What Problem Is Figma Specs Actually Solving?
Before Figma Specs, a typical design handoff looked like this: a designer finishes a flow in Figma, writes the behavior notes in Notion or Confluence, pastes in a few screenshots, and shares the link with engineering. Within a sprint or two, the designer tweaks the flow, and the screenshots in that Notion doc are already out of date. Nobody updates them until a bug report forces the issue.
Figma Specs addresses this by removing the screenshot step entirely. Instead of pasting a static image, you embed the live frame or canvas node, so whoever opens the Spec sees the current design, not last month’s version. The same logic applies to AI agents. An agent reading a stale screenshot has no way to know it’s stale; an agent reading a live embed is always looking at the real thing.
When Did Figma Launch Specs?
Figma introduced Specs in open beta in mid-October 2026, timed to Figma Config India and the same announcement round that moved Code Layers from private to public beta. TechCrunch covered the announcement on October 14, 2026, describing it as part of a push to define how AI agents work inside Figma’s platform.
Access rolled out in stages rather than all at once. Figma Specs first reached paid-plan seats only, then widened to cover every seat type roughly two weeks later, according to independent pricing trackers that monitor Figma’s plan pages. If you opened Figma in mid-October and didn’t see a Spec option, that staged rollout is the likely reason, not a bug in your account.
How Do You Create a Figma Spec?
You can start a Figma Spec three ways:
- Press the “D” keyboard shortcut anywhere on the canvas to drop a new Spec next to your frames.
- Open the Spec tool from the left toolbar and click on an empty area of the canvas.
- Visit figma.com/spec/new to start a standalone Spec that isn’t attached to any particular file yet.
You can also drag an existing .md file straight onto the canvas, and Figma converts it into an editable Spec automatically, keeping the original text intact.
Once a Spec exists, you write in it the way you’d write any Markdown document: headings, lists, links, and code blocks all work. The difference shows up when you want to reference the actual design. Instead of pasting a screenshot, you embed the live frame, FigJam board, or canvas node, and it stays connected to the original. If the design changes, the embedded reference in the Spec reflects it automatically.
Specs can also be moved and resized like any other canvas object, so teams commonly park one beside the flow or component set it documents, rather than filing it away in a separate tool. If you’re already comfortable rearranging layers and frames, for instance using tools covered in our guide to the Figma Vector Eraser tool, positioning a Spec on the canvas will feel familiar.
What Can You Put Inside a Figma Spec?
A Figma Spec can hold embedded FigJam files, full frames, individual canvas nodes, and the usual Markdown elements: headings, tables, checklists, and inline code. Because the embeds are live references rather than static images, a reviewer looking at a Spec always sees the current state of the design, not a screenshot taken weeks earlier.
The comment layer is where Figma Specs diverge most from a plain Markdown file. Comments left on a Spec are visible to Figma’s AI agents operating in that file. That means a product manager can leave a note like “update this copy to match the new tone guidelines” directly on the Spec, and an agent working the file can read and act on it without anyone copying the instruction into a separate prompt window.
This is also why Figma frames Specs as a counterpart to Code Layers rather than a separate, unrelated feature. Code Layers lets a design layer become an interactive, code-backed element; Specs gives the agents working on those layers a structured, canvas-native source of context to work from. Teams already experimenting with Figma’s generative tooling, such as the workflows in Figma Weave Tools, will likely find Specs a natural extension of that same agent-driven direction.
Who Can Access Figma Specs Right Now?
Figma Specs is in open beta for paid plans: Professional, Education, Organization, and Enterprise, across web, desktop, and mobile. The free Starter plan does not include Figma Specs. Coverage of the rollout notes that access expanded from paid seats only to all seat types roughly two weeks after the initial launch, so the exact feature set an account sees can depend on when that account’s rollout stage lands.
Because this is still a beta, expect the usual caveats: UI details can shift, and not every workspace will see the Spec tool appear on the same day as another. If your team doesn’t see it yet, checking back in a week is more useful than troubleshooting account settings. Teams comparing Figma’s paid tiers against competitors, including the breakdown in our Canva vs Figma 2026 guide, should note that Specs is one more reason the paid tiers keep pulling ahead of free design tools on agent-ready features.
How Does Figma Specs Compare to Markdown Files and Notion Docs?
The short version: a plain Markdown file is portable but disconnected from the design, a Notion doc is easy to organize but lives in a separate app, and a Figma Spec trades some of that portability for being physically attached to the work.
| Feature | Figma Spec | Plain Markdown File | Notion Doc |
|---|---|---|---|
| Lives next to the design | Yes, on the canvas | No | No |
| Embeds live frames or nodes | Yes | No | No, screenshots only |
| Readable by Figma’s AI agents | Yes | No | No |
| Portable outside Figma | No | Yes | Yes |
| Requires a paid plan | Yes | No | Free tier available |
| Best suited for | Canvas-native specs for agents | Version-controlled docs in a repo | Cross-functional planning |
For a design system team that already lives inside Figma all day, keeping the brief on the same canvas removes a tab-switching step that adds up over a week. For a cross-functional team that relies on Notion for sprint planning, engineering tickets, and non-design documentation, moving specs into Figma just for this feature may create a second source of truth instead of removing one. The right call depends on where your team already spends its time, not on which tool has the newer feature.
How Do Figma Specs Work With Figma’s AI Agents and Code Layers?
Figma Specs and Code Layers shipped in the same announcement round because they’re meant to work together. Code Layers converts a design layer into an interactive, code-backed element, and an agent assigned to build or adjust that layer needs context about what it’s supposed to do. A Figma Spec sitting next to the layer, with comments the agent can read, is that context.
In practice, this means a design lead can write a Spec describing the intended behavior of a component, embed the frame it applies to, and leave follow-up comments as the agent iterates. The agent reads the Spec and the comment thread without anyone needing to re-explain the brief in a chat window each time. Figma’s framing, per its own announcement and TechCrunch’s coverage of it, is that Markdown files have historically been single-player documents, written by one person and rarely updated by anyone else; Figma Specs are built to be read and acted on by both humans and agents.
This agent-readable layer is the real differentiator. A Notion doc can be shared with a bot through an integration, but it isn’t native to the canvas the agent is actually editing. A Figma Spec sits in the same file, next to the same layers, which removes a step that would otherwise require piping context between two separate tools.
Should You Replace Your Design Docs With Figma Specs?
For a design-system or product-design team that already does most of its documentation work inside Figma, yes, Figma Specs is worth trying: it removes the drift between a written brief and the frames it describes. For a team whose planning lives in Notion, Google Docs, or a wiki shared with engineering and other non-design functions, treat Figma Specs as a canvas-native addition rather than a wholesale replacement.
A reasonable middle ground many teams are adopting: keep sprint plans and cross-functional docs where they’ve always lived, but use a Figma Spec for anything that only makes sense next to a specific frame, flow, or component, such as interaction notes, edge-case behavior, or instructions aimed at an AI agent working that file. Designers who already keep visual references close to their work, the way covered in our Figma Shader Fills guide, will recognize the same instinct driving Specs: context belongs next to the thing it describes, not three tabs away.
How Should a Team Prepare Before Adopting This Workflow?
Before handing a whole team a new way to write documentation, it helps to run a small pilot rather than a wholesale switch. Pick one active component or one in-progress flow, write the brief for it the new way, and compare how long it takes versus the old process of a separate doc plus pasted screenshots.
A few practical steps make that pilot easier to judge fairly:
- Choose a flow that already has stale documentation, so the before-and-after comparison is obvious rather than theoretical.
- Involve whoever reviews design handoffs today, since they’re the ones who will notice whether comments actually get addressed faster.
- Set a two-week check-in to decide whether the new document earned its place, rather than letting it linger unreviewed alongside the old one.
- Keep a short written note of what broke or felt clunky, since a beta feature’s rough edges are useful feedback for the next rollout wave.
Teams that skip the pilot and roll a new documentation habit out company-wide tend to end up with two systems running in parallel: the new canvas-native one and the old Notion habit nobody formally retired. A two-week trial on a single flow avoids that outcome and gives a design lead a concrete answer, backed by one real example, instead of a guess.
It’s also worth telling engineering and product stakeholders what changed, even during a pilot. If a reviewer is used to finding handoff notes in Notion, a documentation habit that quietly moves onto the canvas without anyone being told will just create a new place for information to get lost, which defeats the entire point of trying it in the first place.
What Are the Current Limitations of Figma Specs?
Three limitations are worth knowing before you build a workflow around Figma Specs. First, it excludes the free Starter plan, so teams on that tier won’t see it at all. Second, because it’s in open beta, the rollout has been staged rather than immediate, and published coverage doesn’t fully document export options such as PDF or Word output yet. Third, since a Spec’s embedded frames and nodes are live references, a Spec is tied to the Figma file it was created in; it isn’t a portable document you can hand to someone outside Figma the way a plain Markdown file is.
None of these are unusual for a beta feature, but they matter if you’re deciding whether to make Figma Specs your team’s single source of truth today versus waiting for general availability. A beta that changes its export options or seat coverage mid-rollout is normal for Figma; it is not a sign the feature is being abandoned.
Frequently Asked Questions
Is Figma Specs free to use?
No. Figma Specs is available on paid plans only: Professional, Education, Organization, and Enterprise. It is not included in the free Starter plan.
Can I turn an existing Markdown file into a Figma Spec?
Yes. You can drag an existing .md file onto the Figma canvas and it converts into an editable Spec automatically, keeping the original text while adding the ability to embed live frames and canvas nodes.
Does Figma Specs replace Code Layers?
No. Code Layers converts a design layer into an interactive, code-backed element, while Figma Specs provides the documentation and context around that layer. Figma launched both in the same announcement round because they’re designed to complement each other.
Can Figma’s AI agents read comments on a Spec?
Yes. Comments left on a Figma Spec are visible to Figma’s agents operating in that file, which lets a reviewer leave feedback that an agent can act on directly, without it being re-typed into a separate prompt.
Is Figma Specs available on mobile?
Yes, coverage of the rollout describes Figma Specs as available across web, desktop, and mobile for eligible paid plans, though as a beta feature the experience can vary by platform and account.
How do I start a new Figma Spec?
Press “D” on the canvas, choose the Spec tool from the toolbar, or go to figma.com/spec/new to start a standalone Spec that isn’t tied to a specific file.
The Bottom Line
Figma Specs is still a beta feature, but it answers a problem every design team recognizes: briefs and specs that drift away from the designs they describe. By keeping Markdown content, live canvas embeds, and agent-readable comments on the same surface as the work, Figma is betting that documentation stays more useful when it never has to leave the file. If your team is on a paid plan and already working inside Figma, it’s worth testing Figma Specs on your next component or flow before deciding whether it earns a permanent spot in your workflow.
Subscribe for Newsletter
