Video summary
Master plugin for Figma — Video Guide
Main summary
Key takeaways
Summary (Technological Concepts / Product Features)
The video is a guide to the Master plugin for Figma, focused on making component workflows faster and safer, especially while preserving overrides (e.g., text, icons/images, colors).
Main features demonstrated
-
Create a component from existing objects
- Start with regular frames/objects that have similar structure (e.g., song frames).
- Use “Create component from objects” in the plugin.
- The plugin generates a new component and converts the selected items into its instances.
- Key benefit: overrides are preserved automatically (texts/icons/images remain updated on instances).
-
Link objects to an existing component (instead of creating a new one)
- When you already have a component you want to reuse:
- Set the plugin’s target component (via a command such as “Set target component” / “Set target component”).
- Run “Link objects to target component” on the selected frames.
- Result: frames become instances of the existing component, and overrides (text/images) are kept.
- When you already have a component you want to reuse:
-
Duplicate/clone component variants safely
- Useful when you want to change one instance without affecting others.
- Example: one shared component across two screens; you want to update only the second screen’s artist page.
- Approach shown:
- Select the target instances (plus their main component).
- Use Master → create component from objects to generate a copied component.
- Benefit: editing the copied component updates only its own instances, not the original.
-
Merge two similar components into one without losing overrides
- To consolidate components:
- Choose the target component to keep.
- Select instances of the component you want to remove/discard.
- Link them to the target component.
- Benefit: all instances link to one component, and the extra component can be deleted without sacrificing images/icons/colors (unlike some basic swap methods).
- To consolidate components:
-
Workaround for moving main components across files
- Figma limitation noted: moving a main component to another file while keeping instance connections isn’t supported yet.
- Master workaround:
- Publish/copy the component to a library file (requires Teams / Professional / Education / Org plans).
- Then swap local instances to the library component.
- Automation detail:
- Master can locate all instances of a local component in the file and link/swap them to the library version automatically.
- After linking, the local component can be safely deleted.
-
Multiple ways to swap components
- The guide mentions component swapping can be done in three different ways (Master provides one method).
- General principle: Master is designed to preserve overrides; default Figma methods may be faster sometimes—choose based on the situation.
Tutorial/Guide resource
- Mentions the Master plugin guide here: dominate.design/guide
Free trial and closing
- The creator encourages viewers to try Master for free and to reach out with feedback/questions.
Main speakers / sources
- The video creator/presenter (no specific name given in the subtitles), speaking directly in a “video guide” format.
- Source referenced: Master plugin guide at dominate.design/guide.