Locals Only!

About this plugin

Locals Only! re-binds all applied styles and variables on your selection to the current file’s local styles and variables. It can even update variables applied to component properties.

Why Locals Only!?

Resolves every applied style, variable and/or component by looking for a matching name in the current file.

1. Preview local variable behavior of published designs from within a branch.
2. Move components between templates and product files, and easily sync them to the product file.

How to use

1. Select one or more layers.
2. Decide whether or not you want to localize components.
3. Click Analyze to generate the scope of the updates.
4. Click Go Local to reapply local styles, variables and components to your selection.

Swapping Components (NEW)

Use the toggle next to the component section to include or exclude localizing matching components.

Components OFF applies local styles and variables to the full tree: the selection and every descendant, including inside instances.

1. Use this when you only want to preview local styles and variables while keeping instance links as they are.
2. Useful for branch previews.

Components ON swaps each instance to a matching local component by name (when one exists). Nested instances inside swapped components are swapped too, so everything ends up pointing at the current file.

1. Use this when you want instances to become local components and still get local styles and variables. It will additional apply matching local styles and variables if they exist outside of components.
2. Useful for component migration.

Details and limitations

1. Matching is by style or variable name only (for variables, the collection name must also match).
2. The plugin does not create styles or variables; it only rebinds to existing local ones with the same name.
3. Large selections can take some time; consider batching to avoid freezing the tab.