Assets & tasks / MERCHANT WORKFLOW
Why Did a Figma Master Component Update Some Product Posters but Not Others?
Figma handles same-file component changes differently from changes to published library components. Local instances can reflect edits to their main component in the same file, while subscribed files receive library updates through a publish-and-review process. An updated master, a published library revision, an accepted subscriber update, and a newly exported advertisement are four distinct states.
Identify which file owns the component
Start by locating the actual main component used by the affected poster. Figma's Edit main components instructions distinguish the main component from its instances. When a main component is edited, its connected instances inherit applicable changes, subject to intentional overrides.
For a component published from a shared library, the publishing workflow introduces another boundary. The library owner must publish changes; subscribing files then review available updates.
A poster that still displays an old logo may therefore be linked to a different source, be awaiting a library update, or contain an instance override. Do not assume every old-looking poster has the same cause.
| State | What it establishes |
|---|---|
| Main component edited | Source design changed |
| Library update published | Revision made available to subscribers |
| Subscriber update accepted | Receiving file applied the available revision |
| Poster exported again | New delivery file created for review |
Trace the update through its actual owner
For an instance in the same file as its main component, inspect the source and the instance together. If the intended change does not appear, check whether an override or a different component identity explains the difference.
For an instance from a shared library, inspect the source library's publication state. Figma documents a library publishing process that allows the owner to review unpublished changes and publish updates.
Next open the subscribed campaign file and inspect its available library updates. The authorized editor should review and accept the intended revision, then inspect the affected instances.
Do not describe an unpublished local edit as a completed cross-file rollout. Similarly, accepting a library update does not rewrite PNGs previously exported to an advertising account.
Hypothetical three-poster campaign
Hypothetical exercise. No Figma library was edited or published. Shared library BRAND-LIB-R4 contains component PosterHeader. The proposed revision changes the approved logo from mark-r4.svg to mark-r5.svg.
Poster POSTER-A11 is in the source file. POSTER-B12 is in subscribed campaign file CAMPAIGN-A. POSTER-C13 is a previously exported PNG.
The expected workflow is to review the source component, publish the library revision, accept the update in CAMPAIGN-A, and separately export a replacement for POSTER-C13 if its destination still needs the new identity.
None of these steps is assumed complete. The exact current library access and publication permissions must be checked in the merchant's account.
Choose the repair from the missing update
If POSTER-A11 remains unchanged despite a source edit, inspect its component identity and overrides. If POSTER-B12 remains unchanged, first determine whether the library revision was published and whether CAMPAIGN-A accepted it.
If the subscribed file accepted the update but still shows an old logo, inspect local overrides or independent copies before publishing another library revision.
If the Figma design is correct but POSTER-C13 remains old on a website, export and deliver the revised asset through the actual publishing workflow. A library update cannot replace a previously downloaded raster.
For other applications' independent saved-copy behavior, see the Google Photos guide; it is a comparison, not the same Figma mechanism.
CartVisual does not publish Figma libraries, accept subscriber updates, or replace external campaign exports.
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.
| Asset | File | Component source | Proposed revision | Publication or acceptance state | Actual visible mark | Next action |
|---|---|---|---|---|---|---|
| POSTER-A11 | BRAND-LIB-R4 | Local PosterHeader | mark-r5.svg | Not edited | Not inspected | Inspect local component and instance |
| POSTER-B12 | CAMPAIGN-A | Published PosterHeader | mark-r5.svg | Not published or accepted | Not inspected | Publish and review update |
| POSTER-C13 | External PNG | Earlier export | New export required | Not delivered | Not inspected | Replace destination file separately |
What the sources establish
- Figma — Edit main components: Documents main-component changes and connected instances.
- Figma — Publish a library: Documents publishing library revisions and making updates available to subscribed files.
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 — Edit main components · Review date not separately recorded
- Figma — Publish a library · Review date not separately recorded
Frequently asked questions
Does changing a Figma library component immediately update every campaign file?
Do not assume so. Shared-library changes require publication and subscriber update review.
Does accepting a library update replace previously exported PNG advertisements?
No. Exported delivery files require their own replacement and destination verification.
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