Assets & tasks / MERCHANT WORKFLOW
Why Did Your Figma Product Photo or Offer Text Revert After Switching Poster Variants?
Figma attempts to preserve instance overrides when switching component variants, but preservation is conditional. Layer names must match, and some changed properties also depend on matching original values across variants. Text overrides have a less restrictive rule involving matching names and similar hierarchy. A poster that reverts after switching layouts may therefore have a component-structure problem rather than a missing saved file.
Identify which override disappeared
Figma's Apply changes to instances documentation describes how instance edits survive variant switching. For changed fills and similar properties, matching layer names are necessary. When switching variants, Figma also checks whether the original property values matched across the variants.
Text overrides receive different treatment: Figma preserves changed text when the corresponding layer names match and their hierarchy is similar. This makes it important to distinguish a changed headline string from an image fill or a color override.
Figma does not allow an instance override to change the underlying layer order, position within the component, constraints, or text-layer bounds. Those structural decisions belong to the main component.
| Changed content | Preservation evidence | First repair |
|---|---|---|
| Headline text | Matching layer name and similar hierarchy | Align component text structure |
| Product image fill | Matching layer name and compatible original property values | Review source fill configuration |
| Offer badge color | Matching layer and original fill conditions | Inspect variant defaults |
| Layer order or position | Not an instance structural override | Edit main component layout |
Inspect the main component before repeating edits
Open the relevant Figma component set and identify the two poster variants. Compare their layer trees, exact names, hierarchy, and original values for the properties collaborators will override.
If the product image is implemented as an image fill, check whether the corresponding layer has the same name and compatible original fill setup in both variants. If the headline is text, compare its layer name and hierarchy.
Use a duplicate test instance and apply one change at a time. Switch variants, record what survives, and return to the original variant. Do not assume that one preserved field proves all fields are safe.
When the desired change requires moving a layer or altering layout structure, update the main component rather than trying to force an unsupported instance override.
Hypothetical square-to-portrait coffee poster
Hypothetical exercise. No Figma file or component instance was edited. A fictional merchant has poster component set COFFEE-POSTER-V3 with variants Square and Portrait.
SKU COFFEE-BEAN-250 uses approved image coffee-bag-front-v4.png, headline Morning Roast, and an unconfirmed offer field.
The proposed component structure uses layers named ProductImage, Headline, and OfferBadge in both variants. The merchant suspects the Portrait variant has a different original image fill and a differently nested Headline layer.
The expected experiment is to override the Square instance with the approved photo and headline, switch to Portrait, and record each result. No actual preservation result is assumed.
| Field | Proposed override | Potential mismatch | Actual result |
|---|---|---|---|
| ProductImage | coffee-bag-front-v4.png | Different original fill | Not tested |
| Headline | Morning Roast | Different hierarchy | Not tested |
| OfferBadge | Hidden pending offer approval | Different layer defaults | Not tested |
Repair the component or the specific instance
If the image override disappears while the headline survives, compare the image layers' original fill values and names. Correct the component design where appropriate, then repeat the variant-switch test on a fresh instance.
If the headline disappears, inspect its name and hierarchy in both variants. Do not assume that a visually identical text box is structurally equivalent.
If the intended offer badge moves to an unacceptable location, decide whether that is a layout-variant design issue. Do not detach every instance merely to reposition a layer that should be controlled in the main component.
If a collaborator accidentally resets an override, Figma documents Reset controls for individual properties and entire instances. Use the smallest appropriate correction and preserve approved SKU content.
For another application's source-versus-instance behavior, see the After Effects Essential Properties guide. The mechanics are not interchangeable.
CartVisual does not create or repair Figma component sets, preserve their overrides, or publish poster 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.
| Component set | Fictional SKU | Variant transition | Layer | Proposed override | Original-value comparison | Actual preservation | Next action |
|---|---|---|---|---|---|---|---|
| COFFEE-POSTER-V3 | COFFEE-BEAN-250 | Square to Portrait | ProductImage | coffee-bag-front-v4.png | Unknown; suspected difference | Not tested | Inspect layer name and original fill |
| COFFEE-POSTER-V3 | COFFEE-BEAN-250 | Square to Portrait | Headline | Morning Roast | Hierarchy unknown | Not tested | Compare text hierarchy |
| COFFEE-POSTER-V3 | COFFEE-BEAN-250 | Square to Portrait | OfferBadge | Hidden until approved | Defaults unknown | Not tested | Review component design |
What the sources establish
- Figma — Apply changes to instances: Verified layer-name and original-value preservation rules, text hierarchy treatment, unsupported structural overrides, Reset controls, and source-component changes.
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 — Apply changes to instances · Review date not separately recorded
Frequently asked questions
Does Figma always preserve product-photo overrides when switching variants?
No. Its official preservation rules consider matching layer names and, for some properties, matching original values between variants.
Are text overrides preserved under the same conditions as image fills?
Not exactly. Figma documents less restrictive text preservation based on matching text-layer names and similar hierarchy.
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