Skip to content
tezvyn:
Menu

Figma Components: Main vs. Instance

Source: help.figma.comEasyHow cards are made

Think of a main component as a cookie cutter and instances as the cookies. The main component defines the master design (e.g., a button's shape). Instances are linked copies you use everywhere.

Why it exists

Components solve the problem of inconsistency and repetitive work in design. Without them, changing the color of 100 buttons would mean editing 100 separate objects. A component system ensures that when the master design changes, all copies update automatically, saving time and preventing errors.

The mental model

A main component is a blueprint or a master template. An instance is a live, linked copy of that blueprint. You can have one main component for a button and hundreds of instances of it across your application mockups. If you update the blueprint, all the copies instantly reflect that change.

How it works

The main component defines the core properties of an element. When you create an instance, it's a copy that remains linked to the main. You can apply local changes to an instance, like changing a button's text label—these are called overrides. However, fundamental properties inherited from the main component, like color or corner radius, will update across all instances when you edit the main. This allows for both consistency and flexibility.

When to use it

Use components for any element that appears more than once in your designs. This is essential for building a design system. Common use cases include buttons, icons, form fields, navigation bars, cards, and footers. Any element you want to manage from a single source of truth is a candidate for a component.

When not to use it

Avoid creating components for truly one-off, unique elements that will never be reused. For example, a custom illustration for a single marketing page doesn't need to be a component. Making it one adds unnecessary complexity to your file without providing any benefit of reusability.

One canonical example

Imagine you design a primary button with a blue background and white text. You designate this as your main 'Primary Button' component. You then create three instances and override their text to say 'Sign Up', 'Confirm', and 'Submit'. Later, you decide the brand color should be green. You edit the single main component's background to green, and all three instances instantly update to a green background while retaining their unique text labels.

Interview question

When you update the background color of a main component, what is the expected outcome for its instances?

  • a.All instances will automatically update to the new background color.Correct
  • b.Instances will retain their original background color unless manually detached.
  • c.The main component's color changes, but instances require a manual refresh to update.
  • d.Only instances that have no local overrides will reflect the color change.
Why?

The card states that 'fundamental properties inherited from the main component, like color... will update across all instances when you edit the main,' making option A correct. Option D is incorrect because local overrides (like text) do not prevent fundamental property updates from the main component.

Just read this? Test yourself on what you have been reading.

Read the original → help.figma.com

Put your scrolling time to good use

Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.

The iPhone app is on the way

We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.

Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.

Get it on Google PlayiPhone app coming soon

We are hiring for this. Open roles that interview on figma — each one lists the topics its interview covers.

See open roles