Base UI vs Radix Primitives
Compare unstyled React component foundations, installation, and adoption tradeoffs before choosing primitives for your design system.
Where we would start
Keep your existing primitives when they meet the task. For a new project, compare the exact components and APIs you need in Base UI and Radix Primitives. Both let you supply the visual design; the decision should reflect component coverage, integration effort, and the conventions your team will maintain.
| Consideration | Base UI | Radix Primitives |
|---|---|---|
| Visual styling | Unstyled; bring your own styling approach | Unstyled Primitives; separate from Radix Themes |
| Package | @base-ui/react | radix-ui is the recommended starting package |
| Component structure | Assemble component parts and style them for your product | Compose primitive parts, including asChild where supported |
| Adoption cost | Check component APIs, portals, and your current wrappers | Check component APIs, wrappers, and existing Radix dependencies |
| Before shipping | Test the actual composition, labels, keyboard flow, and focus | Test the actual composition, labels, keyboard flow, and focus |
Should I migrate an existing application?
Identify a concrete missing capability or maintenance problem first. Changing primitives can affect focus, portals, event handling, and wrapper APIs. A representative dialog or select is a better migration experiment than rewriting every control at once.
Does either require Tailwind?
No. Both provide unstyled building blocks. Choose a styling approach that fits your application and verify how states and component parts are exposed.
Does an accessible primitive make the whole page accessible?
The surrounding composition still matters. Verify names, errors, contrast, keyboard order, and focus restoration in your rendered interface. This comparison is based on upstream documentation, not a conformance audit.
Explore the resources
Sources and review
Prepared by UI Finds from upstream documentation. Sources checked October 1, 2026. Recommendations are editorial judgments; no hands-on benchmark is claimed.