Why It Matters
When you detach an instance in Figma, you're essentially creating a copy that no longer receives updates from the main component. This can lead to design drift, inconsistencies across your files, and increased maintenance burden. While sometimes intentional for one-off variations, accidental detachment is a common source of design system debt.
Examples
1
A button instance was detached so a designer could add a custom icon, but now it doesn't reflect the updated border radius from the design system.
2
A card component was detached months ago and now uses the old color palette while the rest of the app has been updated.
3
An engineer implemented a component based on a detached instance, resulting in hardcoded values instead of design tokens.
How BiblioKit Helps
ComponentQA automatically scans your Figma files for detached instances, helping you identify and reconnect components to maintain design system integrity.
Related Terms
Instance
A linked copy of a main component that inherits its properties and automatically updates when the main component changes.
Main Component
The original, source component that defines the structure, styles, and behavior that all its instances inherit.
Component Set
A group of related component variants combined into a single component with configurable properties, allowing users to switch between variants without swapping components.
Design System Audit
A systematic review of design files to assess adherence to design system standards, identify inconsistencies, and find components that have drifted from their source.
Explore More Design Terms
Browse our complete glossary of Figma and design systems terminology.