Swapping instances in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Instance Swapping in Figma

In Figma, what happens when you swap an instance of a component with another instance of a different component?

A Swapping instances is not possible in Figma; you must delete and add a new instance.

B The new instance replaces the old one, keeping all overrides like text and colors intact where possible.

C Both instances merge their properties, combining overrides from both components.

D The new instance replaces the old one but all overrides are lost and reset to default.

💡 Hint

Think about how Figma preserves your custom changes when you swap components.

When you swap instances in Figma, the new component replaces the old one but keeps overrides like text, colors, and other property changes where they apply. This helps maintain your customizations.

🎯 Scenario

intermediate

Swapping Instances with Nested Components

You have an instance of a button component that contains a nested icon component. You want to swap the button instance with another button variant that uses a different icon. What happens to the nested icon instance when you swap the button instance?

A The nested icon instance is swapped to the new variant's icon, but any overrides on the icon are preserved.

B The nested icon instance remains the same as before, ignoring the new button variant's icon.

C The nested icon instance is deleted and replaced with a default icon with no overrides.

D Swapping the button instance does not affect nested components at all.

💡 Hint

Consider how nested instances behave when their parent instance is swapped.

When swapping a parent instance, nested instances update to match the new component's structure, but any overrides on those nested instances are preserved where possible.

🔧 Formula Fix

advanced

Why Overrides Are Lost After Swapping?

You swapped an instance of a card component with another variant, but all your text and color overrides disappeared. What is the most likely cause?

A You swapped the instance using copy-paste instead of the swap feature.

B Figma does not support preserving overrides when swapping instances.

C Overrides are only preserved if the components share the same parent frame.

D The new component variant has different layer names or structure, so overrides cannot map correctly.

💡 Hint

Think about how Figma matches overrides to layers inside components.

Overrides are matched by layer names and structure. If the new component variant has different layers or names, Figma cannot apply the overrides, so they are lost.

❓ visualization

advanced

Visualizing Instance Swap Effects

You have a dashboard showing two side-by-side instances of a card component: one original with overrides and one after swapping to a new variant. Which visualization best shows the differences caused by swapping?

A A line graph showing the number of layers in each component variant over time.

B A pie chart showing the percentage of overrides preserved versus lost.

C A side-by-side comparison highlighting changed text and color fields in the swapped instance.

D A bar chart comparing the file sizes of the original and swapped components.

💡 Hint

Think about what helps you see what changed visually after swapping.

A side-by-side comparison with highlights on changed properties clearly shows what overrides remain or changed after swapping instances.

❓ data_modeling

expert

Modeling Component Instance Swapping Logic

In a BI tool tracking Figma design changes, you want to model how swapping instances affects overrides. Which data model best captures the relationship between components, instances, and overrides to analyze swap impact?

A A relational model with tables for Components, Instances, Overrides, and a mapping table linking Overrides to Instances and Components.

B A flat table listing all overrides with component and instance names combined in one column.

C A single table with columns for component name, instance ID, and a JSON column storing all overrides as text.

D A star schema with a fact table for overrides and dimension tables only for components.

💡 Hint

Consider how to represent many-to-many relationships and preserve detailed override info.

A relational model with separate tables for Components, Instances, and Overrides, plus mapping tables, allows detailed tracking of which overrides belong to which instance and component, enabling analysis of swap effects.

Practice

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

1. 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.

2. 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.

3. Final Answer:

   Replace one component instance with another while keeping custom changes -> Option A

4. Quick Check:

   Swapping instances = Replace component keeping edits [OK]

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

1. 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.

2. Step 2: Evaluate other options

   Double-clicking edits text, dragging replaces layers but not swap instance, deleting loses custom changes.

3. Final Answer:

   Right-click the instance and select 'Swap Instance', then choose the new component -> Option D

4. 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

1. Step 1: Understand what swapping preserves

   Swapping keeps custom overrides like text and fill color unless the new component lacks those properties.

2. 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.

3. Final Answer:

   The instance changes to the new button's shape, but keeps the red fill and the text 'Submit' -> Option C

4. 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

1. 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.

2. 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.

3. Final Answer:

   The new component does not have the same color properties exposed for overrides -> Option B

4. 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

1. Step 1: Understand the goal

   You want to update the base card style globally but keep each instance's custom text and colors intact.

2. 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.

3. Final Answer:

   Select all card instances and use the 'Swap Instance' option to replace them with the new card component -> Option A

4. 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