Softwr

Web Development · head to head

shadcn/ui vs Preact

shadcn/ui logo

shadcn/ui

Web Development

Copy-paste React components you own, not a dependency

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: shadcn/ui no upgrade path: once copied, upstream fixes and improvements are yours to port by hand; 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: shadcn/ui covers Copy, not install, Preact covers 3kB runtime.

Where they differ

Only the attributes on which shadcn/ui and Preact actually diverge.

Attributes where shadcn/ui and Preact differ
Attributeshadcn/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 shadcn/ui

  • Copy, not install
  • Radix primitives
  • Tailwind styling
  • Themeable

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.

shadcn/ui

  • Projects already using Tailwind that need accessible components without a theming fightnot Preact
  • Design systems that will diverge from any library’s defaults anywaynot Preact
  • Teams who have been burned by breaking changes in component library upgradesnot Preact

Preact

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

Where each one falls short

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

shadcn/ui

  • No upgrade path: once copied, upstream fixes and improvements are yours to port by hand
  • Requires Tailwind and React, so it is not an option outside that stack
  • Component code lives in your repository, which grows it and puts maintenance on your team
  • Its popularity has made the default look recognisable, which undercuts the customisation argument

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

shadcn/ui

Free
  • shadcn/uiFree
    • Full functionality
    • Commercial use permitted
    • Community support

Preact

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

Which should you pick?

Choose shadcn/ui if

  • You need copy, not install.
  • You want to start without paying.
  • You also want radix primitives.
shadcn/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 shadcn/ui or Preact better?
Neither clearly leads. shadcn/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, shadcn/ui or Preact?
shadcn/ui starts at Free and Preact at Free.
Does shadcn/ui or Preact run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use shadcn/ui for free?
Both have a free tier, so you can try either at no cost before committing.
What is shadcn/ui best used for?
shadcn/ui is most often used for projects already using tailwind that need accessible components without a theming fight, design systems that will diverge from any library’s defaults anyway, teams who have been burned by breaking changes in component library upgrades. Of those, projects already using tailwind that need accessible components without a theming fight and design systems that will diverge from any library’s defaults anyway are not what Preact is typically brought in for.
What can shadcn/ui do that Preact cannot?
shadcn/ui covers Copy, not install, Radix primitives, Tailwind styling, Themeable. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

shadcn/ui: Is shadcn/ui free?

Yes, open source and free for commercial use.

Preact: Is Preact free?

Yes, open source under the MIT licence.

shadcn/ui: Why is it not an npm package?

So you own the code. Components are copied into your project, which makes customisation trivial — at the cost of receiving no automatic updates.

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.

shadcn/ui: Do I need Tailwind?

Yes. Components are styled with Tailwind utility classes and built on Radix primitives, so both are required.

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 shadcn/ui

More on Preact

Keep looking

Other head to heads