All comparisons

Rad UI vs Headless UI

Headless UI is made by Tailwind Labs, the team behind Tailwind CSS. It is a small, carefully designed set of unstyled components, built to be styled with Tailwind utility classes.

Rad UI is unstyled too and works well with Tailwind (it ships a Tailwind v4 preset), but it covers many more components: menus beyond dropdowns, toasts, tooltips, sliders, trees, tables and more.

Last checked 2026-11-18 against the sources at the end of this page.

At a glance

TopicRad UIHeadless UI
Package@radui/ui@headlessui/react (v2.1 at time of writing)
StylingUnstyled, with an optional theme and tokensUnstyled, made for Tailwind
API shapeCompound parts, asChild, data-* stateNamed components (Menu, MenuButton, MenuItems), render props and data-* state
FrameworksReactReact and Vue (separate packages)
Component count60+About 15 (see the table)

Component coverage

Built from each library’s public component list. “Yes” means a dedicated, documented component; a name means the closest equivalent.

ComponentRad UIHeadless UI
AccordionYesDisclosure
Alert DialogYesNo
AvatarYesNo
ButtonYesYes
CheckboxYesYes
Collapsible / DisclosureYesYes
ComboboxYesYes
Context MenuYesNo
DialogYesYes
DrawerYesNo
Dropdown MenuYesYes
Field / FieldsetYesYes
Hover CardYesNo
Input / TextareaYesYes
MenubarYesNo
Navigation MenuYesNo
Number FieldYesNo
PopoverYesYes
Progress / MeterYesNo
Radio GroupYesYes
Scroll AreaYesNo
Select (custom listbox)YesListbox
SliderYesNo
SwitchYesYes
TableYesNo
TabsYesYes
ToastYesNo
Toggle GroupYesNo
TooltipYesNo
Transition helperNoYes
TreeYesNo

Headless UI rows come from the component list in the Headless UI React docs sidebar (Components and Forms).

Accessibility

Both implement WAI-ARIA patterns with keyboard support and focus management, so you do not wire roles and key handlers yourself.

Headless UI covers fewer widgets, so you will build more of the remaining ones (tooltips, toasts, sliders) yourself or bring another library for them.

Styling model

Headless UI exposes state as data attributes (data-focus, data-open, data-active) and render props, and its docs style everything with Tailwind modifiers like data-focus:bg-blue-100.

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

Rad UI
pnpm add @radui/ui
Headless UI
npm install @headlessui/react

Both are single packages. Headless UI has a separate @headlessui/vue package for Vue.

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. Headless UI keeps the open state in your component; Rad UI can manage it for you or take it controlled.

Rad UI
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>
  )
}
Headless UI
import { useState } from "react"
import { Dialog, DialogPanel, DialogTitle } from "@headlessui/react"

export function EditProfile() {
  const [isOpen, setIsOpen] = useState(false)
  return (
    <>
      <button onClick={() => setIsOpen(true)}>Edit profile</button>
      <Dialog open={isOpen} onClose={() => setIsOpen(false)}>
        <DialogPanel>
          <DialogTitle>Edit profile</DialogTitle>
          <button onClick={() => setIsOpen(false)}>Done</button>
        </DialogPanel>
      </Dialog>
    </>
  )
}

Which one should you pick?

Pick Headless UI when

  • You live in Tailwind, need only the components it has, and want the smallest possible API from the Tailwind team.
  • You also build in Vue and want the same component model in both.
  • You use Tailwind Plus (formerly Tailwind UI) templates, which are built on Headless UI.

Pick Rad UI when

  • You need components Headless UI does not have: tooltips, toasts, sliders, accordions, context menus, menubars, trees, tables and more.
  • You want an optional theme and design tokens alongside unstyled parts.
  • You prefer one consistent compound-part API across every component.

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.