Figma Library Component Update Resets Nested Overrides on Parent Layout Change

Answer – What Triggers Override Reset?

Figma stores overrides by the exact layer reference path inside a component. If that path changes, the editor cannot map the old override to the new node and clears it. The following parent‑level changes are the most common culprits:

• Switching auto‑layout direction (horizontal ↔ vertical) on the parent component.
• Adding, removing, or reordering layers between the parent and a nested instance.
• Renaming any layer that lies on the hierarchy path to the nested instance.
• Changing the parent’s constraints so that the nested instance’s relative position is no longer represented by the same node reference.
• Swapping the nested instance’s component target in the consuming file (e.g., replacing a button with a link).

Pure property tweaks—spacing, padding, alignment, corner radius, text content, or color changes—usually preserve overrides because the node tree stays intact.

Why Version Numbers Don’t Affect Override Preservation

Figma’s override logic is independent of the semantic version you assign to the library. A "minor" bump that flips auto‑layout direction will reset overrides just as aggressively as a "major" bump that adds a new component. The only determinant is the structural diff between the old and new component node trees.

How to Spot Affected Instances Before Publishing

1. Create a copy of the current library file and apply the intended layout change.
2. Publish the modified file to a new branch (e.g., lib-v2).
3. Open a representative consuming file that uses the component.
4. Accept the update banner. If any nested instance has lost overrides, Figma shows a "Reset overrides" badge next to the instance in the layers panel.
5. Use the Reset overrides dialog to confirm which properties were lost. This is the only built‑in pre‑publish audit.
6. Optionally, run a visual diff on a dedicated QA file that imports every variant you use in production. A side‑by‑side comparison will reveal any visual regressions caused by override loss.

Automated checks can be added by querying the Figma REST API for the component’s node tree before and after the change. Any change in a node’s id or name along the path to a nested instance predicts a reset.

Practical Safeguards

• Keep the component hierarchy flat where possible. A single auto‑layout container that holds all nested instances reduces the chance of accidental path changes.
• Avoid renaming layers that are part of the public API. If a rename is unavoidable, document it and run the test‑branch workflow above.
• Use component swaps sparingly. If a nested instance is swapped in the consuming file, its overrides will always be lost on any update, regardless of the parent’s layout.
• Maintain a “library‑test” file that imports every component variant. Run the update workflow against this file after each change to catch regressions early.

Quick Diagnostic Question

To refine the recommendation for your specific case, could you confirm whether any of your nested instances are currently swapped to a different component or have been detached in the consuming files?