From the perspective of UX/UI design, the significance of leveraging components in Figma cannot be overstated. These powerful tools serve as catalysts for elevating the caliber of our projects, bestowing upon us the ability to establish a standardized framework.
By harnessing the potential of Figma’s components, we embark on a journey toward optimal efficiency and impeccable consistency in our creative endeavors. These versatile building blocks allow us to fashion reusable templates for various objects and elements, empowering us to seamlessly replicate and iterate upon our design solutions.
The integration of Figma’s components within our workflow paves the way for a harmonious fusion of uniformity and innovation, ensuring that our designs resonate with both precision and creativity.
To use a component, we can simply duplicate it or call it from the left sidebar: Assets > Local Components. An instance will be displayed in our workspace, easily identifiable by the diamond-shaped icon in the left sidebar, under the Layers section. Meanwhile, the main components are marked by four solid diamonds:
Instances cannot be modified entirely as they are subordinate to the main component. For this reason, it may sometimes be necessary to detach the connection between our instance and the main component in order to apply all the modifications that our main component does not allow us to make.
To detach an instance, simply follow these steps:
Or you can simply select the instance > right-click > Detach Instance:
Alternatively, you can simply click the following key combination, which may vary depending on the device: Ctrl or Cmd + Alt + B.
Once you’ve done that, the connection between the instance and the main component will be interrupted. We can see that the disconnection has occurred because its selection rectangle will change from purple to blue, and its identifying icon (◇) will disappear from the layers section:
It is not so unlikely to accidentally delete a main component, but fortunately, this situation can be easily remedied as follows: Select one of the instances connected to the deleted main component and press the button located on the right sidebar > Restore Component:
Once the button is pressed, the main component will be automatically retrieved and placed back into your project.
Making changes to an instance of a component that contains nested components requires careful attention because it is important to understand from the beginning which nested instances within it will be modified and which ones will not:
In the following case, we have a card containing a series of components (1. Primary Button, 2. Secondary Button, and 3. Avatar). If we want to modify the following instance without completely disconnecting it from its main component, and instead only modify one of the instances within it, we will not disconnect the entire instance.
Instead, we will select one of the nested instances within it and perform the same procedure as seen in the previous pages to Detach Instance. This way, we can modify the content of the card while leaving it unchanged, as it will always be subordinate to its main component.
In the event that we need to modify an instance and decide to restore its original characteristics, we simply need to perform a recovery action:
To perform the recovery action, we will need to: Select our instance > Instance Options > Reset all changes:
In this way, our instance will return to its original appearance. Note that in the dropdown menu of the instance options, in addition to the Reset all changes action, another set of actions appears. These actions represent the changes that have been applied to the instance and that we can choose to reset.
There are several plugins in Figma that allow you to perform what is called Undo Component, which will enable us to undo one or more groups of components (variants) without the need for too many steps:
The plugin to be activated is the following:
Once activated, all we need to do is select the group of components, open the plugin panel, and activate the following plugin: Detach Component. Automatically, all the components will be detached.
As you can see, there’s more than one way to undo a component — you have several choices. Hopefully this guide saves you from any pesky situations where you’re stuck with components you don’t want or need.
LogRocket's Galileo AI watches sessions and understands user feedback for you, automating the most time-intensive parts of your job and giving you more time to focus on great design.
See how design choices, interactions, and issues affect your users — get a demo of LogRocket today.
This article examines when hero sections are necessary in digital products, when they create friction, and how to evaluate them using UX goals, primary actions, user flow impact, and real-world alternatives.
AI speeds up tasks like research synthesis, ideation, and first-draft wireframes, but it can’t replace clarity, taste, or decision-making. Here’s a grounded look at what AI actually does well in UX right now.
Discover how to craft UX-friendly hero sections with examples, design tips, and strategies that drive engagement and conversion.
I once sent a half-written email by accident, until Gmail saved me with an Undo button. Those tiny moments define trust in UX. In this guide, we’ll break down how to design reversible actions, when to use them, and how to choose the right recovery pattern for your product.
Learn more →
