Figma Make Adds Codebase Integration and Git-Style Version Control.

Figma is expanding its Make product with capabilities that blur the line between design and development. The company announced on LinkedIn that users can now bring their entire codebase into Make, edit code with precision, and perform git-style actions like branching, committing, and shipping. The rollout is live in the Beta desktop app.

The move positions Make as more than a prototyping tool. By integrating codebases directly into the workflow, Figma is giving teams a way to iterate on production code without leaving the design environment. This addresses a longstanding pain point: the handoff between designers mocking up features and engineers implementing them in actual code.

The core update centers on bringing your existing codebase into Make. Once imported, you can make targeted code changes directly in the app. Figma describes these as "precise changes," suggesting the tool supports line-level edits rather than generating entire components from scratch.

This fits with Make's recent addition of custom skills, which let teams define reusable workflows. Combining custom skills with codebase editing means teams can standardize how they apply design tokens, component structures, or accessibility patterns across a live codebase.

The announcement also highlights branching, committing, and shipping. These are developer staples, borrowed from version control systems like Git. In Make, you can now create a branch to test changes, commit those edits with a message, and push the code to production.

For teams already using tools like GitHub or GitLab, this integration likely hooks into existing repos. Figma has not detailed whether Make supports pull requests or merge conflict resolution, but the presence of branching suggests some level of version control parity.

This is a significant shift. Design tools have historically focused on visual states, not code history. By adopting git conventions, Figma is acknowledging that modern design work increasingly involves touching code directly, especially as AI-assisted tools like Cursor, Bolt, and Lovable make it easier for non-engineers to write and iterate on code.

The features are rolling out now, but only in the Beta desktop app. Figma has not announced a timeline for general availability or web support. Desktop-only releases are common for features that require deeper system access, such as filesystem integration or local repository management.

Teams interested in testing should download the Beta app from Figma's site. The LinkedIn post links to an announcement page with additional details, though the page was not accessible at the time of this writing.

Figma has been steadily expanding Make since its launch. Earlier this year, the company introduced a design agent embedded directly into the canvas, allowing users to prompt AI for layout changes or component generation. The addition of codebase editing suggests Figma sees Make as a bridge between design intent and production code, rather than just another prototyping layer.

This also aligns with a broader industry trend. Tools like v0, Replit, and Windsurf are collapsing the distance between idea and implementation. As we tested in our comparison of Claude Design, Figma Make, and other AI coding tools, the real value lies in how quickly you can move from concept to functional code. Figma's approach prioritizes design fidelity first, then lets you refine the underlying code.

For small teams or solo builders, this could streamline workflows significantly. Instead of prototyping in Figma, exporting specs, and recreating the design in a separate codebase, you can now design, code, and version in one environment. Whether that replaces dedicated IDEs or simply reduces friction in the handoff process remains to be seen.