FIGMA May 27, 2026

Figma Make Can Now Edit Your Production Codebase

General Availability

Figma Make is now generally available with production repository connections and precise editing controls.

The News

Figma announced on May 27, 2026 that Figma Make can now edit production codebases — a significant expansion from its prototype-only origins.

Teams can now use Figma Make as a visual surface for building and editing real software by connecting to production or sandbox repositories via the Figma desktop app.

New Capabilities

🔗 Repository Connection

Connect Make to production or sandbox repositories via GitHub integration in the Figma desktop app.

🎨 New Editing Panel

Precise design adjustments for layouts, colors, font sizes, and effects with real-time code sync.

What This Means

✓ Design-to-code workflow: Designers can now make changes in Figma that directly update production code — no more manual handoff or translation errors.
✓ Visual development: Non-technical team members can contribute to real products through a visual interface, with AI handling the code generation.
✓ Iteration speed: Changes that previously required developer time can now be made directly by designers, with AI translating intent to code.

Workflow Example

Designer opens Figma Make and connects to GitHub repository
Make imports the production codebase as a visual canvas
Designer makes changes using visual tools or natural language prompts
Figma Make generates code changes and creates a pull request
Developers review, approve, and merge — or request adjustments

Competitive Context

Figma Make's evolution positions it against several categories of tools:

• Traditional design tools: Sketch, Adobe XD (Figma already won this battle)
• AI code generators: Cursor, GitHub Copilot, Claude Code (now competing directly)
• Low-code platforms: Webflow, Bubble (different approach, similar goal)
• Design-to-code tools: Anima, Builder.io (Figma has the home-field advantage)

Why This Matters

This is a significant step toward democratizing software development:

• Designer empowerment: Designers gain direct agency over implementation, not just mockups
• Developer focus: Engineers can focus on complex logic while AI handles routine UI changes
• Speed vs. quality: Teams must balance rapid iteration with code quality and technical debt
• Role evolution: The line between "designer" and "developer" continues to blur