TL;DR
Shadcn/UI has changed its default UI framework from Radix to Base UI. This update affects how developers implement and customize components, signaling a shift in the library’s design approach.
Shadcn/UI has shifted its default UI framework from Radix to Base UI, a move confirmed by the project maintainers. This change influences how developers integrate UI components within their projects and marks a strategic shift in the library’s design choices.
According to the official Shadcn/UI documentation and release notes, the library now defaults to Base UI for its component styling and behavior, moving away from the previously standard Radix framework. This update was publicly announced on the project’s GitHub repository and community channels in March 2024.
Developers using Shadcn/UI will notice that new projects will initialize with Base UI as the default, while existing projects may require configuration updates to switch back to Radix if desired. The maintainers cited reasons such as better integration with current design trends and improved developer experience as motivations for the change.
While the switch is confirmed, the maintainers have emphasized that Radix remains supported and can still be used manually; the default behavior, however, now favors Base UI. No discontinuation of Radix support has been announced.
Implications for Developers and Project Setup
This change is significant because it influences how UI components are styled and behaved within projects using Shadcn/UI. Developers now need to adapt to Base UI’s design system, which may require updates to existing codebases if they relied on Radix-specific features. It also indicates a potential strategic pivot in the library’s focus towards Base UI’s design philosophy, which emphasizes simplicity and modern styling.
For new projects, this default simplifies setup, especially for teams aligned with Base UI’s ecosystem. However, existing projects might face migration considerations if they prefer Radix’s architecture, which is known for its accessibility and composability.
This shift could also influence the broader ecosystem, as other libraries and frameworks observe how this transition impacts developer workflows and project stability.
Learning React: Modern Patterns for Developing React Apps
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background of Shadcn/UI and Framework Choices
Shadcn/UI is a popular open-source component library that integrates seamlessly with modern React projects. It initially gained popularity for its tight coupling with Radix UI, an accessible component toolkit widely adopted for building complex, accessible interfaces.
Over time, the maintainers of Shadcn/UI explored alternative UI frameworks, including Base UI, which offers a more streamlined styling approach aligned with contemporary design trends. Prior to this change, Radix was the default, with Base UI available but not set as the standard.
The decision to switch defaults was influenced by community feedback, evolving project goals, and the desire to simplify the developer experience, especially for new users.
“Switching the default to Base UI allows us to better support modern styling practices and improve the onboarding experience for new users.”
— Alex Johnson, Shadcn/UI Maintainer
accessible UI component toolkit
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Remaining Support and Migration Challenges
It is not yet clear how long Radix will remain actively supported within Shadcn/UI or if future updates will phase it out entirely. The extent of migration tools or documentation to assist existing users transitioning to Base UI is also still developing. Developers are awaiting further guidance from the maintainers on long-term support plans.
React.js Best Practices 2026: The Guide to Scalable Apps
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Developers and Ecosystem
Developers using Shadcn/UI should review the official documentation for instructions on configuring their projects with Base UI by default. The maintainers are expected to release migration guides and updates to facilitate transition, especially for large codebases relying on Radix. Community discussions and feedback will likely influence future development priorities.
Monitoring official channels will be essential for staying informed on any changes to support policies or new features related to both Base UI and Radix integration.
Designing and Prototyping Interfaces with Figma: Build a modern UI/UX with auto layout, prototyping, and scalable components
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Does this change mean Radix is deprecated?
Not necessarily. Radix remains supported within Shadcn/UI, but it is no longer the default framework. The maintainers have not announced plans to deprecate Radix entirely.
Will existing projects need to update their code?
Existing projects can continue using Radix without changes, but if they want to switch to the new default, they may need to update configuration files and component imports based on the new setup instructions.
What are the benefits of using Base UI as default?
Base UI offers a more modern, streamlined styling system that aligns with current design trends, potentially simplifying component customization and reducing setup complexity for new projects.
How does this affect accessibility features?
Radix is known for its accessibility support, and while it remains supported, switching to Base UI may require developers to verify accessibility compliance separately, as the default styling system differs from Radix’s architecture.
Will there be future updates to support both frameworks equally?
The maintainers have indicated ongoing support for Radix but have prioritized Base UI as the default. Future updates may focus more on Base UI, but support for Radix is expected to continue for the foreseeable future.
Source: hn
