Hello! I created a new plugin that can help identify stray variables or components that are still attached to a node somewhere in your file. You may have to run the plugin one page at a time for bigger files for now (it can timeout on whole file scans if the project file is large). Hoping this helps some others like it did for me. Give it a try!

Stray Component & Variable Finder

Unfortunately, that doesn’t solve the described issue. We’re looking for a way to identify all instances of a given component across ALL files in an account/org/enterprise, not just within a single file (let along a single page). It’s easy enough to locate a component within a file with the native search or any number of existing plugins.

​​​​​​​I want to know how many times our primary button component, for example, is being used across all files created by a large product design team. I can get a count from the library’s analytics report, but there no way to see WHERE those instances are being used. Ostensibly, Figma knows because it’s counting them. I’d like to be able to see the locations and access them to view and/or make changes.

+1. We need this feature now for managing large-scale design systems.

+1 another one of those small QOL updates it would be great to see Figma prioritise over the more flashy stuff

Some suggestions to the Figma team:

• Make library analytics searchable and filterable on component properties
• Allow us to right click a component variant, and ‘view library analytics’ for that specific variant which could open up the existing dialog that shows no. instances per file with links to them
• When clicking on a link to a file, show us where the instances are - I imagine a similar UI to the one where we review component updates

I might be a bit late, but I built a plugin to search for and locate both components and instances. The plugin searches, locates, and lists components and their instances. Plus, with a single click, it takes you directly to each component or instance

https://www.figma.com/community/plugin/1505449538275448157/components-explorer

Adding to the discussion. I assume most Figma users work on one design at a time and are not using a global design system. My team works on SAAS products with hundreds of page designs across dozens of projects. I am currently trying to understand how disruptive a component design change would be across all our products. But I can’t easily find how often this component is being used. I should be able to have a global view of where the instance of the component is used. As someone mentioned, Sketch was able to do this. 😓

I’m cleaning up some outdates library files and want to check if components are used in any other file before removing them. 

Library analytics may provide what we’re looking for.

I might be wrong but Library analytics seems to only point out and open Figma files that have a published component instance in them. Once in the file with the instance there are only plugins to search for components but no Figma "official" tool. If anyone knows of a tool that can search across files and pinpoint instances of published assets that would be great. 

I have a phantom instance of a component from Library A in the Design System document for Library B so that Library B insists on saying that Library A is being “used in the file” and there’s literally no way to just search the document for things from that library. 

All of the suggestions from older threads refer to a “used in this file” section of the assets pane which does not seem to exist any more. I suspect it may be complicated by the fact that the original component was deleted from Library A.

But there’s no reason that the assets pane shouldn’t show you a list of what assets are coming from what other files and the ability to find them within your file. That seems like incredibly basic level functionality.

++++
Really need this feature. I work in the corporation with a lot of products but with one design system, and i have to go through many design files blindly FOR HOURS to find use cases of a component, because i simply don’t know where we use it in our interfaces, because it’s a lot of products out there really. 
 

It’s hard to work without this feature in the big companies, especially if you’re new employee. I have to bother my colleagues with those questions and they happens not to know an answer themselves!