Library components are taking too long load when brought into the design design file

I have a design library on Figma that contains everything from small components, like forms fields, to really large components, like table, modals and wizards. There are no interactive components in the library and it is very easy to publish any component when updates are made.

The problem is when we use the library within a design file, bringing in components takes a long time, almost 2-5 seconds. This happens with larger components only. When the components are brought in, it is difficult to change their component and variant properties. I am able to see that the property is changed on the right panel, but the change does not immediately show on the design. It sometimes takes 10 seconds to load the change made to the property. This happens every time a component or a variant property or a nested component property is changed.

My whole team is facing this problem, and it is leading to them detaching the component from the library, which kind of defeats the purpose of having the library.

1 Like

Hey @Mona2, thanks for reaching out and sorry to hear you’ve been having trouble with this library!

You mentioned that your whole team is facing this problem, but has this loading issue been happening for a while or just recently?

When a library is large, especially if it includes many variants in one component set, this extra load time may be expected. A component set appears as a single-component update when publishing, but keep in mind that publishing a single component set includes all of its variants. Very large component sets can be slow to publish and can slow down performance in files using these variants.

If you continue to have issues with the library, please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new

Be sure to use your Figma account email, include a screen recording of the behavior as well as a link to the library, and invite support-share@figma.com as an editor on the library, so we can take a closer look as to what may be causing the issue.