Understand how swapping instances in Figma helps quickly update dashboard visuals by replacing one design component with another without losing layout or styles.
Sample Data
Component Name
Type
Current Instance
Available Instances
Sales Chart
Chart
Bar Chart
Bar Chart, Line Chart, Pie Chart
Region Filter
Filter
Dropdown
Dropdown, Checkbox List
KPI Card
Card
Total Sales
Total Sales, Average Sales, Sales Growth
Time Selector
Control
Date Range Picker
Date Range Picker, Month Selector
Legend
Info
Color Legend
Color Legend, Symbol Legend
Dashboard Components
Sales Chart: A bar chart instance showing sales by region. Swappable with line or pie chart instances to change visualization style.
Region Filter: Dropdown instance to select regions. Can swap to checkbox list for multi-select.
KPI Card: Displays total sales as a card instance. Can swap to average sales or sales growth cards.
Time Selector: Date range picker instance to filter data by time. Swappable with month selector instance.
Legend: Color legend instance explaining chart colors. Can swap to symbol legend instance.
The Region Filter and Time Selector control the data shown in the Sales Chart and KPI Card. Swapping the Sales Chart instance changes the chart type but keeps the data and filters connected. Swapping the Region Filter instance changes the selection style but maintains filtering functionality. Swapping the KPI Card instance changes the metric displayed but updates dynamically with filters.
Self Check
If you swap the Sales Chart instance from a bar chart to a pie chart, which components update their appearance and which keep their data?
Sales Chart: Appearance changes to pie chart style but data remains filtered by region and time.
KPI Card: Remains the same, showing total sales filtered by selections.
Region Filter and Time Selector: No change in appearance or data.
Legend: Updates to match the pie chart color scheme.
Key Result
A Figma dashboard demonstrating how swapping instances updates visuals while keeping data and filters connected.
Practice
(1/5)
1. What does swapping instances in Figma allow you to do? Swapping instances means:
easy
A. Replace one component instance with another while keeping custom changes
B. Delete a component from the design permanently
C. Create a new component from scratch
D. Group multiple layers into a frame
Solution
Step 1: Understand the purpose of swapping instances
Swapping instances means replacing one component instance with another without losing custom edits like colors or text.
Step 2: Compare options with this definition
Only Replace one component instance with another while keeping custom changes describes this behavior correctly; others describe unrelated actions.
Final Answer:
Replace one component instance with another while keeping custom changes -> Option A
Hint: Swapping keeps your edits but changes the base component [OK]
Common Mistakes:
Thinking swapping deletes components
Confusing swapping with creating new components
Assuming swapping groups layers
2. Which of the following is the correct way to swap an instance in Figma?
easy
A. Delete the instance and insert the new component manually
B. Double-click the instance and type the new component name
C. Drag the new component over the instance and drop it
D. Right-click the instance and select 'Swap Instance', then choose the new component
Solution
Step 1: Recall the swapping method in Figma
Swapping is done by right-clicking the instance and selecting 'Swap Instance' to pick a new component.
Step 2: Evaluate other options
Double-clicking edits text, dragging replaces layers but not swap instance, deleting loses custom changes.
Final Answer:
Right-click the instance and select 'Swap Instance', then choose the new component -> Option D
Quick Check:
Swap via right-click menu = Right-click the instance and select 'Swap Instance', then choose the new component [OK]
Hint: Use right-click menu to swap instances quickly [OK]
Common Mistakes:
Trying to swap by double-clicking
Dragging components over instances thinking it swaps
Deleting instance instead of swapping
3. Given a Figma file with a button component instance that has custom text 'Submit' and a red fill, what happens if you swap this instance with a different button component that has a blue fill and default text 'Click'? Choose the correct outcome.
medium
A. The instance keeps the old button's red fill and text 'Submit' without any change
B. The instance changes to the new button but resets text to 'Click' and fill to blue
C. The instance changes to the new button's shape, but keeps the red fill and the text 'Submit'
D. The instance disappears and must be recreated
Solution
Step 1: Understand what swapping preserves
Swapping keeps custom overrides like text and fill color unless the new component lacks those properties.
Step 2: Apply this to the example
The text 'Submit' and red fill are custom changes, so they remain after swapping to the new button shape and style.
Final Answer:
The instance changes to the new button's shape, but keeps the red fill and the text 'Submit' -> Option C
Quick Check:
Swapping keeps custom text and fill [OK]
Hint: Swapping keeps your edits, changes base component shape [OK]
Common Mistakes:
Assuming swapping resets all properties
Thinking swapping deletes the instance
Believing swapping keeps old component shape
4. You tried swapping an instance in Figma but the custom color changes disappeared. What is the most likely cause?
medium
A. You swapped the instance with a frame instead of a component
B. The new component does not have the same color properties exposed for overrides
C. Swapping always resets all custom changes
D. You forgot to save the file before swapping
Solution
Step 1: Identify why custom colors might be lost
If the new component lacks matching color properties exposed for overrides, custom colors cannot be preserved.
Step 2: Evaluate other options
Saving the file doesn't affect swapping, swapping does not always reset changes, and swapping with a frame is not possible.
Final Answer:
The new component does not have the same color properties exposed for overrides -> Option B
Quick Check:
Missing override properties cause lost custom colors [OK]
Hint: Check if new component exposes same override properties [OK]
Common Mistakes:
Assuming swapping always resets changes
Blaming unsaved file for lost changes
Trying to swap with non-component frames
5. You have a dashboard design with multiple instances of a card component, each customized with different text and colors. You want to update the card style globally by swapping all instances to a new card component with a modern look, but keep each card's custom text and colors. What is the best approach?
hard
A. Select all card instances and use the 'Swap Instance' option to replace them with the new card component
B. Manually replace each card instance by deleting and adding the new component, then reapply custom text and colors
C. Create a new frame and copy all custom text and colors into new card components inside it
D. Use the 'Detach Instance' option on all cards, then replace them with new components
Solution
Step 1: Understand the goal
You want to update the base card style globally but keep each instance's custom text and colors intact.
Step 2: Evaluate methods
Swapping all instances preserves custom overrides while updating the base component. Manual replacement loses overrides and wastes time. Detaching instances removes link to components, losing benefits.
Final Answer:
Select all card instances and use the 'Swap Instance' option to replace them with the new card component -> Option A
Quick Check:
Swap all instances to update style, keep custom edits [OK]
Hint: Swap all instances at once to keep custom edits and update style [OK]
Common Mistakes:
Deleting and recreating instances losing customizations
Detaching instances losing component benefits
Copying text/colors manually wasting time
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.