Figma Make is Figma's prompt-to-code prototyping tool, transforming text prompts or existing Figma designs into functional React prototypes. Powered by Anthropic Claude 3.7 Sonnet (Gemini 3 Pro added Nov 2025). Launched Config 2025 (May 7), GA July 24, 2025. Now available in Figma for Government with FedRAMP Moderate authorization (Dec 2025).
The core tension: Figma Make is a prototyping tool masquerading as a code generation tool. It generates working React prototypes quickly—that part works. The problem is the dead-end architecture. Code exports are non-functional, there's no GitHub integration, and the ecosystem lock-in is by design.
Core strength: design context depth—native access to Figma's design primitives (layer hierarchies, components, auto-layout rules, variables, spatial relationships) that no other tool matches. Make Kits (early access) allow importing production React NPM packages, enabling prototypes that use exact production code.
Strategic reality: The Figma MCP server enables Cursor, Windsurf, and Claude Code to read Figma designs directly. This is arguably more valuable than Make's broken code export. The emerging workflow—design in Figma Design, use MCP to give context to agentic IDE, generate production code in Cursor/Windsurf—may render Make a curiosity rather than a core product.
Critical limitation: code export lacks package.json, outputs single files with undocumented dependencies, and requires substantial restructuring for project integration. Independent review: "dead end by design" for production workflows. Developer attempting code extraction resorted to reverse-engineering the .make binary format (Jan 2026).
Adoption & Proof Points
- Adoption signals: ~30% of customers spending $100K+ annually use Make weekly (CEO Dylan Field, Nov 2025). 95% of Fortune 500, 100% of Fortune 100 use core Figma platform. 450,000 paid customers, 13M+ monthly active users. 1,031 customers >$100K ARR (47% YoY growth). Figma IPO July 2025 (NYSE: FIG).
- Named integrations: ServiceNow partnership claims 80% reduction in initial UI implementation time using Make's MCP integration. 100+ federal, regional, and local government agencies worldwide.
- Financials: $749M revenue (2024), 48% YoY growth. Q1 2025: $228M revenue (46% YoY). 91% gross margins. Net dollar retention ~132% (custom calculation excluding churned customers).
- Pricing: Seat-based with usage-based AI credits. Professional $16/mo (3,000 credits), Organization $55/mo (3,500 credits), Enterprise $90/mo (4,250 credits). Credit limit enforcement begins March 18, 2026. Subscription credits March 11, 2026, pay-as-you-go Q2 2026.
Recommended Use Cases
- Rapid prototyping and concept validation (10-20 iteration cycles)
- Internal tool MVPs and proof-of-concepts
- Testing interaction patterns before developer handoff
- Stakeholder review prototypes for design-led teams
- Teams already invested in Figma wanting natural extension into prototyping
- Organizations needing compliant prototyping (SOC 2, ISO 27001, FedRAMP Moderate) with design system fidelity
- Teams with production React design systems (via Make Kits)
- Federal agencies requiring FedRAMP-authorized prototyping
Risks & Limitations
- Code Export is Non-Functional (Critical)
- Downloaded code lacks package.json—no way to install dependencies
- Missing config files: tailwind.config.js, tsconfig.json, vite.config.ts
- All output dumps to single file regardless of project complexity
- Version numbers embedded in imports break builds (e.g., @radix-ui/react-switch@1.1.3)
- Users report 24+ hours trying to get exports running locally
- Figma API returns "File type not supported" for Make files—no programmatic access
- Community building third-party VS Code extensions just to scaffold exports
- One developer reverse-engineered the .make binary format (Jan 2026) to extract code
- Ecosystem Lock-In (By Design)
- Make files cannot export back to Figma Design
- Published outputs deploy only to Figma hosting
- No GitHub connection (unlike v0, bolt.new, Lovable)
- React + Tailwind + Shadcn UI only—no Vue, Angular, Svelte
- Forum confirms: no framework conversion planned (Dec 2025)
- AI Behavior is Unpredictable
- Overwrites manual code changes via chat without warning
- Makes unsolicited UX decisions (changing radio buttons to selects)
- No undo/rollback when AI breaks a working prototype
- User feedback: "When it says it fixed the issue, it in fact did NOT fix the issue, AND it also decided to edit something entirely unrelated"
- Credit Crunch Coming (March 2026)
- Power users report hitting 80-100 prompts daily during normal 8-hour workdays
- Current limits: 3,000-4,250 credits/month depending on plan
- Enforcement begins March 18, 2026
- Forum feedback: "Increase the limit by tenfold (10x) would be a more acceptable limit"
- Risk: pushes heavy users to competitors
- Other Limitations
- Not HIPAA compliant (explicitly prohibits PHI storage)
- No SSR support—client-side React rendering only
- 58/100 comprehensive developer review score
- "Dead end by design" for production workflows
Capabilities & Integration
Agentic depth: Intelligent copilot, not autonomous agent. Generates complete working prototypes from prompts but requires user guidance and iterative refinement. Can start from scratch, import Figma Design frames, or upload images/screenshots. Known to overwrite manual code changes and make unsolicited UX decisions without permission.
Context handling: Native access to Figma design primitives—layer hierarchies, components, auto-layout rules, variables, spatial relationships. Make Kits (early access) import production-ready React NPM packages directly into Make workspace—prototypes use exact same code as production apps. External connectors (Asana, Jira, Confluence, GitHub, Linear, monday.com, Notion) pull PRDs, tickets, and product documents for fuller context. Variables support multiple modes (light/dark theming), scoping, and REST API sync.
Model flexibility: Claude 3.7 Sonnet primary, Gemini 3 Pro (Nov 2025). Figma states plans for additional models. Third-party vendors contractually prohibited from using customer data for training.
Integration surface: MCP Server available both remote (mcp.figma.com/mcp) and local desktop modes. Enables Cursor, Windsurf, Claude Code, VS Code Copilot, Codex integration. Remote server eliminates desktop app dependency. Code Connect maps Figma components to production repo code (React, React Native, SwiftUI, Jetpack Compose, Vue/Angular via Web Components). GitHub push integration available.
Framework support: React with Tailwind CSS and Shadcn UI only. TypeScript supported. No Vue, Angular, Svelte, or alternative CSS approaches—confirmed no conversion path planned (Dec 2025 forum).