Skip to main content

​
Getting started

Figr is built for teams designing on top of a product that already exists. It learns your product from Context Pods and your Design System, then designs inside them: your components, your tokens, your flows and your states. The output exports to Figma with auto layout and your library components, or goes to code through Figr MCP, so designers refine it instead of rebuilding it.
A first useful setup takes minutes: one recording, a few screenshots or a Figma file. A full setup for a complex product, with a design system and several Context Pods, takes longer and pays off on every project after.Enterprise teams get onboarding with the Figr team. Talk to us to set it up.
No. Figr asks questions, explores directions and explains its reasoning. PMs use it for flows, edge cases and first passes. Designers use it to explore faster and hand off cleaner work.
Yes. Figr takes Figma, Storybook, npm packages and GitHub as design system sources, and connects to tools like Notion, Confluence, Linear, Asana, Slack, Mixpanel and Amplitude. Output goes to Figma, to code, or to coding agents like Claude Code, Cursor, VS Code and Codex.

​
Features

Context Pods hold what Figr knows about your product: recordings, files, notes, links and instructions. Figr also keeps memory of product decisions, constraints and preferences across your work, pulls relevant decisions from earlier chats in the same pod, and shows which memories or sources it used. See Context Pods.
Images (PNG, JPG, WebP, GIF, SVG), videos (MP4, MOV, MKV, WebM), PDFs, Markdown, text, CSV, JSON, CSS, HTML and Mermaid files. Word, Excel and PowerPoint files aren’t supported, so export them to PDF first. You can also record a walkthrough inside Figr or capture pages with the Figr Capture Chrome extension.
Yes. Teammates see each other’s live cursors on the canvas, comment on designs, and run separate chats in the same project. Share a project with view or edit access, and share Context Pods and design systems across the workspace.
Yes. Figr designs for web and mobile, and builds prototypes in React or Angular.
Export screens to Figma with auto layout and your components, download the code, or click Open in coding agent to connect Claude Code, Cursor, VS Code or Codex through Figr MCP.

​
Plans and credits

See current prices and annual options on the pricing page.
Credits are used based on the work each message does. A large multi-screen prototype uses more than a quick question. You can see usage per member in Settings.
Yes. Enterprise includes SSO, roles and permissions, domain auto-join, onboarding with the Figr team, and admin controls for seats and credits. Admins can move unused credits between seats and request seats or top-ups inside Figr. Email hi@figr.design or talk to us.
Yes. You keep access until the end of your billing period.

​
Security and admin

Figr is SOC 2 Type II compliant, and your data is encrypted in transit and at rest. Enterprise plans include SSO. Every workspace can choose EU data residency. See Data protection for details.
Yes, on Enterprise plans. Figr supports SAML and OIDC, set up by a workspace owner or admin.
A connector uses the account you connect it with, and only reaches what that account can reach. Some connectors ask for write access as well as read, so review the permissions when you authorize. For GitHub, you choose exactly which repositories Figr can access. You can turn any connector off at any time.

​
Getting help

Check these docs first, then email hi@figr.design. We reply within 24 hours. Enterprise customers get priority support.
Every week or two. See the changelog for what’s new.
Yes. Email us, or use the feedback option in the app.

Still have questions?

Reach out to us at hi@figr.design or through our contact page.