Libraries make it easy to reuse pages, sections, and components across your projects. They are essential for:
Ensuring design consistency.
Speeding up collaboration and production.
Making ready-made, up-to-date assets accessible to your entire team.
Creating a Library
To create a library, you will start with a regular Vev project that contains the pages, sections, or components you intend to share.
Once the project is ready, you can "push" these assets to turn them into a library, making them available in the Add menu for your team or across all teams (requires Org plan).
Steps to Create a Library:
Open the Add menu in your project.
Click Manage libraries.
Click Use as library.
Choose the scope: push the library for your team or across all teams.
Click Push update.
Create from a Template
If your account has custom templates created using Vev’s outdated template feature, you can easily migrate them into the new Libraries workflow. This allows you to keep your existing designs while gaining the ability to sync updates and manage assets across teams.
Go to the Templates page on the Dashboard.
Identify the template you want to convert.
Click the three "dots" menu.
Select "Create library from template".
Select the team and folder the template should be located in.
Select whether to push the template assets to all your teams or to the team you have moved the template to.
The template page and its sections will now be available to use across projects as a library to the team(s) you have pushed the assets to.
ℹ️ When you convert a template, Vev duplicates the template content into a new, regular project. The existing template file remains in your account, ensuring your source content stays safe while transitioning.
Adding Assets from a Library
Because Pages and Sections/Components serve different functions, they are accessed from different locations within the Vev Editor.
Adding Pages
Library pages are found within the Pages panel area, where you normally add more pages.
Click the "+" icon
Select "Library page"
Browse your available libraries and select a page to add to your project.
Adding Sections and Components
Sections and Components are found in the primary Add menu.
Open the Add menu on the left-hand side.
Browse libraries available to you.
Drag and drop the section or component onto your canvas
Pushing Updates
When you make changes in a project that is used as a library, you can push those updates to keep the library assets current for everyone.
Option 1: Push from the Add Menu
Open the Add menu.
Click Manage libraries.
Click Push update to open the confirmation modal.
Click Push update again to confirm.
Option 2: Push from the Top Bar
Click Push to library (located next to the Publish button).
In the modal, click Push update to confirm.
How Updates Affect Assets
The way a library update is handled depends on the type of asset used in a project:
Pages and Sections
Behavior: Pages and sections added from a library are disconnected instances. When they are added to the canvas, they do not automatically sync the latest updates when a new library push occurs.
Best For: Assets that serve as a starting point and need to be freely edited and adjusted for each project. You will always receive the latest version when adding a new page or section.
Main Components
Behavior: Main components added from a library are connected to the library. When a new library update is pushed, users will receive an "Update required" notification in the Layers panel and in the Add menu.
Best For: Providing sections or smaller components that should only allow content updates (text, images, videos, shapes). This ensures strict design consistency across all usage.
Managing Library Access
How you structure your library projects on the dashboard is critical, as the library's location and sharing scope affect how other users can access and use the libraries.
Pushing Library to a Single Team
This is the standard approach for accounts using one team or for sharing assets within a specific team only.
Sharing Scope: The library is pushed to your team only by storing the library project within that specific team, shared from the push library update modal from the library project.
Access: Any member of the team where the library project is located will be able to access and use the library from the Add menu in other projects in that team space.
Pushing Library Across Teams (Org Plan Required)
This approach allows you to share a library across your entire organization.
Sharing Scope: The library is pushed across all teams by selecting it from the push library update modal in the library project.
Organization: Create a new or dedicated team to gather and organize your cross-team library projects.
Project Location is Key: The team where the library project is located is responsible for editing and pushing updates.
Access: All other teams can drop library assets in their projects. You can then control which specific teams have access using the Managing Library Access to Selected Teams steps below.
Closed Team for Controlled Updates
For extra control over who can modify your library, use a closed team to house the library project. This ensures that only designated team members can edit the library and push updates across to all teams. 🔗 Learn more about teams.
Manage Library Access to Selected Teams
Only users with an Admin or Owner role can manage which teams have access to use specific libraries.
Go to Account settings from the dashboard
Click Libraries in the left panel
Locate the library and click Manage access
Toggle team access on or off
Click Save
Frequently Asked Questions (FAQs)
Why am I seeing an "Update required" in the Add menu?
The "Update required" tag indicates that you are using components in your project that are not up to date with the latest library push. You must update your existing components to the latest version before you can add the component from the library again.
Why can't I or my team member find the library in the Add menu?
Library access from the Add menu is determined by the team space the library project is located in, and if the library is pushed to one team or to all teams. If the library isn't showing as expected, please check which team the library project is located in, and if it is pushed to that team only, or if it is shared across all teams.
Why are the sections I have pushed before no longer Main Components?
If you used the Libraries feature in early access, you may have relied on an automatic conversion that turned sections into Main Components during the push. This automatic conversion has been removed.
If you want your sections to behave as Main Components, you must now manually convert sections into Main Components on the canvas before pushing the library update.