Swapping instances in Figma - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'Swapping instances' mean in Figma?

Swapping instances means replacing one component instance with another while keeping the same position and overrides.

beginner

How do you swap an instance in Figma?

Select the instance, then use the right sidebar's 'Instance' section to choose a different component from the dropdown.

intermediate

Why is swapping instances useful in design workflows?

It lets you quickly change designs without rebuilding layouts or losing custom changes like text or colors.

intermediate

What happens to overrides when you swap instances in Figma?

Overrides like text changes or colors are preserved if the new component has matching properties.

advanced

Can you swap instances between components from different libraries in Figma?

Yes, as long as the components are published and accessible, you can swap instances across libraries.

What is the first step to swap an instance in Figma?

A Delete the current instance

B Select the instance you want to swap

C Create a new component

D Open the layers panel

You must first select the instance before you can swap it with another component.

When swapping instances, what happens to custom text overrides?

A They are preserved if the new component supports the same text fields

B They are always lost

C They become default text

D They turn into images

Overrides like custom text stay if the new component has matching text fields.

Can you swap an instance with a component from a different Figma library?

A No, only components in the same file

B Only if you copy the component first

C Yes, if the library is published and accessible

D Only with plugins

Figma allows swapping with components from any published and accessible library.

What is preserved when swapping instances in Figma?

A Position and overrides

B Only position

C Only overrides

D Nothing is preserved

Swapping keeps the instance's position and any overrides applied.

Why might you want to swap instances instead of deleting and adding new ones?

A To export faster

B To reduce file size

C To change colors automatically

D To keep layout and overrides intact

Swapping saves time by keeping layout and custom changes without rebuilding.

Explain how swapping instances works in Figma and why it is helpful.

Think about changing a design piece without losing your edits.

Describe what happens to overrides when you swap instances between components.

Consider what stays the same and what might change.

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