Figma Blog: Introducing Specs — Markdown as a medium
On October 15, 2026, Figma announced Specs — a new type of object on the Figma canvas that creates a Markdown document directly alongside designs. Authors Luke Zhang, Johnny Dallas, and Aosheng Ran describe it as an attempt to solve a problem that has persisted in every design team: written intent and visual work live in different places, and the written part goes stale.
A Spec opens from the toolbar or by pressing D. It is a real Markdown file, multiplayer and editable inline, placed directly on the canvas next to the frames it describes. Designers can embed FigJam boards, canvas frames, and canvas nodes into the Spec, so the document and the referenced designs exist side by side rather than separated by a link or a screenshot.
The agent layer is significant. A Spec can host comments from an agent — the system supports asking an agent to expand a section, update content, or read and respond to reviewer notes. External connectors can supply context: Figma demonstrates a Hex integration where the agent runs a data analysis, then deposits the result as a comment inside the Spec. The content can move between the Spec, the canvas, and code layers as a project progresses.
The connection to engineering handoff is where Specs may matter most. Copying a Specs link to a coding agent via MCP passes the linked frames, diagrams, code layers, and Code Connect snippets alongside the Markdown text. The agent receives the written spec and the design artifacts as a single package, rather than having to infer structure from screenshots or navigate a fragmented document trail.
Specs is in open beta on paid Figma plans. The feature addresses a gap that annotation tools, Notion embeds, and link-based documentation approaches have not fully closed — that design intent, once written, tends to drift away from the design it describes.