As a design systems designer with a Design team of 75+ designers

I want to bulk swap an entire component library with a similar but updated library

So that when I’m syncing Figma Libraries between two or more separate Figma Organizations, I can easily replace a whole component library at the library level instead of needing designers to swap libraries per Figma project file.

• This feature would use some existing workflows and interfaces for choosing, comparing, and merging/swapping components in bulk.


• This swap should be treated as publishing a new update to the existing library and still require Designers to “accept” the changes.


• New components or existing components with a different name, should be treated as introducing a new component into the library.

Open Questions:

• How are new components handled within the updated library after the swap?


• How are design elements that aren’t components handled within a library swap?

To give a specific example of how this scenario appears.

Organization A is an open source project that publishes a Figma library

Organization B relies on this library and uses it to support their ongoing work.

When Org A has updates, Org B needs to download the library and swap it with the one they were using before.