0
100
200
300
400
500
600
700
800
900
1000
1100
0
100
200
300
400
500
600
700
800
900
1000
1100
Guide · Files, sharing & libraries

How to Create and Publish a Library in Figma

A Figma library is a regular design file that you publish. Put your components, styles or variables in one file, then open the Assets tab, click the Libraries icon, and under This file click Publish. Add a description, untick anything you want to leave out, and click Publish again.

Publishing needs a paid plan, a Full seat and edit access to the file. The file must hold at least one component, style or variable, and it can't sit in your drafts: move it to a project folder first.

Updated Sep 24, 20265 min read
On this page
6 steps

Quick steps

1

Build the assets in one file

Create the components, styles and variables you want to share in a single file. Give the file a clear name, such as Website design kit, so people know what it's for.

2

Move the file out of drafts

If the file is in your drafts, move it into a project folder. Draft files can't be published.

3

Open the Libraries modal

Open the Assets tab in the left sidebar and click the Libraries icon.

4

Click Publish

In the This file section, click Publish.

5

Describe and review

Add a description of the library or a summary of changes, then untick any assets you don't want to publish. On Organization and Enterprise plans, choose where to publish.

6

Publish

Click Publish. Teammates can now add the library to their files from the same Libraries modal.

01

What you need before you publish

  • A paid plan. Publishing is available on all paid plans. Starter can't publish.
  • A Full seat with edit access to the library's source file.
  • At least one component, style or variable in the file.
  • A project folder. Files in drafts must move to a folder before they can be published.
02

How to set up a Figma component library

Keep the source file tidy before the first publish, because everything in it becomes what your team searches for. A layout that works for most teams:

  1. Foundations first. Set up colour, spacing and type as variables or styles. Components should use them, not raw values.
  2. One page per group. Buttons, inputs, navigation and so on, so the file is easy to maintain.
  3. Components with properties. Use variants for states and sizes, and component properties for optional icons and labels, so nobody needs to detach.
  4. Clear names. Consistent names like Button/Primary make components easy to find when other people search Assets.

If you're new to building components, start with how to create a component in Figma.

03

What your team does after you publish

Publishing makes the library available. It doesn't switch it on anywhere. Each file that needs it has to add it: Assets → Libraries icon → find the library → Add to file. People need at least can view access to the library file to use its components, styles and variables. Anyone with can edit access to a file can add or remove libraries for it, and the change applies to everyone who opens that file.

If someone later removes the library from their file, the assets they already placed stay on the canvas. They just can't pull new ones from Assets until they add it back.

04

Keep some assets private

Not everything in a library file should reach the team. Working drafts, internal building blocks and test components can stay local. Right-click the asset in the library modal and choose Hide when publishing, or untick it in the Publish dialog. Variables have their own Hide from publishing option in the Edit variable dialog.

05

How to publish library updates

Updates use the same flow: Assets → Libraries icon → This file → Publish. Write a short summary of what changed, since that's what your team reads before accepting. After you publish, people using the library see a blue badge on their Libraries icon, and the tooltip reads Review library updates. Their instances change only when they accept.

If a component you expect is missing after publishing, check the Invalid section of the Publish modal. Assets with problems are listed there and skipped. More causes in Figma library not showing.
06

Is there a shortcut to publish a library?

Figma's help center doesn't list a shortcut for the Publish button. The fastest route is to open the panels from the keyboard and click from there.

Open the Assets panelMac⌥2WindowsAlt2
Open LibrariesMac⌥3WindowsAlt3
Create componentMac⌥⌘KWindowsCtrlAltK
Publish libraryMac—Windows—
07

How to add a design kit in Figma

A design kit works like any other library. If it's already published in your team or organization, open Assets → Libraries icon, find it and click Add to file. If you have the kit as a file of your own, move it into a project folder and publish it with the steps above, then add it to the files that need it.

08

Document the library for the people using it

A published component without documentation gets misused. Before a big publish, put a spec next to each key component: anatomy, spacing and a table of its properties. Autospec, our plugin (free to start), generates those frames from a selected component, and resolves bound variables so the legend shows token names. The method is in how to make Figma design specs.

Ranked listThe best Figma plugins for design systems in 2026
FAQ

Frequently asked questions

Can I publish a Figma library on the free plan?

No. Publishing a library is available on paid plans and needs a Full seat with edit access. On Starter, you can still enable libraries for draft files, but that shares styles only.

Why can't I publish my Figma library?

Check four things: the plan is paid, you have a Full seat with edit access, the file contains at least one component, style or variable, and the file isn't in your drafts.

How do I stop some components from being published?

Right-click the asset in the library modal and choose Hide when publishing, or untick it in the Publish dialog before you click Publish.

Do library updates change other files automatically?

No. Users see a Review library updates prompt on the Libraries icon and choose when to accept. Until they do, their instances keep the previous version.

Keep learning

More in Files, sharing & libraries

All guides in Files, sharing & libraries