MiniDev UI vs Radix Themes: which should you use?
Facts checked October 15, 2026
@radix-ui/themes from npm, import its stylesheet, wrap the app in a Theme component and set accent color, gray color, radius and scaling with props. It is built with vanilla CSS and does not depend on Tailwind. MiniDev UI is a free, MIT, shadcn-compatible registry that copies source into your repo, built on Base UI, Tailwind CSS v4 and motion, with 548 items. Pick Radix Themes if you want a coherent, closed component system with strong color scales and no utility CSS. Pick MiniDev UI if you want Tailwind, editable source, and finished product screens, blocks and motion.At a glance
| Feature | MiniDev UI | Radix Themes |
|---|---|---|
| Price | Free, everything | Free |
| License | MIT | MIT |
| Scope | 548 items: 397 UI components, 108 motion components, 43 blocks and pages | 36 components plus 5 layout, 9 typography and 6 utility components in the docs sidebar (56 in all) |
| Install model | Source copied into your repo with npx shadcn@latest add @minidev/<name>, or npm minidev-ui-kit | npm package @radix-ui/themes; import @radix-ui/themes/styles.css and wrap the app in <Theme> |
| Styling | Tailwind CSS v4 utilities with semantic OKLCH tokens | Vanilla CSS under the hood with its own CSS variables and no built in styling system; the docs say Tailwind may not mix well with its closed component model |
| Theming | Semantic tokens plus materials (hairline, glass, metal, paper) and one light source for shadows | accentColor, grayColor, radius and scaling props on Theme, a ThemePanel for live preview, dark mode through appearances; colors powered by Radix Colors with almost 30 scales |
| Primitives | Base UI (@base-ui/react) | Radix Primitives are the unstyled sibling; the docs point to them for custom components, and Tab Nav is built on the Navigation Menu primitive |
| Customization | Edit the file in your repo | Components are described as relatively closed, customized through props and theme configuration; most accept className and style |
| Blocks and templates | 15 block types, 43 full page blocks and 8 landing page templates as live demos | Components, layout, typography and utilities, plus a playground on the site |
What each one is
Radix Themes is described by its makers at WorkOS as an open source component library optimized for fast development, easy maintenance and accessibility. It is pre-styled: you install @radix-ui/themes, import styles.css, wrap the root in Theme, and set accentColor, grayColor, radius and scaling as props. Under the hood it is built with vanilla CSS and exposes the same CSS variables that power its components, with colors from Radix Colors. The docs are candid that components are relatively closed and are meant to be customized within their props and theme configuration, and that Tailwind may not mix well with that model. MiniDev UI takes the opposite approach: 548 items that land as source in your repo, styled with Tailwind CSS v4 utilities and semantic OKLCH tokens, with behavior from Base UI and 108 motion components built on motion. Both are MIT.
Where each one is the better pick
- Pick Radix Themes for a closed, coherent system. If you want components that look right together without writing utility classes, and a theme you configure in one place with props, it is designed for exactly that.
- Pick Radix Themes for its color system. Almost 30 color scales from Radix Colors, each with light, dark and alpha variants, plus a custom palette tool.
- Pick Radix Themes if you do not use Tailwind. It needs no utility framework, and its layout components (Box, Flex, Grid, Container, Section) handle spacing and layout through props.
- Pick MiniDev UI if Tailwind is your styling language. Every component is utilities and tokens you can read and edit, which also fits projects already on shadcn/ui.
- Pick MiniDev UI for screens, blocks and motion. Billing, settings, sign in, analytics and admin pages, 15 block types, 8 templates and 108 motion components come with the registry; Radix Themes focuses on components, layout and typography.
Running both in one app is awkward. Radix Themes ships its own base styles and tokens, and its styling docs describe a conflict between Tailwind's button reset and Themes buttons, with workarounds. If you want Radix behavior with Tailwind styling, the usual pairing is Radix Primitives (or Base UI) under a Tailwind registry such as shadcn/ui or MiniDev UI, not Radix Themes.
Frequently asked questions
Is Radix Themes the same as Radix Primitives?
No. Radix Primitives are unstyled components. Radix Themes is a pre-styled library from the same team at WorkOS, configured through a Theme component; its docs point to Primitives when you need a custom component.
Does Radix Themes work with Tailwind CSS?
It can, with care. The styling docs say Tailwind is a different paradigm that may not mix well with a closed component system, and they describe a base style conflict with workarounds. MiniDev UI is built for Tailwind CSS v4.
Are both free?
Yes. Radix Themes is MIT licensed and free, and MiniDev UI is MIT with no paid tier.
Sources
- Radix Themes home
- Radix Themes getting started
- Radix Themes styling
- Radix Themes 3.0 announcement
- radix-ui/themes on GitHub
Radix Themes is a trademark of its owner. This page is our own summary, checked on October 15, 2026. Pricing and features change, so confirm on their site.