Assets & tasks / MERCHANT WORKFLOW
Can You Move a Product Photo Above the Headline in One Figma Component Instance?
You cannot change the underlying layer order of a Figma component instance through an ordinary instance override. Figma also restricts instance-level changes to structural properties such as layer position in the hierarchy and constraints. If a product photo must appear above the headline in one campaign, decide whether that arrangement should become an approved component variant or remain an independent one-off design.
Identify the difference between content and structure
Figma instances inherit their structure from the main component. An editor can override supported content and appearance properties, but Figma's instance documentation excludes underlying layer order, constraints, and structural positioning from ordinary overrides.
For a merchant poster, replacing a photograph is a content change. Moving its layer above the headline changes the composition's structure. These requests may sound similar because both concern the product image, but they have different editing consequences.
Before changing anything, inspect the selected object. Confirm that it is a component instance rather than an independent group or frame. Identify its main component and any available layout variants. A layer appearing above another in the visual composition does not necessarily mean its position in the Layers panel has changed; distinguish visible placement from stacking order.
| Requested change | Appropriate scope |
|---|---|
| Replace product photo | Supported instance content or fill override |
| Change headline wording | Text override or exposed property |
| Use photo-first composition repeatedly | New component variant |
| Change every poster's hierarchy | Main component |
| Make a permanently independent one-off | Consider detaching after approval |
Choose a reusable layout or an independent exception
If several campaigns need a photo-first arrangement, ask the component owner to add a documented layout variant. That preserves a reusable structure while allowing instances to select the appropriate arrangement. Compare corresponding layer names and properties across variants because Figma's override-preservation rules can affect content when switching.
If the existing composition is wrong for every campaign, revise the main component instead. That decision can affect linked instances, so the owner should inspect the change scope before publishing a library update.
If exactly one poster needs an exceptional composition that should no longer inherit future component changes, detaching may be appropriate. Detachment is a deliberate loss of the component relationship, not a harmless method for temporarily moving a layer. Preserve the original linked instance or an untouched file version for comparison.
Do not change the shared master merely to satisfy a single unapproved campaign request. The template field guide
Hypothetical bottle-poster exception
Hypothetical exercise; no Figma instance was modified. Component POSTER-BOTTLE-V4 has a Standard layout with layer order Headline, ProductImage, and Footer. Campaign instance AD-BTL-014 represents SKU BTL-GLASS-500, using approved photograph bottle-clear-front-v3.png and headline Everyday Glass Bottle.
The creative brief requests a photo-first layout for this campaign. A second campaign, AD-BTL-015, must retain the Standard arrangement. The proposed reusable solution is a PhotoFirst variant, not a change to the shared Standard structure.
Expected states are: AD-BTL-014 uses PhotoFirst with the approved photograph and wording; AD-BTL-015 remains Standard. Neither outcome has been tested. The component owner must confirm whether the requested hierarchy can be implemented without disrupting existing overrides.
Branch on the result of the layout change
If the new variant displays the correct hierarchy but loses the product photograph, inspect matching layer names and original property values before rebuilding the image. The variant override guide
If the main-component change unexpectedly affects AD-BTL-015, stop the shared release and restore or revise the intended variant boundary. If the one-off detached poster looks correct but no longer receives approved brand changes, record its independent status and assign an owner for future updates.
Approve the exported poster only after checking the exact SKU, headline, layer visibility, and destination crop. CartVisual does not edit Figma component structures or publish their derivatives.
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.
| Instance ID | SKU | Current layout | Requested layout | Approved image | Chosen mechanism | Actual observation | Next action |
|---|---|---|---|---|---|---|---|
| AD-BTL-014 | BTL-GLASS-500 | Standard | PhotoFirst | bottle-clear-front-v3.png | Proposed new variant | Not tested | Author variant and check image override |
| AD-BTL-015 | BTL-GLASS-500 | Standard | Standard | bottle-clear-front-v3.png | Retain existing instance | Not tested | Confirm no unintended change |
What the sources establish
- Figma — Apply changes to instances: Documents supported instance overrides and structural restrictions.
- Figma — Edit main components: Documents the main-component editing relationship and consequences for instances.
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
- Figma — Edit main components · Review date not separately recorded
Frequently asked questions
Can an ordinary Figma instance override change layer order?
No. Figma documents structural layer order as outside ordinary instance overrides.
Should I detach an instance for a single unusual poster?
Only when the loss of future component inheritance is acceptable. A reusable layout variant is preferable when the composition will recur.
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