Skip to main content
_logeast
March 17, 2023

[LAUNCHED] Add a "slot" functionality to components

  • March 17, 2023
  • 44 replies
  • 8554 views

My suggestion for Figma is to add a “slot” functionality to components.

This would allow designers to create more flexible and customizable components, by adding empty slots or placeholders within a component. Users could then insert their own content or elements into these slots, without having to ungroup or modify the component itself.

This functionality would save time and increase efficiency for designers, while also promoting a more consistent design system across a project or organization.

I believe this feature would greatly enhance the flexibility and usability of Figma’s component system, and would be a valuable addition to the platform.

44 replies

Taun
New Member
November 28, 2025

@WellyKake , there are bearable workarounds, like using Components and not slotting like we do as developers. For some reason Figma isn’t following a standard development workflow and architecture, so we have to modify our thought process and workflow to suit the Figma way. It’s not terrible, but yea it’s not ideal.

Jonathen
New Participant
January 21, 2026

Someone may have already mentioned this or it may be a related topic but also making the nested components duplicatable within a parent instance. For example, a tab list with multiple tabs within it. Currently, I am having to make more tabs than I think I will need just so I can always have enough. If i try to duplicate a tab within the parent via copy/paste it just creates an instance of the nested component below the parent😣 (im kinda new)

I can see where this might cause an issue with prototyping but if the same logic is applied to each tab perhaps it is possible

Andrew Jones
New Member
February 8, 2026

I’m a developer of 30+ years, and finding myself getting back to doing more UI design. I’ve been consuming a LOT of educational materials on Figma and I very quickly ran into this stumbling block. I’m trying to make this work with instance swaps, but A) it’s limited to swapping in only one component at a time, and B) it’s completely unrealistic to have to make components out of all possible content variations. I think mimicking the “slot” architecture of every modern frontend tool feels like a no-brainer, and I hope Figma is hearing the feedback here (although it’s disturbing this thread was started 2 years ago).

Update: Not long after posting this, I saw that Slots has indeed been announced. I’ve signed up for Early Access, but it’d be great to know more about an official release date. Video: 

 

ksn
Figmate
Community Support
March 5, 2026

Hello everyone! Happy to announce that Slots is now in open beta, and is starting to roll out to all full seat / Starter+ users today.

 



Learn more about how we are rolling out slots to you.