Rad UI vs React Aria
React Aria, from Adobe, is two layers: low-level hooks (react-aria) and unstyled components (react-aria-components). It powers Adobe’s React Spectrum and is known for unusually thorough accessibility, internationalisation and touch handling.
Rad UI aims for the same outcome, accessible components you style yourself, with a smaller API in the Radix style. React Aria goes further in some areas, especially dates, calendars, colour pickers, drag and drop, and locale-aware formatting.
Last checked 2026-11-18 against the sources at the end of this page.
At a glance
| Topic | Rad UI | React Aria |
|---|---|---|
| Package | @radui/ui | react-aria-components (and react-aria hooks) |
| Styling | Unstyled, with an optional theme and tokens | Unstyled; default class names, data-* states and render props |
| API shape | Compound parts, asChild, data-* state | Composed components with slots, render props, onPress-style events |
| Frameworks | React | React |
| Maintainer | Open-source community | Adobe |
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 | React Aria |
|---|---|---|
| Accordion / Disclosure | Yes | Yes |
| Alert Dialog | Yes | Dialog with role="alertdialog" |
| Avatar | Yes | No |
| Breadcrumbs | Yes | Yes |
| Calendar / Date Picker | No | Yes |
| Checkbox | Yes | Yes |
| Color picker | No | Yes |
| Combobox / Autocomplete | Yes | Yes |
| Context Menu | Yes | No(unverified) |
| Dialog / Modal | Yes | Yes |
| Drag and drop, drop zone | No | Yes |
| Dropdown Menu | Yes | Menu |
| File trigger | No | Yes |
| Form / Field | Yes | Yes |
| Hover Card | Yes | No |
| Link | Yes | Yes |
| Menubar | Yes | No |
| Meter | Yes | Yes |
| Navigation Menu | Yes | No |
| Number Field | Yes | Yes |
| Popover | Yes | Yes |
| Progress | Yes | ProgressBar |
| Radio Group | Yes | Yes |
| Scroll Area | Yes | No |
| Search Field | No | Yes |
| Select | Yes | Yes |
| Separator | Yes | Yes |
| Slider | Yes | Yes |
| Splitter | Yes | No |
| Steps | Yes | No |
| Switch | Yes | Yes |
| Table | Yes | Yes |
| Tabs | Yes | Yes |
| Tag Group | No | Yes |
| Text Field / Text Area | Yes | Yes |
| Toast | Yes | Unstable (UNSTABLE_Toast) |
| Toggle / Toggle Group | Yes | ToggleButton, ToggleButtonGroup |
| Toolbar | Yes | Yes |
| Tooltip | Yes | Yes |
| Tree | Yes | Yes |
React Aria rows come from the component files in the react-aria-components package source and its docs. Toast is exported with an UNSTABLE_ prefix in its docs. Rows marked "unverified" could not be confirmed from the public docs.
Accessibility
React Aria is tested across many screen readers and devices, normalises pointer, touch and keyboard input into press events, and ships localisation for many languages, including date and number formats.
Rad UI follows the WAI-ARIA patterns with keyboard support, focus management and right-to-left support through DirectionProvider. It does not ship React Aria’s depth of locale data or its date and colour widgets.
Styling model
React Aria Components render default class names (like .react-aria-Button) and data attributes (data-pressed, data-selected), and accept render props for state-based classes. Adobe publishes starter kits, including a Tailwind one.
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 react-aria-componentsReact Aria also publishes the lower-level react-aria hooks for building fully custom components.
We do not quote bundle sizes here: they depend on which components you import and on your bundler. Measure your own build.
API shape
A dialog in each. React Aria wires the trigger and dialog through DialogTrigger and uses a render function for close; Rad UI uses named parts.
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 { Button, Dialog, DialogTrigger, Heading, Modal } from "react-aria-components"
export function EditProfile() {
return (
<DialogTrigger>
<Button>Edit profile</Button>
<Modal>
<Dialog>
{({ close }) => (
<>
<Heading slot="title">Edit profile</Heading>
<Button onPress={close}>Done</Button>
</>
)}
</Dialog>
</Modal>
</DialogTrigger>
)
}Which one should you pick?
Pick React Aria when
- You need date pickers, calendars, colour pickers, drag and drop, or tag groups with full accessibility.
- You ship in many languages and want built-in locale-aware formatting and translations for component strings.
- You want hooks to build fully custom widgets with the same accessibility engine.
Pick Rad UI when
- You prefer the Radix-style compound API (Root, Trigger, Content with asChild) over slots and render props.
- You need components React Aria does not list, such as Avatar, Hover Card, Menubar, Navigation Menu, Scroll Area, Splitter or Steps.
- You want an optional theme and token system you can switch on.
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.