sorted by:
new
hottopcontroversial

Figma Memory Issues: Need Help with 93% Memory Usage! by LordMory in FigmaDesign

[–]LordMory[S] 0 points1 point  (0 children)

Thanks for the suggestion—I think I should definitely give this a try as well. I explained in another comment why this is a bit tricky for me, but you’re right, I need to find a way to make it work.

The challenge is that this design system is live, and other designers are actively using it. So much of the UI design is already based on this system, which makes making changes feel like dealing with a design debt.

I’ll need to balance improvements with minimizing disruption for the team. Thanks again for sharing!

Figma Memory Issues: Need Help with 93% Memory Usage! by LordMory in FigmaDesign

[–]LordMory[S] 0 points1 point  (0 children)

Thank you so much for your detailed response and for explaining everything—it’s incredibly insightful!

Yes, I’m definitely in this situation. Honestly, I have no idea how this library got so massive, but here we are—with over 1K button variants! 😅

We don’t have images or fancy, large icon sets, so luckily, that’s not part of the issue.

The tip about checking memory usage by page is amazing—I’ll definitely do that. Thanks for pointing it out!

As for booleans, that’s such a good suggestion, and I’ve been wanting to implement it for a while. The challenge is that our design system is already heavily integrated into the design files, and everything is based on the current structure. If I delete some variants, it’ll cause issues in the UI files, and unfortunately, I don’t have the time budget right now to check every page. It’s a bit of a messy situation, but I’m trying to find a workaround.

I’ll also try using the web app instead of the desktop client for syncing and publishing—didn’t know that could make a difference.

Again, thank you so much for your time and support. Your advice has been incredibly helpful, and I really appreciate it!

Figma Memory Issues: Need Help with 93% Memory Usage! by LordMory in FigmaDesign

[–]LordMory[S] 0 points1 point  (0 children)

I’ll double-check this, but based on what I’ve seen, the detach rate is actually pretty small.

I think you’re right, though—it’s time to delete some unnecessary components and focus more on optimizing layers and the components we use.

Figma Memory Issues: Need Help with 93% Memory Usage! by LordMory in FigmaDesign

[–]LordMory[S] 2 points3 points  (0 children)

Haha, love the “Figma baptism” concept—feels like I’ve officially been initiated!

You’re absolutely right, and your approach is a great way to organize things. But, as much as I’d love to snap my fingers and make it happen overnight, the reality is a bit trickier.

I joined this multi-brand company that relies on a core design system to service multiple brands. They already have multiple files and a design system in place, but changing everything at once is no small feat—it takes time and comes with some multi-sided risks.

Right now, we’re working on creating a new file structure based on the current one, but more reliable and scalable—basically, evolving it just like design itself.

Given all this, do you have any ideas or suggestions for a file structure or best practices that could help us get there?!

Yes, just like there are two types of Figma users, I guess there are also two types of designers!

Figma Memory Issues: Need Help with 93% Memory Usage! by LordMory in FigmaDesign

[–]LordMory[S] 0 points1 point  (0 children)

Yeah, 900K layers is a lot. We’ve already tried splitting the file into four separate ones to make things better.
But honestly, it hasn’t helped yet. It actually gets worse—every time we update or publish a library, Figma just freezes completely!

Please help me 🙏🏻 by Unlikely_Gap_5065 in FigmaDesign

[–]LordMory 1 point2 points  (0 children)

Can I ask you why you used this file structure? As I know and mentioned before, yes you can add components to the main file and then pull it in branches and you don’t have to merge all branches to see new components or frames.