
Figma is releasing Slots to general availability on March 5, bringing a long-awaited component architecture feature out of beta and into the hands of all design teams. The company announced on LinkedIn that the feature will begin rolling out Wednesday.
Slots fundamentally changes how designers work with components by allowing them to swap content inside instances without detaching from the main component. This addresses one of the most persistent pain points in component-based design systems: the choice between maintaining component connections or customizing content.
How Slots Changes Component Workflows
Traditionally, designers who needed to customize a component instance, such as replacing placeholder text or swapping an icon, had to detach the instance from its main component. This broke the connection to the design system, meaning future updates to the component wouldn't propagate to the detached instances. Teams were forced to choose between flexibility and maintainability.
Slots introduces designated areas within components where designers can insert custom content while preserving the link to the main component. A button component, for example, might have slots for an icon, label text, and badge, each swappable without detaching. Style properties, layout rules, and other component characteristics continue to update from the main component even as the content changes.
This capability becomes especially powerful in design systems with complex components. Navigation bars, card layouts, and form elements often require content variations across different screens while maintaining consistent structure and styling. Slots makes these variations possible without fragmenting the design system.
From Beta to Production
Figma launched Slots in open beta in late 2024, giving design teams several months to test the feature in real-world projects. The beta period allowed Figma to gather feedback on performance, edge cases, and integration with existing workflows before committing to general availability.
The March 5 rollout follows a broader pattern of Figma shipping infrastructure improvements alongside its AI initiatives. Earlier this year, the company launched a Codex MCP server for bidirectional design-to-code workflows and expanded MCP server integration to five AI code editors. These moves signal a platform strategy that balances core design tool improvements with AI-powered automation.
Impact on Design Systems
For organizations with established design systems, Slots represents both an opportunity and a migration challenge. Teams will need to retrofit existing components to take advantage of the new architecture, defining which elements should become slots and updating documentation accordingly. The payoff is a more resilient design system that accommodates variation without sacrificing consistency.
Smaller teams and individual designers benefit from reduced friction in the design process. The ability to customize components without losing their connection to a library makes it easier to maintain quality and consistency, even when working quickly or without formal design system governance.
The general availability announcement comes as no-code and AI-assisted design tools continue to blur the lines between design and development. Platforms like Lovable, Bolt, and v0 are changing how products get built, often bypassing traditional design handoff entirely. Figma's response appears to be strengthening its position as the source of truth for design systems while building bridges to code through features like Slots and its MCP integrations.
The March 5 rollout will be gradual, with availability expanding across accounts over the following days. Teams currently using the beta version should see no disruption as the feature transitions to general availability.
Sources
1 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.







