Git Like versioning

Hey @Pavels_Amosovs! You’re correct that branching & merging is currently limited to beta testing for individuals on our Organizations plan.

We don’t have any immediate plans to roll this beta out to users on our Professional plan, but we’ll pass the feedback along that this is something you’d like to see.

Also disappointed this is only for org users. This would be such a useful feature for me as a solo designer on a small team plan. I’d maybe be open to paying a little more to get access to it, but not so much to switch to an Org plan when I’m the only designer at my company.

Figma shouldn’t just be for big teams.

I created a specific request to make branching available for non-org teams.

Thanks. I think many designers here will agree that the branching feature should be available on the Professional plan when it goes out of beta. The price difference between professional and org plans is just too big but the branching would be hugely beneficial for so many designers who have subscribed to the professional plan.

I would just like some type of version control on Figma projects. For example, we had someone delete a component and had to get the original designer to place it back in. Would have been nice to just identify when it was deleted and copy and past it from that version.

Hi @Matthew_Beasley, there are currently two options:

1. Version history;
2. Branches (Beta, for Organization plan).

The thing is we have basic version control in the forms of History and Branching but it’s still difficult to VISUALLY identify changes or for them to be otherwise highlighted.

Clicking through the file history can show large changes but what about smaller ones? Changes across multiple pages? It’s useless for that. Branching is great when you know you’re going to do a major or discrete update but what about after the fact?

With multiple people editing everything, it would be nice to have a visual way to inspect the history. That way we could quickly demystify who did what, when; or we could watch the evolution of a single component.

For instance in a design system very much in progress, someone identified some inconsistencies in the type ramp styles. Did that arise from edits that I did? Something that I missed? Another person? When did they happen? If I could just zoom into the type ramp and poke at the objects with some history spyglass tool, I could answer all those questions in a few seconds. It’s useful to learn these things so that future problems can be prevented.

If instead I try going through the whole document History, that could take hours and I still might not see when the change occurred.

The “Branch review” screen is a great start in that direction but:

1. I can only zoom in to 100%.
2. No pinch zoom / pan control.
3. Nothing can get highlighted on the previews.
4. The change detail list is view only. No selection to highlight in the canvas. No ability to disregard individual changes.
5. It’s only available to see changes done on a branch. No screen like this for seeing file history changes.

Love the fact that I can branch on a file. Only wish I could lock the main “prod” file (esp to a library) so that all editors must use branches – ultimately keeping autosaves of other team members from effecting other lower branches.

This is so important. Even the design leads often forget that they are on the main file instead of a branch and end up making huge changes to the entire file without realizing.

+100 For this!