Softwr

Web Development · head to head

Radix UI vs Preact

Radix UI logo

Radix UI

Web Development

Unstyled, accessible React component primitives

From
Free
Rated
-
Full reviewWebsite
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Radix UI you write all the styling, so time to a finished interface is much longer than with a styled library; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Radix UI covers Unstyled primitives, Preact covers 3kB runtime.

Where they differ

Only the attributes on which Radix UI and Preact actually diverge.

Attributes where Radix UI and Preact differ
AttributeRadix UIPreact

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), platforms (Web), user rating (Not yet rated), category (Web Development).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Radix UI

  • Unstyled primitives
  • Accessibility built in
  • Composable API
  • Controlled or uncontrolled

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What people use each for

The jobs each tool is most often brought in to do.

Radix UI

  • Design systems that need correct accessibility without inherited visual opinionsnot Preact
  • Replacing hand-built dropdowns and dialogs that have accessibility bugsnot Preact
  • Teams with a designer whose output should not be constrained by a library’s themenot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Radix UI
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Radix UI
  • Applications targeting low-bandwidth or low-powered devicesnot Radix UI

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Radix UI

  • You write all the styling, so time to a finished interface is much longer than with a styled library
  • Composable part-based APIs are more verbose than a single component with props
  • Covers primitives rather than complex widgets, so data grids and date pickers come from elsewhere

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

Pricing, plan by plan

Radix UI

Free
  • Radix UIFree
    • Full functionality
    • Commercial use permitted
    • Community support

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose Radix UI if

  • You need unstyled primitives.
  • You want to start without paying.
  • You also want accessibility built in.
Radix UI review

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.
Preact review

Questions people ask

Is Radix UI or Preact better?
Neither clearly leads. Radix UI starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Radix UI or Preact?
Radix UI starts at Free and Preact at Free.
Does Radix UI or Preact run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Radix UI for free?
Both have a free tier, so you can try either at no cost before committing.
What is Radix UI best used for?
Radix UI is most often used for design systems that need correct accessibility without inherited visual opinions, replacing hand-built dropdowns and dialogs that have accessibility bugs, teams with a designer whose output should not be constrained by a library’s theme. Of those, design systems that need correct accessibility without inherited visual opinions and replacing hand-built dropdowns and dialogs that have accessibility bugs are not what Preact is typically brought in for.
What can Radix UI do that Preact cannot?
Radix UI covers Unstyled primitives, Accessibility built in, Composable API, Controlled or uncontrolled. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Radix UI: Is Radix UI free?

Yes, open source under the MIT licence.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Radix UI: Why use unstyled components?

Because accessibility is the hard part and visual design is the part teams want to own. Radix gives the first and stays out of the second.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

Radix UI: What is the relationship with shadcn/ui?

shadcn/ui is built on Radix primitives, adding Tailwind styling and copy-paste distribution on top.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

Share

Related pages

More on Radix UI

More on Preact

Keep looking

Other head to heads