Skip to content
saymock
Product Agents Use cases Developers FAQ Pricing
EN, English
  • Français
  • English
  • Deutsch
  • Español
  • Português
  • Italiano
  • Nederlands
  • 日本語
  • 한국어
  • 简体中文
Theme
Sign in Try it

Guides · Figma import

Import a Figma design into Saymock

Updated November 18, 2026

Your screens are in Figma and you want your agent to work on them, or your team to review them on a Saymock board? There are two ways: paste the frames into the editor, which converts the layers into HTML + Tailwind in seconds, or let your agent rebuild them through both MCP servers and check each one against Figma.

1. Copy in Figma, paste in Saymock

  1. In Figma, select the frames to bring over and copy them (⌘C, or Ctrl+C).
  2. Open a file in Saymock, click on the board and paste (⌘V, or Ctrl+V).

Each frame becomes a screen with its Figma name. What carries over:

  • Layout: auto-layout becomes flex, with Figma’s sizes, spacing, padding, alignment and wrap; other frames place their layers absolutely, as in Figma.
  • Styles: fills, strokes, radii, shadows, blurs, opacity and clipping become Tailwind classes; text keeps its font and its mixed styles.
  • Images and vectors: images are stored in the workspace, vectors become SVGs; Material Symbols icons are recognized.
  • Components: Figma components become Saymock components, their instances become instances with their own props.
  • Boards: a Figma frame that lays out several screens is pasted as those screens, each in its place.

Not carried over: prototype links and Figma variables. Your agent can link the screens again (a click-through prototype) and turn repeated values into a shared system.

Figma’s image links expire after a while: if the paste says an image could not be fetched, copy the layers again in Figma. Pasting needs edit rights on the Saymock file; images and icons need a workspace account (when you try Saymock without one, they are left out).

2. Let your agent rebuild the screens

With Figma’s MCP server and Saymock’s both connected (in Claude Code, Cursor or another client), give the agent the Figma link:

Bring this Figma frame into Saymock as an editable screen, with real text, flex layouts, components and the same images: https://www.figma.com/design/… Check it against a Figma screenshot and fix what differs.

The agent then:

  1. reads the frame from Figma (its outline first, then each part) and saves a screenshot of it;
  2. uploads the images and fonts to the workspace (get_upload_url), without sending them through the conversation;
  3. draws the screen in one create_frame call, using templates for repeated rows and components for shared blocks;
  4. compares it with the screenshot (compare_to_reference), which names the elements that differ and the move that aligns each one, and fixes them.

Reading Figma costs tokens: ask for one screen at a time, or a section, rather than a whole page (why, and how to keep it low).

Which one to use

PasteAgent
TimeSeconds, any number of framesA few minutes per screen
FidelityFigma’s layers as they areChecked against a Figma screenshot
StructureFigma’s structure, absolute layers includedRebuilt: flex, templates, components, responsive
Best forReviewing existing screens, starting quicklyScreens the agent will keep working on, or turn into code

Then

Once the screens are on the board, your team comments on them and the agent handles the comments; ask it for alternatives, a new flow next to them, or the code (design to code). The whole loop, step by step: designing an app with Claude Code.

Questions

Do I need a paid Figma plan to paste into Saymock?

No. You need to be able to open the Figma file and copy its layers. Saymock reads what Figma puts in the clipboard: no Figma connection is needed for the paste.

Does the import keep auto-layout?

Yes. Auto-layout becomes CSS flex with Figma’s spacing, padding, alignment and fill or hug sizes; layers outside auto-layout stay positioned as in Figma.

Are Figma components kept?

Yes. They become Saymock components, and their instances become instances with their own props, so a change to the component reaches every screen.

Can I go back to Figma afterwards?

Saymock does not export to Figma. Screens export as images, PDF or code (React, Vue, HTML with Tailwind classes).

See also

  • Figma MCP tokens
  • Design tools for agents
  • Claude Code
saymock
Product Agents Developers FAQ Pricing Benchmark Figma MCP alternative Connect your agent Use cases Gallery Guides MCP tools Changelog About Contact Sign in

© 2026 Saymock

Legal notice Terms of use Terms of sale Privacy