Unstyled UI components for building accessible web apps and design systems. From the creators of Radix, Floating UI, and Material UI.
10.3k
Stars
482
Forks
394
Open issues
30
Contributors
AI Analysis
Base UI is an unstyled component library for building accessible React interfaces, created by the team behind Radix, Floating UI, and Material UI. It serves developers and design system teams who need accessible, composable components without opinionated styling, allowing complete design control. It's best suited for organizations building custom design systems or applications with specific visual requirements, not for teams seeking pre-styled components out-of-the-box.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Base UI: Unstyled accessible React components from the teams behind Radix, Floating UI, and Material UI
Base UI provides a set of unstyled, accessible React UI primitives aimed at developers who need full styling freedom while relying on battle-tested accessibility and behavior logic. It targets teams building custom design systems or web apps who find opinionated component libraries too restrictive but still want production-ready keyboard navigation, ARIA handling, and interaction semantics. The project is backed by the team that built Radix UI primitives and Material UI, giving it strong credibility in the accessibility-first component space.
Base UI was formally created as a public GitHub repository in February 2024, though it evolved from MUI's earlier 'Base UI' package within the MUI monorepo (formerly @mui/base). The current repo represents a re-launch with Colm Tuite (Radix co-creator) and other recognized contributors joining forces under the MUI organization.
The repo accumulated ~10K stars in roughly 28 months, a moderate but steady pace. Initial momentum was likely driven by the credibility of the team — combining Radix, Floating UI, and Material UI pedigrees attracted developer attention quickly. Growth appears organic, with sustained weekly activity (66 stars in the last 7 days as of late June 2026) suggesting ongoing community interest rather than a viral spike.
Adoption not verified from the README alone. The project's association with MUI (widely used in production) and the Radix ecosystem lends indirect credibility, but direct evidence of large-scale production deployments by third parties is not documented in available metadata. Early adopters likely include design-system-focused engineering teams already in the MUI or Radix orbit.
Likely follows a headless/renderless component pattern similar to Radix UI primitives — components expose behavior and accessibility hooks without coupling to visual styles. Appears to be TypeScript-first based on repo language tagging. The team composition (Floating UI maintainer included) suggests floating/overlay components likely use Floating UI internally.
Not documented in README
Last push was June 27, 2026 — two days before the evaluation date — indicating very active, ongoing development. The presence of a dedicated documentation site, Discord, and social media accounts signals an organized, well-resourced project rather than a side effort. Commit cadence and recency strongly suggest active maintenance.
ADOPT IF: you are building a custom design system in React and need accessible, behavior-correct primitives without style lock-in, and you value the team's track record with Radix and Floating UI. AVOID IF: you need a stable, production-hardened API today — the project is still pre-1.0 in practical terms and APIs may shift; or if your team wants a full styled component library out of the box. MONITOR IF: you are evaluating unstyled primitive libraries for a future design system project and want to see whether Base UI differentiates sufficiently from Radix Primitives in scope and stability before committing.
Independent dimensions
Mainstream potential
6/10
Technical importance
8/10
Adoption evidence
3/10
- Direct competition from Radix UI primitives, which has a multi-year head start, deep ecosystem integration (shadcn/ui, etc.), and comparable team credibility — differentiation may prove difficult to communicate.
- API stability risk: the project appears still in active design flux as of mid-2026; teams adopting early may face breaking changes.
- The team spans Radix and MUI codebases, raising a question of long-term resource focus — though no concrete evidence of neglect exists currently.
- Community fragmentation risk: developers already invested in Radix primitives have little incentive to switch, potentially limiting Base UI's addressable market to greenfield projects.
- Sparse README and lack of documented production case studies make independent adoption verification difficult, creating uncertainty about real-world battle-testing.
Base UI is likely to grow steadily into a credible alternative to Radix Primitives, particularly if it delivers tighter Floating UI integration and broader component coverage. Mainstream dominance is unlikely given Radix's entrenchment, but it may carve out a solid niche among MUI-ecosystem teams.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://base-ui.com
- Language
- TypeScript
- License
- MIT
- Last updated
- 6h ago
- Created
- 29mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[checkbox group] Invalid form submission focuses the first checkbox instead of the checkbox that failed validation
[dialog] Rationale for `aria-expanded` on `Dialog.Trigger` (modal dialogs)
[popover] Positioner slides from viewport top-left on first open in React 17
[select] popup is not removed from the DOM after closing.
"llms.txt" search result navigates to a 404
Open pull requests
Top contributors
Recent releases
Similar repos
radix-ui/primitives
Radix Primitives is an open-source, low-level UI component library focused on...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
mui/base-ui
this
|
10.3k | +192 | TypeScript | 8/10 | 6h ago |
 uber/baseweb
|
9k | — | TypeScript | 7/10 | 3d ago |
|
mui/material-ui
|
98.6k | — | JavaScript | 9/10 | 3h ago |
|
radix-ui/primitives
|
19k | — | TypeScript | 8/10 | 11h ago |
|
radix-ui/website
|
1k | — | TypeScript | 8/10 | 1w ago |
|
radix-ui/themes
|
8.5k | — | TypeScript | 8/10 | 3mo ago |
The most direct competitor. Radix Primitives is more mature (~19K stars, several years in production) and heavily adopted in the ecosystem (powering shadcn/ui). Base UI is built partly by the same people, positioning itself as an evolution — broader scope, stronger Floating UI integration — but Radix currently has a large head start in adoption.
shadcn/ui is not a direct competitor — it builds on top of Radix primitives and provides copy-pasteable styled components. Base UI could serve as an alternative foundation layer for shadcn-style distribution, but they occupy different layers of the stack.
Material UI is the MUI team's flagship opinionated component library (~98K stars). Base UI is the unstyled, behavior-only layer underneath, targeting users who explicitly don't want Material Design constraints. They serve different needs and are complementary rather than competitive.
Baseweb is Uber's design system built with styletron and tightly coupled to Uber's visual language. It's a full design system rather than an unstyled primitive layer, making Base UI's target audience almost entirely different.
Radix Themes adds a styled layer on top of Radix Primitives. It competes with styled solutions rather than with Base UI, which remains unstyled. Teams wanting plug-and-play visual components would choose Radix Themes; those wanting control would consider Base UI.