Figma Library Component Update Resets Nested Overrides on Parent Layout Change

Figma Library Component Update Resets Nested Overrides on Parent Layout Change

Publish a new Figma library version for a small design system while keeping consuming files open and preserving local overrides on nested component instances.

Figma Libraries surface an update banner in consuming files, and instances can be updated without closing the file. The unresolved boundary is what happens to nested overrides when the published change modifies a parent component’s layout, such as changing auto-layout direction or constraints. Published Figma documentation does not specify which change types preserve overrides versus reset them to library defaults.

A rolling library migration depends on predictable instance behavior. Teams cannot currently determine whether a layout update will force designers to reapply overrides across dependent files after publication.

• Which parent-component layout changes cause Figma to clear nested instance overrides during a library update?
• Can a team identify affected consuming instances before publishing a new library version?
• Does override preservation differ between major and minor library version changes?