Skip to main content

Component instances inside slots still reference original page components after page duplication

  • June 1, 2026
  • 3 replies
  • 30 views
PierreMo

Hi,
I’m experiencing an issue when duplicating a page that uses a design system component with a slot.

Steps to reproduce:

  1. In a working file, create “Page v1”.
  2. Add an instance of a design system component that contains a slot, for example a modal.
  3. On “Page v1”, create a local component, for example a data table.
  4. Place an instance of this local component inside the modal slot.
  5. Duplicate “Page v1” to create “Page v2”.

Expected behavior:

The component instance inside the slot on “Page v2” should reference the duplicated local component from “Page v2”.

Actual behavior:

The local component is duplicated correctly on “Page v2”, but the instance inside the slot still references the original component from “Page v1”.

This makes duplicated pages unreliable for versioning, because some nested instances still depend on the previous page.

Could you confirm if this is expected behavior or a bug?

Thanks!

3 replies

Jaycee Lewis
Figmate

Hey hey ​@PierreMo 👋 Thanks for the detailed steps and clean write-up, always helpful 🙌

Two quick troubleshooting questions:

  • When you select the instance inside the slot on Page v2, what does the right sidebar show as its main component — the v1 copy or the v2 copy? (The panel labels the source; we want to confirm it's a true reference and not just visually unchanged.)

  • Is the modal (the slot host) a local component in this file, or one published from a library? That can affect how Figma scopes the remap during duplication

 

And one simple isolation test:

On Page v1, place your local component (the data table) instance twice — once inside the modal slot, and once as a plain instance sitting free on the canvas. Then duplicate to Page v2 and check both in the right sidebar.

  • If both still point to v1 → this is may not be not slot-specific

  • If only the slotted one points to v1 while the free one re-points to v2 → that's something we can look at deeper

If you're able to share the following, it'll let the team reproduce quickly:

  • A screen recording of the duplication and both right sidebar checks. Recording full screen so the right sidebar is completely visible is best if possible

  • Full-screen screenshots of each instance selected with the right sidebar

Thanks for the additional information! — Jaycee 

PierreMo
  • PierreMo
  • Author
  • New Member
  • June 2, 2026

Hi Jaycee, thanks for the quick reply :)

Regarding the first two questions:

Yes, the component on Page v2 is an instance linked to the component on Page v1.

I discovered the issue when editing the component on Page v2 and not seeing the changes applied. I then selected the instance inside the modal and clicked “Go to main component”. That’s when I noticed it took me back to Page v1.

The modal is a component from a published library, my design system file, and it uses slots.


For the quick test, I tried again with another instance of the same local component placed outside the slot.

Result:

  • The instance inside the slot on Page v2 is linked to the component on Page v1.

     

  • The instance outside the slot on Page v2 is linked to the component on Page v2.
     

     

Based on this test, it seems that the issue is related to the slot.

Unfortunately, I won’t be able to share a screen recording publicly due to an NDA. Do you have a private way for me to send you the video?

 

Pierre

Jaycee Lewis
Figmate

Hey, ​@PierreMo 👋 Thank you very much! I took it to my internal resources for more clarity on expected behaviour here. I’ll follow up as soon as I have more info or more questions 🤩 — Jaycee

Terms & ConditionsAccessibility statement