Introducing branching: space to iterate and explore freely | Figma Blog (opens in new tab)

Figma introduced branching in beta to help large design teams experiment without risking changes to shared files. The feature combines the freedom of isolated exploration with Figma’s multiplayer collaboration, while keeping the main file as the approved source of truth. Branches are auto-saved and can later be merged into the main file by editors.

The challenge of decentralized design systems

• Design systems were spread across teams and tools, creating inconsistencies and forcing designers to switch contexts.
• Centralized systems improved reuse and efficiency but introduced governance challenges.
• In large systems such as Netflix’s Hawkins, many contributors may update files, even when the latest changes are not approved for production.
• Teams needed a way to protect shared libraries while still allowing designers to explore new ideas.

Branching built around simplicity

• Figma considered traditional workflows involving commits and nested branches too complex.
• The product adopted two principles: simplicity and consistency.
• Branches work within Figma’s existing multiplayer model, retaining real-time collaboration.
• Work is automatically saved, eliminating the need for explicit commits.
• Designers can create a branch from any file, experiment safely, and merge approved updates into the main file.

Future plans and availability

• Figma planned to expand branching with features such as reviews.
• The company was also exploring a unified approach to versioning across branching and multiplayer workflows.
• The beta initially launched for Organization-plan customers, with access granted gradually.

Branching is intended to let organizations centralize their design systems without limiting experimentation. Teams managing shared libraries should use branches for exploratory work and merge only reviewed, approved changes into the main file.