Skip to main content
Chela
New Member
December 3, 2025
Question

Figma Constantly “Syncing” and Not Saving

  • December 3, 2025
  • 9 replies
  • 562 views

We’re seeing a recurring issue in Figma where files get stuck in a constant “syncing” state and fail to properly save changes. This creates several workflow blockers:

  • Severe lag while working — interactions become slow or unresponsive during sync.

  • Unable to close the browser tab — Figma prevents closing due to “unsaved changes,” even when everything should be saved.

  • Version history overload — the system generates excessive versions because of the repeated auto-sync attempts, making the file history cluttered and harder to audit.

As a design system designer managing component libraries, this issue becomes especially problematic. It interrupts handoffs, slows down updates to shared components, and increases the chance of file conflicts or outdated states being published. It directly impacts our ability to deliver high-quality, timely component updates.

Requesting investigation into:

  • Why files remain stuck in the syncing state

  • Whether autosave is failing silently

  • How version creation is being triggered

  • Any performance issues affecting large component libraries

This is becoming a blocker for day-to-day design system work.

 

 

9 replies

Lukáš Kulla
New Member
December 11, 2025

Hello, I have the same issue with unsaved changes.

 

I figure out that this issue is affected with editing the same Figma file with another user. When another user is active and editing the file, my file is constantly freezing, lagging and it is impossible to work.

 

 

djv
Figmate
Community Support
December 22, 2025

Hi All, thanks for reaching out and apologies for the delayed reply! 

May I ask if this is happening for all your files or one file in particular?

As ​@Lukáš Kulla mentioned, is this only happening in files with multiple users editing the same file? And if so, is the unsaved changes happening for all users in the same file? Lastly, do you see an icon in the upper-right corner indicating saving issues, and if you do, what text is shown when hovering over the icon? 


With these details, we can work together to try and pinpoint the issue. 

Lukáš Kulla
New Member
December 23, 2025

Hey Djv,

 

this is happening in only one Figma file, I didn’t find other files with this issue yet.

There are few details:

  • When my colleague don’t work with the file, he only has opened file on another tab.
  • Figma shows “changes didn’t saved” pop-up within closing the file even tough the “changes didn’t saved” Icon is not visible.
  • We both have this issue, when we are in the file.

 

djv
Figmate
Community Support
December 24, 2025

HI ​@Lukáš Kulla, thanks for the additional context! 

What OS are you using, and is this happening in the desktop app, browser or both? Since you mentioned that this is only happening with one file, are you also able to share the file URL and invite support-share@figma.com as an editor to the affected file, so our technical quality team can take a closer look?

Thomas_Klepl
New Participant
June 19, 2026

I am experiencing this as of late as well. Never used to happen before. I think it might be related to the latest Figma update.

Desktop app on Mac.

Etienne Ledemay
New Member
September 17, 2026

I have the same issue: it happens on certain files where I use multiple stroke effects 

Gayani_S
Figmate
Community Support
September 17, 2026

Hey ​@Etienne Ledemay and ​@Thomas_Klepl, thanks for both flagging more detail here.

A few things worth trying for both of you:

  1. Force-quit and reopen Figma (desktop app, or a fresh browser window if you're on web)
  2. Toggle off multiplayer cursors, layout guides, or effects while working in the affected file.
  3. Make sure you're on the latest version of Figma (desktop app or browser)

 

​@Thomas_Klepl, since you're on the desktop app on Mac and this started around an update, it's also worth clearing the Figma desktop app cache. On Mac, that's in the Help menu in your system menu bar at the top of the screen (not inside the Figma app window itself): Help > Troubleshooting > Reset Figma and Restart. If you get a chance, could you also try the same file in a browser (Chrome, Firefox, Safari) to see if it follows you there or stays isolated to the desktop app?

 

​@Etienne Ledemay, could you let me know whether you're on the desktop app or in browser, and which OS? That'll help me see if the stroke-effects pattern lines up with what Thomas is seeing, or if it's a separate thing.

 

Since both of these seem tied to what's happening in specific files, I'd also recommend submitting a bug report through our Support Hub. That lets our customer support team take a closer look at your files and setup directly, which is hard to do here in the thread. The Troubleshooting checklist and Clear the Figma desktop app cache guides cover a few more steps if the above doesn't clear things up.

Thanks both for your patience while we get to the bottom of this one!

Etienne Ledemay
New Member
September 17, 2026

I use the desktop app, Tahoe 26.2

Since my previous message, I removed all the dynamic effects on the strocks and everything is back to normal. I used it on typographic elements and the issue started when I have duplicated an artboard containing those elements.

Gayani_S
Figmate
Community Support
September 17, 2026

Hey ​@Etienne Ledemay, thanks for following up with that extra detail!

When you say "dynamic effects on the strokes," were you using drop shadow or inner shadow (with the blur set to zero) to fake a stroke look? Figma doesn't currently support independent multiple strokes on text layers, so a lot of designers achieve that look this way instead, and it'll help our team know exactly where to look.

 

Could you please submit a bug report through the Support Hub. That way you can attach the file (or a short screen recording of it happening) and our team can look at the reproduction directly.

It'd help to include:

  • The steps you outlined here (duplicating a frame with text layers using those effects)
  • Whether it's reproducible in a fresh file or specific to that one

 

Thank you so much for your help!