When you add a library to a file, you’ll be able access its components, styles, and variables and use them in the file. Click the Libraries icon to open the Libraries modal. Locate the library you want to enable. Use the search bar to search your library by name. Click the library to view its assets. In the Libraries modal, you can browse libraries available to you and add them to the current file.
UI kits are a set of libraries curated by Figma and partners. Find and apply styles using the Style and variables picker in the right sidebar. Learn how to apply styles in Figma Design. Drag components into the canvas from the Assets tab in the left sidebar. Learn how to add components to your designs. Variables can be applied to various properties from the right sidebar. Learn how to apply variables to designs.
At the Digital Services Factory (DSF) we believe that sharing our work can benefit other teams developing digital services for the government and ultimately improve the digital experience of citizens with the government. We have therefore created and published a Figma community library file based on the library we use in our team internally to design our services. The Figma library has been created to rapidly create designs and prototypes the gov.cy way. However, it is not intended to be used as a source of guidance or documentation on how to use its design elements.
Our library is built within Figma’s ecosystem and its functionality is subject to any changes made by Figma. You will need to have a Figma account. Get a copy of the library for your team by visiting our Figma community file page and clicking the “Open in Figma” button. A copy of the file will be added to your Figma account’s “drafts” area. To publish the components of the library in your team, you need a paid subscription with Figma. If you don’t have a paid subscription with Figma, you can still publish the library in your team, but this will publish only the styles and not the components. Still, you can use the components of the library by simply copying component variants from the library file to your team’s design files.
To create a design for a page, start with a new instance of a “Page” or a “Page group” component. To make changes to page component instances, first detach the instance. Make sure to create the component instances in the appropriate area. When making changes on component instances, make sure you use the pre-defined colour and text styles. Most of the components of the library have different variants.
Would you be willing to attempt one more troubleshooting step for us? Sometimes with a larger library, Figma has to compile a lil before it really has all the data to publish. Then publish it. Longshot maybe? 🤞LikeAnswerOh. Also are you using the desktop Figma app?
LikeNew MemberJust cleard app cache and everything works, thanks. LikeThat is awesome! Yeah sometimes it gets hung up. Glad it works!
LikeNew MemberCheck for conflicts within the component properties as these will stop the components from publishing. The easiest way to find this is to right click on a component or component group and select Main component > Publish selected components. This will bring up the ‘Publish library’ model in which it lists any “invalid assets” and the reason why they are invalid.
Like many others, I’d like to reference components from our design system or other style files when creating something in Make. This page on the Figma Help site says a Design Library can be attached to each Make file so I can reference components from it, but I don’t see the Browse Libraries link the article mentions to attach it - specifically this direction from the article, “Above your components, click Browse libraries”. The Browse Libraries link isn’t there for me, only a random assortment of components seem to appear. Maybe I need to move the Make file to a different folder on my account? Any advice would be helpful.
Once you have a View-Only Link of a file that is a published Library, all you have to do is open the file while you are logged into Figma to see it as an option within Team Libraries. From there you can enable it.This makes it really easy to create open libraries to share with the design community at large. ❤Open the Library while logged into Figma. I’m using a sketch wireframing kit based on Balsamiq published by queer.tech in this example. Access Vinaigrette here
Press enter or click to view image in full size2. Create a new file within your Drafts and enable the Library. You can now pull in any of the published components & styles.
The components you use will be synced to the original library you pulled the components from. Hello Figma Community and Team, I’m incredibly excited about the potential of Figma Make and have been eagerly experimenting with its AI capabilities. However, I’ve run into a significant roadblock when it comes to integrating my team's comprehensive design library, and I’m hoping to get some clarity on the current limitations and what we might expect in the future.
Our Setup: A Highly-Structured Design System. To provide some context, we’ve invested a substantial amount of time and effort into building a robust and meticulously organized design system within Figma. This isn't just a collection of components; it's a fully-fledged system that includes hundreds of components, meticulous naming conventions, comprehensive variables (design tokens), an interconnected system, and more. The challenge is that the library recognition in Figma Make can be sparse for large, variable-driven libraries. The ideal workflow would be to paste a frame that is already designed and wired up with our library components and variables, and have Figma Make produce code that accurately reflects our established system, including our specific component and variable names. However, the import often recognizes only a small subset of the library, which necessitates manual refactoring to align with production code.
Is this sparse import a known limitation of the current version of Figma Make? How does Figma Make currently "scan" or "translate" a connected library? Is there a specific way we need to structure our components or variables to improve recognition? Is there a plan to enhance Make's ability to ingest a connected design library fully?
Ultimately, the goal is to have the AI generate code that uses our established variable names (for example, --color-primary-500 instead of a raw hex code). This roadmap inquiry reflects the desire for deeper design token integration in Figma Make. Has anyone found workarounds or best practices to improve fidelity of library imports?
Shareable libraries can also be added to your slides in Figma Slides to access components, variables, and styles there. If a component has properties, you can access them in the right sidebar. Variables can be applied to objects only in design mode, and variable modes are available in slides and design mode. If the library includes styles, you can apply them to objects in slides. When someone publishes an update to a component, style, or variable in a library, Figma notifies every file that uses these assets that an update is available. To see updates, you’ll need to accept them from the published libraries.
In summary, libraries in Figma are designed to share reusable design assets like components, styles, and variables. You access published libraries in any draft or team files where you have edit access, enable them in the Libraries modal, and then pull in assets to your canvases. If you’re using Make, expect ongoing improvements around how tokens and complex libraries are imported and utilized in generated code.

| Aspect | Description |
|---|---|
| Access | Enable libraries via Libraries modal; browse and add to current file |
| Assets | Components, styles, and variables from libraries |
| Publishing | Publish updates; accept updates in files using the assets |
| Make | Figma Make may have limited recognition for large, token-driven libraries |
When you access a library in your file, you can add an instance of the component to the canvas. Styles define a collection of properties or settings we want to reuse. Before you can access components, styles, or variables in other files, you need to publish them as a library. If you change a published style, component, or variable, Figma will only apply the changes to instances in the current file. You can access published libraries in any draft files or team files where you have edit access. Don’t have a library to use?