The short answer
If you want a foundation you own, start with shadcn/ui and add animated blocks from Aceternity UI or Magic UI. If you want a finished, art-directed look with Figma files and code under one roof, HorizonX is the subscription option. If your team standardises on one vendor's design language forever, Tailwind Plus or Untitled UI React are the one-time buys. Everything else on this list is a good answer to a narrower question: DaisyUI for class-only theming, HeroUI for a batteries-included app kit, Flowbite and Preline for marketing-site speed.
The rest of this post explains how we sorted them, what each one actually ships, and which one to pick for the kind of project you have this month.
How we compared them
Libraries get lumped together as "React + Tailwind" when they solve different problems. We scored each on six things you can check yourself before buying:
- Delivery model: copy-in source you own, an npm dependency, or downloadable templates.
- Scope: primitives (buttons, inputs), blocks (hero, pricing), full pages, or complete products.
- Design direction: neutral system you restyle, or an opinionated look you ship as-is.
- Design files: is there a matching Figma kit, and is it included or sold separately?
- License: open source, one-time commercial, or subscription; client-work rights.
- Motion: does it come with animation, or do you wire GSAP / Motion yourself?
The libraries
shadcn/ui
The default answer in 2026. Components are copied into your repo through a CLI, built on Radix primitives and Tailwind, styled with CSS variables, MIT licensed. You own the code, which is why AI builders (v0, Lovable, Bolt, Cursor) all speak it fluently. What it is not: a finished look. Every shadcn site looks like every other shadcn site until a designer touches it, which is the gap most of the rest of this list fills.
Pick it when you need a neutral, accessible base and have design taste in-house or in a template.
Tailwind Plus (formerly Tailwind UI)
The Tailwind team's own catalogue of components, page sections and templates, sold as a one-time purchase. Impeccable HTML and React examples, very conservative visual direction, no motion. It is the safest choice for content and marketing sites where "clean" is the brief.
Pick it when your product's aesthetic is "Stripe docs" and you want the reference implementation of Tailwind itself.
Aceternity UI
Copy-paste React components for animated marketing pages: spotlight cards, beams, text reveals, 3D tilts. Free core with a paid All-Access Pass for the full block and template library. It is the fastest way to make a landing page feel expensive, and the easiest way to over-decorate one. We compare it with HorizonX in detail in HorizonX vs Aceternity UI.
Pick it when the page is a launch or a portfolio and motion is the product.
Magic UI
The same category as Aceternity (animated, copy-paste, shadcn-compatible), with a stronger focus on SaaS marketing patterns and a free tier that covers a surprising amount. Often used alongside shadcn/ui rather than instead of it.
Pick it when you already run shadcn and want a few standout sections without a new dependency graph.
HeroUI (formerly NextUI)
A full npm component library on top of Tailwind and React Aria: modals, tables, autocomplete, date pickers. Opinionated but themeable, good accessibility story, active releases. It is the closest thing on this list to a traditional "app UI kit" you install rather than copy.
Pick it when you are building an application with many interactive controls and want them consistent on day one.
daisyUI
Class-only components (btn, card, modal) that work in any framework because there is no JavaScript. Dozens of themes, MIT license. Great for prototypes and internal tools; less great when a designer hands you a spec that does not match one of the themes.
Pick it when speed beats fidelity and you do not want React-specific components at all.
Flowbite
Tailwind components and blocks with React bindings, a Figma kit and a pro tier of pages and dashboards. The dashboard and admin templates are the strongest part.
Pick it when you need an admin panel fast and are fine with the Flowbite look.
Preline UI
A large open-source Tailwind component set from Htmlstream with framework wrappers and a Figma file. Very wide coverage of marketing patterns, straightforward styling.
Pick it when you want breadth of ready sections at zero cost and can live with a generic finish.
Untitled UI React
The React sibling of the best-known Figma UI kit, built on React 19, Tailwind 4, TypeScript and React Aria, sold as a one-time single-user license. Free open-source components to start, paid kit for the full library. The Figma kit is a separate purchase. Full breakdown in HorizonX vs Untitled UI and Untitled UI alternatives.
Pick it when you want the deepest primitive catalogue and lifetime ownership of one kit.
HorizonX
A different shape from all of the above: a subscription catalogue that mixes Figma UI kits, production-ready React / Next.js / Svelte + Tailwind components and pages, and interactive tools, with new drops every month and a commercial license on every paid plan. It is art-directed rather than neutral: pieces like Velto (Next.js 16 + React 19 + Tailwind v4 + GSAP, scroll-scrubbed and bidirectional) or Apex Roadster (Next.js + GSAP) are finished pages you adapt, not primitives you assemble. Browse the React templates collection to see the range, and the interactive tools for the export-to-HTML/Svelte/React pieces.
Pick it when design and code need to move together, the brief is "make it look like someone with taste built it", and you would rather subscribe to a growing library than buy static kits one at a time. Plans are on the pricing page.
Comparison table
| Library | Delivery | Scope | Look | Figma files | License | Motion |
|---|---|---|---|---|---|---|
| shadcn/ui | Copy-in via CLI | Primitives | Neutral | Community kits | MIT | None |
| Tailwind Plus | Download | Sections, templates | Neutral, conservative | Separate | One-time | None |
| Aceternity UI | Copy-paste | Animated blocks, templates | Opinionated | No | Free + paid pass | Built in |
| Magic UI | Copy-paste | Animated blocks | Opinionated | No | Free + paid | Built in |
| HeroUI | npm | App components | Themeable | Partial | MIT | Light |
| daisyUI | CSS classes | Primitives | Themed | Community | MIT | None |
| Flowbite | npm + download | Blocks, dashboards | Flowbite look | Yes (kit) | Free + pro | Light |
| Preline UI | npm + copy | Blocks | Generic | Yes | Free | Light |
| Untitled UI React | npm + copy | Primitives, blocks | Neutral | Separate purchase | One-time | None |
| HorizonX | Download per asset | Pages, kits, tools | Art-directed | Included | Subscription | Built in (GSAP, WebGL) |
Which one for which project
- A SaaS app with lots of forms and tables: shadcn/ui or HeroUI for the controls, then a HorizonX or Aceternity landing page in front of it.
- A launch page that has to feel premium this week: Aceternity, Magic UI, or a finished HorizonX landing like Veyra or Vantro.
- A client site with a Figma handoff: Untitled UI (Figma + React, bought separately) or HorizonX (both under the subscription). See Figma templates vs coded components for how to decide which format to start from.
- An internal dashboard: Flowbite Pro or the dashboard templates collection.
- Vibe coding with v0 / Lovable / Cursor: shadcn/ui as the base, plus a template as the visual constraint. The vibecoding guide explains why the constraint matters more than the prompt.
Workflow checklist: September 2026 update
The right React UI resource depends on what your team needs to decide next: application behaviour, a consistent visual system, a distinctive section or an editable effect. Comparing everything by component count obscures those differences. Start with one real screen and the responsibility you expect the resource to take off your hands.
This is a workflow-based shortlist, not a performance benchmark. HorizonX publishes this guide and is one of the products discussed. No installation-time, accessibility or conversion ranking is implied.
Separate a foundation from a visual layer
shadcn/ui distributes component source that teams can adapt. It is a starting point to inspect when owning and shaping the component code matters. Ownership also means deciding how your team will maintain its modifications.
Untitled UI presents Figma and React resources. Evaluate the relevant product when design-to-code consistency is central; do not assume every purchase or asset includes identical formats.
For visually expressive sections, inspect Aceternity UI and Magic UI. Their public catalogues give you examples to shortlist, but a polished demo is not proof that a particular component fits your application.
Distinguish discovery from integration
21st.dev is another place to discover components and templates. Finding the right visual is only one stage: the selected item still needs a check for dependencies, maintenance, content fit and usage terms.
HorizonX combines a visual library with interactive editors. It is relevant when you want to start from an art-directed asset or configure a visual before integrating it. Inspect the individual resource and current documentation rather than assuming universal framework support.
These options can coexist. A project can keep its application controls in one system and use a separate resource for a decorative section. The boundary should be explicit so that visual additions do not quietly replace established behaviour.
Compare one task, not two marketing pages
Choose a representative task such as an account settings panel or a product feature section. Write the required states, content lengths, target framework and mobile layout before evaluating candidates.
For each candidate, record what is provided, what you changed, what dependencies you added and what remains untested. Examine keyboard use, error and empty states, resizing and the no-animation presentation where relevant. Record actual observations instead of filling a scoring table from memory.
Pricing and licensing should be checked against the selected item and current vendor terms. A free preview does not establish a right to redistribute source files, and a paid resource does not remove integration work.
What should you choose first?
Choose the foundation that fits the application's behaviour, then add the smallest visual layer that serves the content. Use the production-readiness checklist as a review aid, not as a certification that an untested library has passed.
FAQ
Is shadcn/ui a component library?
Technically no, and its author says so: it is a collection of components you copy into your project and own. That is exactly why it works so well as a base under other libraries, and why it never gives you a finished look by itself.
Do I need a paid library at all?
For an internal tool or an MVP, no. shadcn/ui, daisyUI and Preline will get you shipped. Paid libraries earn their price when the interface is customer-facing and brand-sensitive, because the expensive part is not the code, it is the art direction. The premium vs free ROI analysis puts numbers on that.
Which library is best for animated landing pages?
Aceternity UI and Magic UI if you are assembling blocks; HorizonX if you want complete pages with GSAP or WebGL motion already choreographed, such as Immersive Robotics or Pulso.
Can I use these in client work?
Open-source ones (shadcn/ui, daisyUI, HeroUI, Preline) yes, with attribution rules per license. Tailwind Plus and Untitled UI sell per-seat commercial licenses. HorizonX includes a commercial license for client work with every paid plan.
What about Svelte or Vue?
daisyUI and Preline are framework-agnostic. shadcn has community ports (shadcn-svelte, shadcn-vue). HorizonX ships Svelte pieces alongside React ones, for example Velmont (SvelteKit 5 + Tailwind 4 + GSAP), and its tools export to HTML, Svelte or React.