Skip to main content
Solved

Figma slots do not pass on component properties

  • March 13, 2026
  • 6 replies
  • 1201 views
Bohdan 619

Hi there,

I've been exploring the new Slots feature, but I noticed that slots currently do not pass through the properties of the inner components (instances) placed inside them.

Are there plans to make internal component properties available within slots in upcoming versions? This would greatly improve the flexibility of the new workflow.

Thanks!

Best answer by Celyn_L

Hi everyone — thanks for your patience, and for sharing these examples — they’re really helpful in highlighting how this is showing up in real workflows.

At the moment, component properties (like variants or values) from instances placed inside Slots can’t be controlled or passed through via the Slot itself. Similarly, interactions like hover states on nested components may not behave as expected once placed inside a Slot, even if they work correctly on their own.

This is expected with how Slots work today, and is also consistent with how instances behave more broadly in Figma.

That said, we can see how these limitations impact flexibility — especially when working with interactive or variant-driven components — and the team has heard this feedback and is continuing to explore ways to improve the experience.

As a workaround, if you’re trying to control things like variants or values within slots, using variables and modes can help achieve some of that flexibility.

Really appreciate you all sharing these use cases — they’re valuable as we continue shaping how Slots evolve 🙌

    6 replies

    james-anyteam

    I have a simple component with a hover state. This component is embedded into a slot (which is obviously part of another component). So it’s; Main component>Slot>Nested Component (with hover state). My nested component works fine on its own, but once added to the slot, it loses its hover state.

     

    See video with more detail: 

     

      Denis719k
      • Denis719k
      • New Member
      • March 13, 2026

      It seems to me that this only works with components that contain nested instances, and the slot doesn't pass them along.
      I found a solution, but it looks like a workaround.
      https://www.linkedin.com/posts/denys-dod_figma-productdesign-web3-activity-7437838057573138432-xAMs

        Celyn_L
        Figmate
        • Celyn_L
        • Figmate
        • March 16, 2026

        Hi ​Everyone, Celyn from Figma Community Support here.

        Thanks all for taking the time to share these details and for exploring the new Slots feature.

        ​@Bohdan 619  ​@james-anyteam — I’ve noted the feedback you both shared and passed it along to the team so they’re aware of how these behaviors are impacting real workflows and can review them more closely as the feature continues to evolve.

        Thanks as well ​@james-anyteam for the screen recording, it’s really helpful, and I’ve shared that with the team too.

        ​@Denis719k — appreciate you sharing your observations and the workaround you found, as well as the resource with the community.

        I’ll follow up in this thread if there are any updates I can pass along.

        Really appreciate you all taking the time to document these cases and flag them here 🙌

          Celyn_L
          Figmate
          • Celyn_L
          • Figmate
          • Answer
          • April 9, 2026

          Hi everyone — thanks for your patience, and for sharing these examples — they’re really helpful in highlighting how this is showing up in real workflows.

          At the moment, component properties (like variants or values) from instances placed inside Slots can’t be controlled or passed through via the Slot itself. Similarly, interactions like hover states on nested components may not behave as expected once placed inside a Slot, even if they work correctly on their own.

          This is expected with how Slots work today, and is also consistent with how instances behave more broadly in Figma.

          That said, we can see how these limitations impact flexibility — especially when working with interactive or variant-driven components — and the team has heard this feedback and is continuing to explore ways to improve the experience.

          As a workaround, if you’re trying to control things like variants or values within slots, using variables and modes can help achieve some of that flexibility.

          Really appreciate you all sharing these use cases — they’re valuable as we continue shaping how Slots evolve 🙌

            Dominic
            • Dominic
            • Active Member
            • August 18, 2026

            ​@Celyn_L This doesn’t seem to be the case as Figma’s own Simple Design System allows for editable properties on elements within slots. See Figma’s card component example below (card instance selected, not variant).

            Experimenting with my own components its buggy and very hit and miss. I was not able to recreate a card where all text properties were accessible inside a slot. Nested instances were 50/50.

            Agents assessment: 
            The `Body2` slot proves that slot sublayers can have `componentPropertyReferences` — its children have working refs (Heading#280:0, Body#280:13, etc.). However, the Plugin API actively blocks setting `componentPropertyReferences` on slot sublayers and strips them when a node with refs is moved into a slot.

             

            Celyn_L
            Figmate
            • Celyn_L
            • Figmate
            • August 21, 2026

            Hi ​@Dominic, thanks for following up and for sharing this example from the Simple Design System. This is really helpful context.

            I understand that you’re seeing inconsistent results when trying to recreate a similar setup with your own components, particularly with text properties and nested instances within Slots.

            I’ve gone ahead and created a support ticket for you so that the team can take a closer look. Your ticket number is #2084203.

            It will be really helpful if you could reply directly to the ticket with a link to a test file where you’re able to reproduce the behavior, and invite support-share@figma.com with “Can View” access (this won’t impact your billing and will allow us to reproduce the issue and investigate further with Engineering).

            If possible, a short screen recording showing how you’re setting up the Slot and where the properties become unavailable or behave inconsistently would also be really helpful.

            Someone from the team will follow up with you directly through the ticket. Thanks again for taking the time to test this and document what you found!

            Terms & ConditionsAccessibility statement