Skip to main content
Wen0620
Wen0620
New Member
January 8, 2026
Question

Better Change Tracking for Updated Components in Design Systems

  • January 8, 2026
  • 1 reply
  • 101 views

Hi Figma community đź‘‹

Our team manages a shared design system that is actively evolving, and we frequently update components to improve usability and consistency.

One challenge we often face is tracking component updates across project files. While Figma provides version history and “Compare with previous versions,” identifying changes requires opening each component individually. This becomes especially time-consuming when updates affect many components or multiple screens.

It would be extremely helpful if Figma could provide better visibility into component changes, such as:

  • Notifications when a referenced component has been updated

  • Visual indicators showing which components have changed

  • A clearer diff or change log for component updates

This kind of functionality would greatly help designers, PMs, and developers understand whether updates require action on existing designs.

Curious if other teams managing large design systems experience the same challenge? How are you currently handling this?

Thanks for reading — and thanks to the Figma team for continuously improving the platform!

    1 reply

    Alejandro_Carle_Naon
    Alejandro_Carle_Naon
    New Participant
    September 15, 2026

    When a component property gets deleted and a new one is created under the same visible label, there's no way today to tell that apart from a simple rename — the Plugin API doesn't expose it. We end up guessing based on internal key hashes, which breaks in some cases (property recreated under the same name, but with a different identity).

     

    A similar gap was reported back in 2024 for nested instance variant overrides: https://forum.figma.com/report-a-problem-6/changes-overrides-of-componentproperties-not-exposed-via-the-plugin-api-24016 — went unanswered, but the underlying issue is still there.

     

    Request: when a library gets republished, expose a structured changelog of what changed per component — properties added/removed/renamed, and whether a removed-then-re-added property should count as the same one or not. Even just added/removed keys per component would let us stop guessing.

     

    Thanks for considering this.

    Terms & ConditionsAccessibility statement