See where component is used / find component Instances across files

+1 to a global solution for company-level Design / Product systems. Finding instances across an entire company account.

2 Likes

Сompletely agree. We need this :+1:

1 Like

Still in need of this feature! Hopefully it gets developed sooner than later

@Figma we all need this feature, it’s an essential while working in big organisation with one library used in dozens of files… Any updates on this?

2 Likes

+1; still very much need a global instance search feature to hunt down older ghost components across all files at once.

1 Like

Bumping for visibility. This feature request thread was started in Oct '22, and I have continued to feel significant friction in lacking cross-file instance finding for several years at this point.

Figma team, please prioritize this one asap!

3 Likes

Bumping this also as I need that right now

2 Likes

+1

to have a detailed search of instances across an entire company account !

1 Like

Bumping again for visibility

2 Likes

Ideally you go to master file and be able to visualise where this is used in all the files.
In my case in our team we have a master file for the design system but multiple files for each functionality.
To find where E.g. an old icon was / or if it is still used I have to manually search all the files . It is a lot of work. Specially if I want to redesign the app, it is basically easier to do it just from scratch

2 Likes

Real-time design system management use case:

I just found a pair of duplicate components and would like to delete one.

Before removing one or the other, though, I’d love to also be able to easily see whether one or both are currently being used anywhere.

2 Likes

Bump.

Would be nice to be able to do a global instance search, esp when updating components in libraries that use other components. No idea if they need reset or took the changes correctly without manually going through each instance.

2 Likes

Bump into this for more visibility. Thank you Figma team​:pray:t2::sparkles::sparkles::sparkles:

1 Like

This needs to be a feature!

Bumping for visibility.

My feature files get quite expansive and I often have reduced performance due to memory limitations. I can not unify all instances of a component in one file.

Searching for all component instances across files would be critical to my success as a product designer managing a design system.

4 Likes

I would like to propose the implementation of a feature that provides comprehensive statistics on the usage of components within Figma files.

This feature would offer insights into how frequently a particular component is utilized across different artboards and pages within a file along with detailed information such as usage count, artboard name, page name, and instance count upon selection. (Same on library)

Usage Count: The feature would display the total number of times a specific component is used throughout the entire Figma file. This metric would help designers identify the most commonly used components and prioritize updates or modifications accordingly.

Artboard and Page Name: Alongside the usage count, the feature would provide visibility into the specific artboards and pages where each instance of the component is located. This information would enable designers to quickly locate and navigate to relevant areas of the file for further analysis or editing.

Instance Count on Selection: When a component is selected within the Figma canvas, the feature dynamically displays the number of instances of that component present on the current artboard. This real-time feedback would empower designers to make informed decisions while working on design iterations and updates.

3 Likes

Bump… absolutely needed in big organizations

3 Likes

Agreed with above opinions on using Figma in large scale projects, especially design system

not having a way to gather a list of scenarios where the component is used across projects hugely undermines the ability to predicts the impact of changes and undermining the value of actually spending time creating the components from the get go hugely (especially in scenarios where “one-off” to offer “tailored” experiences to specific projects are accepted)

1 Like

This is a major hurdle for our team; part of a large organization where not everything was implemented with properly organized libraries at the start, and now managing it is very difficult when we can’t see where component instances have been used.