Library is buggy and slow

Hey Sanny,
Thanks for reaching out to the community! Is this happening on both the desktop app and web browser?
The most common cause when a large Library is slow to publish is that this process is getting close to hitting our 2GB available memory limit. You can read more about this in Reduce memory usage in files.

Can you also please try publishing the changes in smaller batches using the checkboxes and see if they publish?
If publishing even a small number of components is quite slow, it means there is likely some other issue affecting this process — if this is the case, let us know and we’ll be happy to keep troubleshooting with you by reaching out directly to the support team: here (please also mention the steps you have done so far)
If it’s only happening in one file, please also include the URL of the file , and add support-share@figma.com as an editor on this file (this won’t affect your billing at all) so the support team can take a closer look. Thank you!

I am having the same issue - any answers to this?

Hi @Christina_Gritsas - issues with libraries (especially performance) tend to be related to the individual library itself. While it could be something buggy, it’s hard to tell unless we can review the library ourselves directly.

Would you be able to share a copy of the file/library you are working with, so we can look into this more?

The issue is after publishing from the ‘master library’
Updating into my other Figma files is very buggy. This started since the ‘new library update’ in the top right corner. Never had this issue before.

Unfortunately, I can’t really give any suggestions at the moment without other details. I understand that these seemed to have appeared after one of our updates, but I can’t say with certainty it’s the actual update that’s the problem, or if there’s some sort of disconnect in your library that can be fixed quickly.

😞 I know it’s probably been frustrating, and I’m sorry I don’t have a direct answer.

My best advice now is to reach out to support to see if they can pinpoint any issues or find any bugs. You can do that by emailing support@figma.com directly, or by filling out this form.

Hey Celine,

Thank you for your reply. I will look into your feedback.

Cheers,
Sanny

I think it is alright, no?

Component file

Token file

Project file

Hi there,
Thanks for the screenshots! I would like our support team to investigate further to double check what’s causing this.
As Kim mentioned, can you please reach out to the support team for further investigation with a copy of your file directly? You can do that by emailing support@figma.com directly, or by filling out this form.
Be sure to use your Figma account email, include a link to the file, and share it with support-share@figma.com, so we can take a closer look. Thank you!

Library components with variants do not update other than the default variant.

Other issues more randomly.

This happens when you are Figma and try desperately to push overall server load to a dystopian level, where usability and experience is dimished. That is why, we also have per-page loading and per-page library updates checks per default.

Then everything appears to be sloooooow.

Hey Figma! We all tend to have pretty powerful computers, do you think you’ll ever get round to letting us use files locally so your cloud limitations don’t mess with us eternally?

Backing up can happen, but coediting isn’t always needed. In the use case of a single designer per team (common), letting us just save to local and back up later (usually when we hand over to dev or submit for review) surely isn’t a crazy idea?

Lots of devs work locally and push to staging when they’re ready. Why is it such an unheard of concept for designers?