Skip to main content

Figma and design tools · Intermediate · 15 min

Publish a team library and push updates to other files

By Padding · Updated 18 Nov 2026
Figma (web) · November 2026

You will have the Larkfield Clinic components in their own library file, used by the booking app file, with one published change reviewed and accepted on the other side.

On this page

So far the Larkfield Clinic components live inside the booking app file. That works while there is one file. It stops working the day someone starts a second file, say a staff rota screen or a marketing page, and copies the Appointment card across. The copy has no link to the original, and the two drift apart.

A team library fixes this. You keep the main components in one file whose only job is to hold them, publish that file, and turn it on in every file that needs the components. Instances in those files point back to the library. When you change a component and publish again, each file is told an update is waiting, and someone with edit access reviews it and accepts it.

That last part is the one people miss. Publishing does not push changes into other files on its own. It offers them. This tutorial walks through the whole loop once, from moving the components to accepting a change, and shows how to write a publish note that tells the person on the other side what they are accepting.

Step 1 · Put both files in a team project and make a backup

Libraries are published from files in a team project, not from your drafts. If the booking app file is in Drafts, move it: open the file menu from the file name at the top of the left sidebar and use the option to move the file, then choose a project in your team. Name the project something plain, such as Larkfield Clinic.

Next, duplicate the booking app file from the same menu and rename the copy Larkfield booking app (backup 18 Nov). You are about to move main components between files, and Figma says that move cannot be reversed with undo or by restoring an older version. A duplicate is your way back if something goes wrong.

Finally, in the same project, create a new Design file and call it Larkfield Components. The library takes its name from this file, so pick the name you want people to see when they search for it. Give it one page called Components for now.

Check it worked

Open the Larkfield Clinic project in the file browser. It holds three files: the booking app, its dated backup and Larkfield Components. None of them is listed under Drafts.

Step 2 · Publish the components where they are now

Figma can move a component from one file to another and keep every instance linked, but only for components that are already published. So the first publish happens from the booking app file, as a stepping stone.

In the booking app file, open the Assets tab in the left sidebar and click the Libraries icon. The Libraries modal opens. Under This file, click Publish next to the file name.

Figma asks for a description and lists the components that will be published. Leave them all ticked and write a short, honest note: Temporary publish so components can move to Larkfield Components. Click Publish and wait for the confirmation.

If the Publish button is greyed out, the file either has no components yet or has nothing new since its last publish. Check that your Appointment card is a main component (four-diamond icon in the layers panel), not a frame.

Check it worked

Open the Libraries modal again. Under This file, the booking app is shown as published, and there is no list of unpublished changes waiting.

Step 3 · Move the main components into the library file

Go to the Components page of the booking app file. Select every main component you want to share, for example the Appointment card, the button and the input field, and cut them (Ctrl X or Command X).

Switch to Larkfield Components, click an empty part of the canvas so nothing is selected, and paste (Ctrl V or Command V). Arrange them with space between them and put each in a section or under a text heading so the page reads as a catalogue.

While they are in front of you, check two things before anyone else depends on them:

  • Names. The layer name of each main component is the name people will search for in the Assets tab. Appointment card is findable; Card v2 final is not.
  • Internal pieces. If a component exists only to build other components, such as a small icon slot, you can keep it out of the published list later with Hide when publishing. Do not delete it: other components use it.

Back in the booking app file, the instances on Home, Pick a time and Booked still look the same. They are still pointing at the components you just cut, and will stay that way until the library publishes and you accept the update.

Check it worked

Larkfield Components shows every main component on its Components page, each with the four-diamond icon in the layers panel. The booking app's Components page is empty, and its screens still show the cards.

Step 4 · Publish the library with a note people can use

In Larkfield Components, open the Assets tab, click the Libraries icon and, under This file, click Publish.

For each moved component, Figma asks whether it should move to this file. Choose Move to this file. That is what keeps the existing instances connected; the other choice leaves you with unlinked copies.

Untick anything you marked as internal, or right-click it in the list and choose Hide when publishing. Then write the description. Treat it as a message to someone who did not see you work and has to decide whether to press Update. A useful note answers four questions:

  1. What changed. Name the components, not "various fixes".
  2. Why. One clause is enough.
  3. What might look different. Size, spacing or anything that could push other layers around.
  4. What to do. Usually "accept", sometimes "check your overrides on X first".

