Rad UI vs Ark UI
Ark UI comes from the Chakra UI team. It is headless and built on Zag.js state machines, which lets the same component logic run in React, Solid, Vue and Svelte.
Rad UI is React-only and uses a Radix-style API. Ark UI’s list is broad, with widgets like date pickers, colour pickers, file upload, signature pad and QR code that Rad UI does not have.
Last checked 2026-11-18 against the sources at the end of this page.
At a glance
| Topic | Rad UI | Ark UI |
|---|---|---|
| Package | @radui/ui | @ark-ui/react (plus Solid, Vue and Svelte packages) |
| Styling | Unstyled, with an optional theme and tokens | Unstyled; data-scope / data-part / data-state attributes; pairs with Panda CSS (Park UI) |
| API shape | Compound parts, asChild, data-* state | Compound parts (Root, Trigger, Content, Positioner), asChild |
| Frameworks | React | React, Solid, Vue, Svelte |
| Engine | React state and hooks | Zag.js finite state machines |
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 | Ark UI |
|---|---|---|
| Accordion | Yes | Yes |
| Alert Dialog | Yes | Dialog with role="alertdialog" |
| Avatar | Yes | Yes |
| Carousel | No | Yes |
| Checkbox | Yes | Yes |
| Collapsible | Yes | Yes |
| Color Picker | No | Yes |
| Combobox | Yes | Yes |
| Context Menu | Yes | Menu with a context trigger(unverified) |
| Date Picker | No | Yes |
| Dialog | Yes | Yes |
| Drawer | Yes | Preview |
| Dropdown Menu | Yes | Menu |
| Field / Fieldset | Yes | Yes |
| File Upload | No | Yes |
| Hover Card | Yes | Yes |
| Menubar | Yes | No |
| Meter | Yes | No |
| Navigation Menu | Yes | Yes |
| Number Field | Yes | Number Input |
| One-time password field | Yes | Pin Input |
| Pagination | No | Yes |
| Popover | Yes | Yes |
| Progress | Yes | Linear and circular |
| Radio Group | Yes | Yes |
| Rating | No | Yes |
| Scroll Area | Yes | Yes |
| Select | Yes | Yes |
| Slider | Yes | Yes |
| Splitter | Yes | Preview |
| Steps | Yes | Yes |
| Switch | Yes | Yes |
| Table | Yes | No |
| Tabs | Yes | Yes |
| Tags Input | No | Yes |
| Toast | Yes | Yes |
| Toggle / Toggle Group | Yes | Yes |
| Toolbar | Yes | No |
| Tooltip | Yes | Yes |
| Tree | Yes | Tree View |
Ark rows come from the Ark UI docs sidebar (Components and Utilities). Ark also lists Angle Slider, Clipboard, Editable, Floating Panel, Image Cropper, Marquee, Password Input, QR Code, Segment Group, Signature Pad, Timer, Table of Contents and Tour, none of which Rad UI has.
Accessibility
Both implement WAI-ARIA patterns with keyboard and focus handling. Ark’s state machines make behaviour the same across frameworks and easy to test.
Some Ark components are labelled Preview in its docs (for example Drawer, Splitter, Image Cropper); check a component’s status before relying on it.
Styling model
Ark components are unstyled and mark every part with data-scope and data-part attributes, plus state attributes. The Chakra team’s Park UI offers styled versions on Panda CSS or Tailwind.
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 @ark-ui/reactArk publishes one package per framework. Components can be imported from subpaths, like @ark-ui/react/dialog.
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. The shapes are close; Ark adds a Positioner part and uses CloseTrigger.
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 "@ark-ui/react/dialog"
import { Portal } from "@ark-ui/react/portal"
export function EditProfile() {
return (
<Dialog.Root>
<Dialog.Trigger>Edit profile</Dialog.Trigger>
<Portal>
<Dialog.Backdrop />
<Dialog.Positioner>
<Dialog.Content>
<Dialog.Title>Edit profile</Dialog.Title>
<Dialog.CloseTrigger>Done</Dialog.CloseTrigger>
</Dialog.Content>
</Dialog.Positioner>
</Portal>
</Dialog.Root>
)
}Which one should you pick?
Pick Ark UI when
- Your team ships in more than one framework and wants one component model across them.
- You need date pickers, colour pickers, file upload, tags input, rating, signature pad, carousel or a guided tour.
- You already use Chakra UI or Panda CSS.
Pick Rad UI when
- You are React-only and prefer a Radix-style API without a state-machine layer.
- You need Alert Dialog, Context Menu as its own component, Menubar, Toolbar, Table or Meter.
- You want an optional theme and design tokens 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.