Anyone else finding that Figma is getting choppier and less performant on Intel macs?
I have a perfectly working machine that’s been running fine for a good amount of time. But in the last 6 months I’ve found that Figma has become more laggy and slower to update things on the canvas. Am I alone, anyone else finding this?
Hey @Benji_Greig1 - I’m wondering if you’re hitting some issues because of your file complexity. Just some questions to get more context:
Are you seeing this overall? Like across all files you work on, even new ones?
Is this slowness on both the desktop app and web browser?
When you notice this, are you working with multiple files at the same time? Do these files have a lot of components or large libraries?
Hey Kim, no I’m seeing this everywhere on files that were previously more performant.
Some files have quite a few components but they’re not epically large.
I’ve been working on this same machine and the same project files for a while without this much of a slowdown. I’ve also tried quitting everything except Figma with little change in behaviour.
Hence why I posted.
Understood! I understand it may have seem repetitive to ask, but I always want to cover my bases before providing suggestions.
It isn’t too uncommon to see performance issues reported, but they vary in cause. Some instances are large libraries/multiple components/complex prototyping. At times, this can be contributed to memory limits being hit.
Every individual browser has its own active memory limit. In general, we work on an active memory limit of 2GB per browser tab. Since Figma is built on browser-based technologies, these limitations apply even when you’re using Figma’s desktop app.
You mentioned “files that were previously more performant” – I do have to wonder if this may perhaps be part of the problem, since I assume these would have a lot of details that have collected over the course of the file’s life (but let me know if I have assumed incorrectly).
What I’d first recommend is reviewing the page we have on troubleshooting - specifically, the memory section.
Another thing I’d try is duplicating one of the problematic files, and seeing if the dupe misbehaves as well. If that turns out to be the case, I would be more suspicious of a memory issue.
If you don’t believe the suggestions above help, I’m happy to get you connected with the support team directly to review the files themselves. Just let me know if you’d like to do that.