Assets & tasks / MERCHANT WORKFLOW
Should You Swap an Entire Figma Brand Library or Replace Individual Components?
Use Figma's Swap library workflow when a campaign contains many published assets that have intentional name-matched counterparts in another library. Figma matches components, styles, and variables by name; unmatched assets remain connected to the original library. For a small number of exceptions, manually swapping individual instances may be clearer than a broad library replacement.
Decide whether the campaign is built for a library swap
Figma's Swap libraries instructions describe replacing published library components, styles, and variables with counterparts from another published library. The assets must originate from a different library; local assets in the current file are not eligible for this operation.
The matching mechanism uses asset names, including component sets and their variants. An asset with a visually similar design but a different name may not match. Conversely, matching names alone do not prove that two assets carry the same approved commercial meaning.
Figma explicitly states that unmatched assets remain connected to the original library. This is a critical handoff risk: a campaign can appear mostly rebranded while retaining an old client's logo or color variable.
Before swapping, compare the two published libraries and identify the assets that should have counterparts. Record intentional exceptions instead of treating every unmatched item as an error.
Review matches before committing
In Figma, open the Libraries modal from Assets, select This file, choose the source library, and use Swap library. Select the replacement library and inspect the matched assets.
Figma documents checkboxes for selecting which matches to swap. Use that review to exclude assets whose matching names conceal different purposes.
After the swap, inspect the resulting components, styles, variables, and product content. If an asset has no match, choose whether to leave it, delete it, or manually swap its instance using the documented instance controls.
A library swap is not a product-identity verifier. A Blue mug image can remain wrong even if the component and color styles now come from the correct client's library.
For broader brand migration, see the brand migration guide. This article concerns Figma's name-based asset substitution.
Hypothetical two-client campaign
Hypothetical exercise. No Figma library swap was performed. A fictional agency has published libraries BRAND-ALDER and BRAND-BIRCH.
The campaign file POSTERS-BIRCH-LAUNCH was duplicated from an Alder campaign and still references Alder assets. The intended product is Birch SKU MUG-BIRCH-12, with approved photograph birch-mug-front-v3.png.
Both libraries contain components named Poster/Card and Badge/Offer. Only Alder contains Logo/Heritage. The expected swap can match the first two names but cannot automatically find a counterpart for the unmatched heritage logo.
| Asset | Replacement match | Proposed action |
|---|---|---|
| Poster/Card | Yes, by name | Review matched component |
| Badge/Offer | Yes, by name | Review offer meaning and style |
| Logo/Heritage | No counterpart | Manual replacement or removal |
| Product photo | Not established by library match | Assign approved Birch source separately |
Repair partial brand migration
If Logo/Heritage remains connected to Alder, inspect the unmatched-asset list and replace or remove it through an authorized manual operation. Do not describe the library swap as complete.
If Poster/Card matches by name but its layout is unsuitable, stop and review the destination component's actual structure. A successful name match does not establish equivalent layout behavior.
If the Birch brand styles appear correct but the poster still shows an Alder product, replace the product-specific image using the approved SKU reference. Library substitution does not guarantee merchandise accuracy.
If the file contains local components rather than assets from another published library, the documented Swap library mechanism does not apply. Use appropriate instance or source-component editing instead.
For individual component swapping, consult the component-property guide for field-level responsibilities. CartVisual does not perform Figma library swaps or certify their results.
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Campaign | Asset | Source library | Target library | Matching name | Actual resulting source | SKU evidence | Next action |
|---|---|---|---|---|---|---|---|
| POSTERS-BIRCH-LAUNCH | Poster/Card | BRAND-ALDER | BRAND-BIRCH | Yes | Not swapped | MUG-BIRCH-12 | Review matched component |
| POSTERS-BIRCH-LAUNCH | Badge/Offer | BRAND-ALDER | BRAND-BIRCH | Yes | Not swapped | Offer unconfirmed | Hold promotional copy |
| POSTERS-BIRCH-LAUNCH | Logo/Heritage | BRAND-ALDER | BRAND-BIRCH | No | Expected to remain Alder until corrected | Not applicable | Replace or remove manually |
What the sources establish
- Figma — Swap libraries: Documents published-library eligibility, name matching, unmatched assets, and selection controls.
- Figma — Swap components and instances: Documents the separate instance-level replacement mechanism.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Figma — Swap libraries · Review date not separately recorded
- Figma — Swap components and instances · Review date not separately recorded
Frequently asked questions
Does Figma match library assets by visual similarity?
No. Its documented Swap library mechanism matches published assets by name.
What happens when the replacement library lacks a matching logo?
Figma leaves the unmatched asset connected to its original library. The editor must decide whether to keep, remove, or manually replace it.
YOUR NEXT CAMPAIGN
Create assets from a clear source
Bring your reviewed source photo or brand brief to CartVisual. Check the current tools, account access and credits before generating, then compare every result with your source.
Create a CartVisual account Open the workspace Check access and credits