Slots Open Beta

What Are Figma Slots?

Figma Slots are a new native component primitive that introduces a designated container layer inside any component — visually bordered in the editor — where designers can freely add, remove, reorder, and customize child content without losing the connection to the main component or parent design system.

In Figma's component model prior to Slots, customization was deliberately constrained. If a designer needed a dropdown list component to show five items instead of three, they had two options: use hidden layers pre-baked into the component (which had to be unhidden one by one and couldn't be reordered), or detach the component entirely — severing its link to the design system and making design-to-development handoff significantly harder. Slots eliminate this false choice.

How Slots Work

A slot is a special layer type (SlotNode) that component authors define within their components. When a library consumer opens an instance of that component, they see the slot boundary and can place any content within it — text, icons, nested component instances, or arbitrary layers — without touching the main component itself.

Component authors retain control over the slot's behavior through a set of constraints:

• Preferred values: Authors specify which component types are recommended for placement inside each slot, ensuring design system compliance.
• Default content: Components ship with sensible defaults (for example, a checkboxGroup might default to three checkbox instances inside its items slot).
• Quantity rules: Minimum and maximum item counts can be documented, giving design system consumers clear guidance on what the component supports.

This architecture maps closely to how component slots work in modern web frameworks — making design-to-code translation more semantically accurate.

Problems Slots Solve

Before Slots, design system teams relied on three common workarounds, each with serious drawbacks:

Instance swapping required separate component assets to represent different configurations and was ergonomically awkward. Hidden nested instances created file performance problems, prevented reordering, and forced designers to hunt through deep layer hierarchies to unhide the right item. Quantity props ("count: 1/2/3/4/5") caused variant explosion and conflated configuration with composition, making components unwieldy to maintain.

Slots replace all three anti-patterns with a single, expressive primitive. Design system architects can now offer genuinely composable components — where users add what they need and remove what they don't — while still defining the "preferred" shape of a slot.

Who Gets Access

Slots are available as of March 5, 2026, to all users with Full seats on any Figma plan. There is no additional cost to access or use the feature. Users who were part of the early access program continue to have access; the open beta simply extends availability to all eligible seats.

Impact on Design Systems

The design systems community has responded with significant enthusiasm to the Slots launch. Nathan Curtis, one of the most cited voices in design systems practice, published multiple preparatory guides through early 2026 — covering implementation strategies, how to architect components around native slots for repeating patterns, and how Slots will gradually reshape which component props are necessary versus which can now be replaced by composition.

For teams maintaining shared component libraries, the Slots open beta is the beginning of a migration opportunity, not an overnight change. Libraries authored before Slots will continue working as-is. Teams can incrementally introduce slot-capable versions of their components, starting with repeating-item patterns like tab groups, breadcrumbs, button groups, and avatar stacks — patterns where the old workarounds were most painful.