Introduction

Rad UI is a headless, accessible React component library for products that expect to live for years. It owns behaviour: roles, keyboard handling, focus, dismissal, positioning. You own the look: style every state through stable data-* attributes, use the included Clarity theme, or mix both.

It is infrastructure for a design system, not a starter kit.

What ships

  • 70+ components, each its own import (@radui/ui/Dialog), so a Dialog never pays for a Table.
  • Accessibility by default. Composite widgets follow WAI-ARIA patterns: one tab stop per group, arrow keys inside it, focus returned on close, live announcements where they belong.
  • A styling contract. Every state is a data-* attribute. Generated class names are opt-in through Theme classNamespace, so nothing leaks into a codebase that did not ask for it.
  • Clarity, an optional theme driven by tokens: appearance, accent, radius and scale, with Tailwind presets for the colour scales.
  • TypeScript end to end, server-rendering safe, React 18 and 19, Next.js, Remix and Vite.

Why Rad UI

Headless at the core

Components ship with no visual styling. They integrate with your tokens, spacing and typography instead of imposing their own, which is what a design system needs. When you want to move fast, turn on Clarity; when a component needs its own look, detach it from the theme and style it directly. Both paths use the same markup.

Accessibility without ceremony

Keyboard navigation, focus management and ARIA are built into each component and documented on its page: the keyboard map, the pattern it follows, the references. You get accessible behaviour on day one instead of accessibility debt later.

Composable primitives

Each component is a set of parts (Dialog.Root, Dialog.Trigger, Dialog.Content) with a small, predictable API. Compose them into your own components, swap the rendered element with asChild, and build new parts with Slot, mergeProps and composeRefs.

Adopt one component at a time

Rad UI does not ask for a rewrite. Bring it into an existing app next to what is already there, replace the hardest widgets first, and keep going at your own pace.

Who it is for

  • Design system builders who want solid primitives under their own language.
  • Product teams who need consistent interactions across a large app.
  • Solo developers who want polished, accessible UI without building it from scratch.

Start here

  1. Installation: install, pick a setup, render a component.
  2. Usage: Theme, class namespaces and the Tailwind preset.
  3. All components: what each one is for.
  4. Playground: every component with its variants, sizes and states side by side.