Skip to main content
Iasonas
March 9, 2021

Enable Assets search only for enabled libraries

  • March 9, 2021
  • 60 replies
  • 7387 views

Since a long time ago I have noticed that Figma allows you to search all your published components within the asset window of a file. The thing is that I want to search only within the localized assets of a file and not all. All other libraries are switched off, however, I still search across every file and this is really frustrating.

I initially believed that this was a bug that would be fixed, but 1 year later I see that nothing changed. I remember that Figma used to allow its users to search within different published libraries in a file - if they wanted to, not obligingly. Anyone else having the same issue and found any solution?

60 replies

Jeffrey_Gadzala
February 8, 2023

This could be really helpful for us. We’re not even a big shop, but keeping the smaller subcomponents we use to create a main component hidden from search would be really helpful.

Serhiy_Vdovichenko
February 23, 2023

Same here so frustrating!!!

John_Burrows1
February 28, 2023

Just joined a large organization with dozens of design teams spread out over years and years.

Searching for “checkbox” shows every checkbox from every possible iteration of old design systems.

The default behavior for component search should only show local components and enabled libraries.

Jan_semler
New Participant
April 12, 2023

This is nearly a two year old topic and it is still a big pain. Please solve this.

April 13, 2023

Please fix this issue! Clearly, its current search behavior is unexpected and counterintuitive. Not looking forward to all the upcoming issues this will cause when our organization grows.

Christian_Davis1
April 20, 2023

This is a critical issue. This structure does not support agencies that have unique design systems for each new clients. Assets search within a design system is completely unusable.

Chris_Ginn_biBERK
New Member
May 19, 2023

This is a huge issue! FIX IT! 😡

Zach_Ward1
New Member
June 1, 2023

I’m surprised this has yet to be fixed. Asset search should be the quickest was to find components, yet I end up not using it because it displays depreciated and “hidden” components. What is the point of this? We unpublish components so they won’t be used by our design team. I constantly have designers pulling in depreciated icons because the asset search querying is so bad. It doesn’t even throw them into categories or divide them by their path. It’s a truly terrible experience and makes search painful if not completely worthless.

Please make this a priority.

Jan_semler
New Participant
June 27, 2023

Please do this. I got a lot of libs running for different clients. And it is annoying as hell to place an icon which isn’t used within the system. I only want local or connected component in the search result and not those of all librarys, outdated, old or new.

Fuse
New Member
July 4, 2023

Any update on this thing? It been started since 2021 with 150+ vote. How many more they need to take action in general?