Rad UI vs Radix UI
Radix Primitives is the library most React developers think of for unstyled, accessible components, and the base layer of shadcn/ui. Rad UI follows the same idea, with a very similar API: compound parts (Root, Trigger, Content), asChild for composition, and state exposed as data-* attributes.
If you know Radix, you already know most of Rad UI. The differences are in what ships around the primitives: an optional theme with design tokens, a Tailwind v4 preset, and more components, such as NumberField, Tree, Table, Steps and Splitter.
Last checked 2026-11-18 against the sources at the end of this page.
At a glance
| Topic | Rad UI | Radix UI |
|---|---|---|
| Package | @radui/ui (one package, per-component entry points) | radix-ui (one package), or @radix-ui/react-* per primitive |
| Styling | Unstyled, with an optional theme and tokens | Unstyled |
| API shape | Compound parts, asChild, data-* state | Compound parts, asChild, data-* state |
| Frameworks | React | React |
| Maturity | Younger, smaller community | Widely used since 2020, large ecosystem |
Component coverage
Built from each library’s public component list. “Yes” means a dedicated, documented component; a name means the closest equivalent.
| Component | Rad UI | Radix UI |
|---|---|---|
| Accordion | Yes | Yes |
| Alert Dialog | Yes | Yes |
| Aspect Ratio | Yes | Yes |
| Avatar | Yes | Yes |
| Checkbox | Yes | Yes |
| Collapsible | Yes | Yes |
| Combobox / Autocomplete | Yes | No |
| Command palette | Preview | No |
| Context Menu | Yes | Yes |
| Dialog | Yes | Yes |
| Drawer | Yes | No |
| Dropdown Menu | Yes | Yes |
| Form / Field | Yes | Form |
| Hover Card | Yes | Yes |
| Menubar | Yes | Yes |
| Meter | Yes | No |
| Navigation Menu | Yes | Yes |
| Number Field | Yes | No |
| One-time password field | Yes | Preview(unverified) |
| Popover | Yes | Yes |
| Progress | Yes | Yes |
| Radio Group | Yes | Yes |
| Scroll Area | Yes | Yes |
| Select | Yes | Yes |
| Separator | Yes | Yes |
| Slider | Yes | Yes |
| Splitter | Yes | No |
| Steps | Yes | No |
| Switch | Yes | Yes |
| Table | Yes | No |
| Tabs | Yes | Yes |
| Toast | Yes | Yes |
| Toggle / Toggle Group | Yes | Yes |
| Toolbar | Yes | Yes |
| Tooltip | Yes | Yes |
| Tree | Yes | No |
| Password toggle field | No | Preview(unverified) |
| Visually Hidden, Slot, Direction | Yes | Yes |
Radix rows come from the package list in the radix-ui/primitives repository and the Radix docs. "Preview" marks One-Time Password Field and Password Toggle Field, which shipped as preview primitives; we could not confirm their current label from the docs pages, so check before relying on them.
Accessibility
Both follow the WAI-ARIA Authoring Practices: roles and states, roving focus in composite widgets, focus trapping in modals, and focus return on close.
Radix documents a keyboard interaction table per component. Rad UI component pages document their keyboard map and the ARIA pattern they follow.
Neither library can make your colour choices accessible. Rad UI’s theme checks text contrast in its own palette, and the theme generator checks yours.
Styling model
Radix ships no styles. You target data-state, data-side and similar attributes with any CSS approach.
Rad UI ships unstyled behaviour with stable data-* attributes for every state. Styling is opt-in: import @radui/ui/themes/default.css and wrap the app in <Theme classNamespace="rad-ui"> for the Clarity theme, retheme it through --rad-ui-* tokens (see the theme generator), or skip the theme and style the parts with your own CSS or Tailwind.
Want to see the Rad UI theme in your brand colours? Try the theme generator.
Install and bundle model
pnpm add @radui/uinpm install radix-uiRadix recommends the single tree-shakable radix-ui package and still publishes each primitive as @radix-ui/react-<name>. Its docs advise keeping those versions in step to avoid duplicate shared dependencies.
Rad UI is one package with an entry point per component (@radui/ui/Dialog), so you import only what you use.
We do not quote bundle sizes here: they depend on which components you import and on your bundler. Measure your own build.
API shape
The same dialog in both. The structure is nearly identical, which makes moving between them a mostly mechanical change of imports.
import Button from "@radui/ui/Button"
import Dialog from "@radui/ui/Dialog"
export function EditProfile() {
return (
<Dialog.Root>
<Dialog.Trigger asChild>
<Button>Edit profile</Button>
</Dialog.Trigger>
<Dialog.Portal>
<Dialog.Overlay />
<Dialog.Content>
<Dialog.Title>Edit profile</Dialog.Title>
<Dialog.Close asChild>
<Button>Done</Button>
</Dialog.Close>
</Dialog.Content>
</Dialog.Portal>
</Dialog.Root>
)
}import { Dialog } from "radix-ui"
export function EditProfile() {
return (
<Dialog.Root>
<Dialog.Trigger asChild>
<button>Edit profile</button>
</Dialog.Trigger>
<Dialog.Portal>
<Dialog.Overlay />
<Dialog.Content>
<Dialog.Title>Edit profile</Dialog.Title>
<Dialog.Close asChild>
<button>Done</button>
</Dialog.Close>
</Dialog.Content>
</Dialog.Portal>
</Dialog.Root>
)
}Which one should you pick?
Pick Radix UI when
- You want the most battle-tested option with the largest community, the most answers online and the most third-party examples.
- You use shadcn/ui or another kit built on Radix and want to stay on one primitive layer.
- You only need the components Radix already has and want nothing else in the package.
Pick Rad UI when
- You want the Radix-style API plus components Radix does not ship, like NumberField, Tree, Table, Steps, Splitter, Meter or Combobox.
- You want an optional, token-driven theme you can turn on, retheme or drop, instead of styling everything from zero.
- You want to influence a younger library directly: issues and PRs on Rad UI get read by the people who write it.
Ready to try Rad UI? Start with the installation guide or open the playground.
Sources
Libraries change. If something here is out of date, open an issue.