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.