For this first library publish:

Text
First publish of Larkfield Components.
Moved from the booking app: Appointment card, Button, Text input.
Nothing looks different; instances should relink with no visual change.
Action: accept the update in the booking app file.

Click Publish and wait for the confirmation.

Check it worked

Open the Libraries modal in Larkfield Components. Under This file, the library shows as published with no unpublished changes. Open the file's version history from the file menu and your note appears against the publish.

Step 5 · Relink the booking app to the library

Go back to the booking app file. The Libraries icon now carries a blue badge, which means updates are waiting. Click it and open the Updates tab. Turn on Show updates for all pages, because by default the list only covers the page you are on, and the cards live on several screens.

Each moved component is listed. Click Update all. The instances now point at Larkfield Components instead of the components you cut.

Figma enables the library in this file as part of the move. To confirm, stay in the Libraries modal and look at the libraries added to this file. If Larkfield Components is not there, find it with the search bar, click it and choose Add to file. Adding a library applies to everyone who opens the file, so collaborators see the same set.

While you are in the modal, the booking app's own stepping-stone publish has nothing left in it. Leaving it published does no harm, but an empty library in the team list confuses people searching for components. If you want it gone, look for the option to unpublish it next to the file under This file.

Check it worked

Select the Appointment card on Home. In the right sidebar, the instance section names Appointment card and shows that it comes from the Larkfield Components library, not from this file. In the Assets tab, the components appear under Larkfield Components.

Step 6 · Change a component in the library

Now make a real change. In Larkfield Components, select the main Appointment card and do two things:

  • change the corner radius, for example from 16 to 12
  • add a small status label above the service name reading Confirmed, so patients see at a glance that a booking went through

Look at the booking app file in another browser tab. Nothing has changed there. Edits to a library stay inside the library file until you publish them, which gives you room to try things, undo, and get a second opinion before anyone else sees the change.

Before publishing, ask what could go wrong on the other side. The new label makes the card taller. On a screen where the card sits in a fixed-height area, that could overlap the content below it. Note this down; it belongs in the publish note.

Check it worked

The main Appointment card in Larkfield Components has the new radius and the Confirmed label. The Libraries icon in Larkfield Components shows unpublished changes. The cards in the booking app file still look as they did before.

Step 7 · Publish the change and review it on the other side

In Larkfield Components, open the Libraries modal and click Publish under This file. Only the Appointment card is listed as changed. Write the note:

Text
Appointment card: added a Confirmed status label above the service name;
corner radius 16 → 12 to match buttons.
The card is about 24px taller. Check Pick a time, where it sits above the time list.
Text overrides (date, clinician) are kept.
Action: accept, then check spacing on Pick a time.

Publish, then switch to the booking app file. The blue badge is back on the Libraries icon.

This time, look before you accept. Select the card on Pick a time. In the Design tab of the right sidebar, click Update available, then Review update. The comparison opens side by side; switch to Overlay and drag the opacity slider to see exactly how far the card grows. Use the arrows to step through the other instances in the file.

If the change looks right, click Update all. If one screen needs fixing first, update that instance on its own with Update instance, fix the spacing around it, and accept the rest afterwards.

Check it worked

Every Appointment card in the booking app has the Confirmed label and the new radius. The Booked card still shows the date you overrode earlier, such as "Thu 11 Dec · 14:15". The Libraries icon in the booking app no longer has a badge.

Next steps

You now have two files sharing one set of components: Larkfield Components holds and publishes them, and the booking app uses them and decides when to take changes. Every later change follows the same loop: edit in the library, publish with a note, review where it is most likely to break, accept.

  • Learn which overrides survive a library update and which are lost in /tutorials/override-component-instances-safely.
  • Let teammates review a component change before you publish it with /tutorials/share-a-figma-file-and-collect-comments.
  • Make your library components easier to use in other files with /tutorials/add-component-properties-in-figma.
  • Go back to the basics of main components and instances in /tutorials/make-your-first-figma-component.

Need this done for you?

Padding does this work for growing companies, from the first diagnosis to a system that keeps working.

Digital Transformation

Get new tutorials

New tutorials, about twice a month.