Overview
Inspect tab in SXL Studio: node inspection, token bindings, instance recovery, drift tracking, and binding management.
What Inspect is for
Every Figma design is a tree of nodes: frames, text, components, instances. Over time, connections between nodes and the design system can break: a variable gets deleted, a component moves to another library, a style is renamed, a composition becomes outdated. Finding and fixing such issues manually takes hours.
Inspect shows the full picture of a selected object: which tokens and variables are bound to each property, which instances are "broken", where the design has drifted from the JSON description, and provides tools for instant fixes.
What you get
- Node tree — hierarchy of the selected object with types, names, and status indicators
- Token bindings — complete list: which token is bound to which property of each node
- Swap — rebind variables and styles from one collection to another
- Rebind — replace an instance's main component while preserving overrides
- Composition Drift — detect discrepancies between the design and JSON composition
- Cross-file Sync — synchronize variables between Figma files
- Import / Export — data loading and export, image export
Interface
Sidebar — node tree
When you select an object in Figma, a tree of its hierarchy appears on the left:
- Indentation shows nesting depth
- Icon corresponds to the node type (frame, text, component, instance)
- Name — the layer name in Figma
- Status indicators for instances:
- 🔴 Broken — main component not found
- 🌐 Remote — component from another file
- 🔗 Linked — bound to a local component
- Binding count — number of tokens bound to the node
- Composition label — if the node was created from a Composition token
Clicking a node in the tree opens its details in the main panel.
Main panel
For the selected node, you see:
- Header — node name, type, Composition / Template badges
- Binding count — total number of token bindings
- Action buttons — Swap, Unlink All
- Data sections:
- Composition Tracking — tracking the connection to JSON composition
- Out of Sync (Drift) — discrepancies with JSON
- Instance Recovery — Rebind tools
- Token Bindings — binding table with Override and Unlink options
When to use
| Scenario | What to do in Inspect |
|---|---|
| Component lost its library connection | Rebind — specify a new component ID |
| Need to migrate to local variables | Swap — rebind the collection |
| Composition was updated in JSON but the design is outdated | Drift → Re-apply |
| Unsure which tokens are used on an element | Token Bindings — full list |
| Need to remove all bindings | Unlink All — recursive cleanup |
| Sync variables from another file | Cross-file Sync |
Related sections
- Swap — rebinding variables and styles
- Rebind — replacing the main component
- Token Bindings — managing bindings
- Composition & Drift — tracking discrepancies
- Cross-file Sync — syncing between files