- Design systems that need full styling control
- Accessibility-sensitive interactions such as menus, dialogs, and selects
- Teams with design bandwidth to compose their own UI layer
Headless UI
review file
Behaviour without opinion.
Headless UI is strongest when unstyled primitives is the right foundation and the team values accessibility and composition control over a generic UI grab bag.
- You need finished components instead of primitives
- Your team does not have time to design and style interactions
Decision dossier
FULL FILEAccessible component logic with zero styling. Pairs naturally with Tailwind, but works with anything that ships CSS.
Editorial note: outbound links may become affiliate or referral links. Rankings stay based on product fit, not commissions.
- Author
- Tailwind Labs
- Released
- 2020
- Pricing model
- Open-source primitives; design layer is built by your team
- Frameworks
- React / Vue
- Tags
- headless / unstyled primitives / mit
- Repository
- 25.2k stars
- Freshness
- Tracked from tailwindlabs/headlessui and @headlessui/react
- Sponsorship
- Sponsor this category
Weekly source checks
We keep automated signals separate from human-written verdicts. GitHub, npm, homepage, and docs checks can flag stale facts without rewriting this review.
Commercial disclosure
Sponsored placements are labeled. Editorial ranking is not for sale.
View sponsorship options →Can teams ship responsibly?
Strong choice when accessibility behavior matters, because primitives focus on keyboard navigation, focus management, and ARIA patterns.
Can it become your brand?
Maximum styling freedom, but the team owns the design language and implementation consistency.
Radix Primitives
Unstyled, accessible building blocks.
View full review →Ark UI
One API across React, Vue, Solid.
View full review →