Inspect

Cross-file Sync

Compare and sync variables from another Figma file using Sync modal: requirements, scope, and current behavior.

Where this tool lives

Cross-file Sync is opened from:

  • Footer -> Sync -> Cross-file Sync.

It is related to Inspect workflows, but it is not inside the main Inspect node panel.

What it does

Cross-file Sync compares variables from a remote Figma file with local variables in the current file and applies selected changes.

Current implementation is focused on:

  • creating missing variables;
  • updating changed variable values.

It does not delete local variables automatically.

Requirements

  • remote Figma File Key;
  • Personal Access Token with access to that file;
  • Figma plan/API access that allows GET /v1/files/:key/variables/local.

If REST access is restricted, the plugin returns an explicit enterprise/permission message.

Step-by-step

  1. Open Sync -> Cross-file Sync.
  2. Enter File Key and Personal Access Token.
  3. Click Compare Variables.
  4. Review result by collection.
  5. Select entries to apply.
  6. Click Sync N variables.
  7. Review created/updated/error counters.

How compare works right now

Remote/local matching key:

  • collectionName + variableName

Per variable, comparison currently uses first mode value from remote vs first mode value from local.

Statuses used in current compare/apply flow:

  • New (added)
  • Changed
  • Same

Removed exists as a technical status type, but it is not currently used as an apply action.

Default selection includes actionable added + changed entries.

Apply behavior

When applying selected entries:

  • missing collections are created locally by name;
  • added variables are created with resolved type and first-mode value;
  • changed variables are updated in the local first mode;
  • unsupported types or write errors are listed in result errors.

Practical limits

  • Comparison/apply is value-focused, not full metadata parity.
  • Current apply flow is additive/update-only (no automatic deletions).
  • Results depend on Figma API availability, permissions, and token validity.