# How (and why) we built branching

DevFeed: [How (and why) we built branching](<https://devfeed.tech/articles/how-and-why-we-built-branching-9750.md>)

Original publisher: [Read original article](<https://www.figma.com/blog/how-and-why-we-built-branching/>)

Author: John Fuetsch

Published: 2021-10-12T00:00:00Z

Content type: article

Language: en

Sources: [Figma Blog](<https://devfeed.tech/sources/figma-blog.md>)

Topics: [Figma](<https://devfeed.tech/topics/figma.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [design](<https://devfeed.tech/tags/design.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [explore](<https://devfeed.tech/tags/explore.md>), [scale](<https://devfeed.tech/tags/scale.md>)

## AI overview

Figma explains how it built branching to support collaboration at scale. Branches provide exploratory spaces for designers to iterate without changing the main file until work is ready and approved, while preserving approved designs and supporting experimentation, design libraries, and stakeholder previews.

## Source excerpt

In April, we introduced branching as a way to enable collaboration at scale. Today, branching is broadly available on our Organization plan.