Headless React components
A headless component owns behaviour, accessibility and state and renders no visual design. You get keyboard interaction, focus management, ARIA semantics and controlled/uncontrolled state without building them, and you keep every pixel.
Rad UI is a headless library with an optional theme: accessible React components with TypeScript types, composition through parts and asChild, stable data-* styling hooks, and Clarity when you want a finished look.
When headless components help
Use headless components when:
- your product has an existing brand or design system
- you need accessible interactions but want to own the CSS
- you want predictable React APIs across forms, overlays, menus, navigation, and feedback components
- you need to compose primitives into app-specific UI without fighting a preset visual language
For a fully custom design system, start with per-component imports and style the exposed parts directly:
When a styled UI kit is better
A styled kit can be faster when your app can adopt its visual language as-is. If the design system is not a product requirement, a fully styled library may reduce decisions and ship screens sooner.
Choose Rad UI when the component behavior matters but the final look belongs to your team.
Rad UI's approach
Rad UI components are designed around:
- Behavior first: components own interaction and accessibility contracts.
- Design-system control: consumers own layout, recipes, and brand expression.
- Per-component imports: import only the components you use.
- Optional theme CSS: use the default theme for a ready baseline, or stay headless.
- Stable styling hooks: use documented parts, CSS variables, and data attributes.
Styling options
You can use Rad UI in three common ways:
- Headless: import components and bring your own CSS.
- Themed: import
@radui/ui/themes/default.cssand wrap UI inTheme. - Design-system integrated: map Rad UI parts and state attributes to your tokens and component recipes.