All comparisons

Rad UI vs shadcn/ui

shadcn/ui describes itself as “not a component library” but “how you build your component library”. A CLI copies styled component source into your project, and you own and edit that code. Most of its interactive components are built on Radix primitives by default, styled with Tailwind.

So the fair comparison is two layers: shadcn/ui is the styled layer you copy, Rad UI is the behaviour layer you install (with an optional theme). You can build the shadcn/ui way on Rad UI: write your own styled wrappers over Rad UI parts and keep them in your repo.

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

At a glance

TopicRad UIshadcn/ui
What you getAn npm dependency with unstyled parts and an optional themeSource files in your repo, styled with Tailwind
UpdatesUpgrade the packageRe-run the CLI or merge upstream changes by hand
StylingUnstyled, theme, or tokensTailwind classes in the copied files, CSS variable themes
Behaviour layerRad UI itselfRadix primitives by default, plus a few other packages
FrameworksReactReact

Component coverage

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

ComponentRad UIshadcn/ui
AccordionYesYes
Alert DialogYesYes
AvatarYesYes
BadgeYesYes
BreadcrumbYesYes
Calendar / Date PickerNoYes
CardYesYes
CarouselNoYes
ChartNoYes
CheckboxYesYes
CollapsibleYesYes
ComboboxYesYes
Command palettePreviewYes
Context MenuYesYes
DialogYesYes
Drawer / SheetYesYes
Dropdown MenuYesYes
Field / FormYesYes
Hover CardYesYes
KbdYesYes
MenubarYesYes
MeterYesNo
Navigation MenuYesYes
Number FieldYesNo
One-time password fieldYesInput OTP
PaginationNoYes
PopoverYesYes
ProgressYesYes
Radio GroupYesYes
Scroll AreaYesYes
SelectYesYes
SidebarNoYes
Skeleton / SpinnerYesYes
SliderYesYes
SplitterYesResizable
StepsYesNo
SwitchYesYes
TableYesTable, Data Table
TabsYesYes
ToastYesYes
Toggle / Toggle GroupYesYes
ToolbarYesNo
TooltipYesYes
TreeYesNo

shadcn/ui rows come from its components page. It lists more items, including layout and AI-chat pieces; this table keeps the rows both sides could reasonably have.

Accessibility

shadcn/ui inherits keyboard and ARIA behaviour from the primitives under it, so its interactive components are as accessible as Radix makes them, as long as edits to the copied code keep that wiring intact.

Rad UI keeps behaviour inside the package, so your styling changes cannot break it, and fixes arrive with an upgrade instead of a manual merge.

Styling model

shadcn/ui components are Tailwind classes in your own files, themed through CSS variables like --primary and --background. Community tools such as tweakcn generate those variables.

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
shadcn/ui
npx shadcn@latest add dialog

shadcn/ui’s CLI writes components into your project (by default under components/ui) and installs the primitives they depend on.

Rad UI installs like any package; there is nothing to copy unless you choose to write wrappers.

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. shadcn/ui wraps Radix parts in styled, flat-named exports that live in your repo.

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>
  )
}
shadcn/ui
// After: npx shadcn@latest add dialog button
import { Button } from "@/components/ui/button"
import {
  Dialog,
  DialogClose,
  DialogContent,
  DialogHeader,
  DialogTitle,
  DialogTrigger,
} from "@/components/ui/dialog"

export function EditProfile() {
  return (
    <Dialog>
      <DialogTrigger asChild>
        <Button>Edit profile</Button>
      </DialogTrigger>
      <DialogContent>
        <DialogHeader>
          <DialogTitle>Edit profile</DialogTitle>
        </DialogHeader>
        <DialogClose asChild>
          <Button>Done</Button>
        </DialogClose>
      </DialogContent>
    </Dialog>
  )
}

Which one should you pick?

Pick shadcn/ui when

  • You want a good-looking Tailwind UI today and are happy to own and maintain the component code.
  • You want the huge ecosystem around it: blocks, charts, a sidebar, registries and many community themes.
  • Your team edits component internals often and prefers source in the repo to a dependency.

Pick Rad UI when

  • You want accessible behaviour as a dependency you upgrade, not code you merge by hand.
  • You want to design your own look from unstyled parts, or start from a theme and retheme it with tokens.
  • You need components shadcn/ui does not include, such as Number Field, Tree, Toolbar, Steps or Meter.

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.