WebberUI vs Aceternity UI vs Magic UI vs React Bits: animated React component libraries compared

Checked on 2026-10-14. The details below come from each project's homepage, install docs, licence page and the LICENSE file on GitHub. Component counts are quoted only where the site or README states them, and are labelled "site states"; we did not count them ourselves. Prices change, so none are listed here; each row links to the relevant pricing page instead. This comparison is written by the WebberUI team. We have kept to facts that can be checked; if anything is out of date, the vendor's own site is the authority.

Summary table

All four follow the copy-the-source model: after installing, the component lives in your own components/ folder and you can edit it directly. The differences are mainly licence terms, dependencies and what kind of content each catalogue focuses on.

Aceternity UI

• Site: ui.aceternity.com
• Install: component pages give a registry CLI command using a namespace such as @aceternity/background-beams, with a Manual tab for copying by hand. The homepage says blocks and full pages also install through the CLI, and mentions an MCP server for AI agents.
• Stack: the homepage says it is built with React, Tailwind CSS and Motion.
• Count: the homepage states 200+ production-ready components, blocks and templates, and labels the components section 116+ free.
• Licence: the /licence page describes the Aceternity License for Aceternity UI Pro items: unlimited end products for yourself or clients, modification allowed, no redistribution of source files, and no selling on marketplaces or building templates for sale. We could not find licence text for the free components on the site or in the pricing FAQ, so confirm with Aceternity before commercial use.
• Paid: the pricing page lists Free, annual, lifetime and team plans.

Good fit: pages built around hero sections and large visual effects, in a project that already uses Motion, with Pro available when you need full-page blocks.

Magic UI

• Site: magicui.design
• Install: initialize the project, then add components with namespace commands such as @magicui/globe (install docs). npm, yarn and bun work too.
• Stack: the homepage lists React, TypeScript, Tailwind CSS and Motion.
• Count: the homepage states 150+ free and open-source animated components and effects.
• Licence: the GitHub repository uses the MIT License.
• Paid: Magic UI Pro offers blocks and templates; the homepage states 50+.

Good fit: marketing-page micro-interactions under an MIT licence, or components you need to use and redistribute freely in a public repository.

React Bits

• Site: reactbits.dev
• Install: a registry CLI, for example the @react-bits/SplitText-TS-TW namespace form, where the suffix picks the variant: JS or TS, plain CSS or Tailwind (install docs). The README also mentions jsrepo, and you can copy code by hand from a component's Code tab.
• Stack: each component comes in four combinations of JS/TS and CSS/Tailwind. Dependencies vary by component; the repository's package.json includes GSAP, Motion, three.js, OGL, matter-js and more, so check the dependencies listed on each component page before installing.
• Count: the README states 200+. On the day we checked, GitHub showed about 49.1k stars.
• Licence: MIT + Commons Clause. You can use it for any commercial purpose as part of an application, website or product, but you may not sell, sublicense or redistribute the components themselves, alone, in a bundle or as a ported version.
• Paid: React Bits Pro is a separate paid product with components, page blocks, app UI blocks and templates.

Good fit: creative effects (backgrounds, text, 3D, physics), or projects that do not use TypeScript or Tailwind and need plain JS or plain CSS versions.

WebberUI

The numbers below come from the same source as our llms.txt index: items marked available in lib/roadmap-data.json and lib/templates-data.json.

• Install: install with npx webberui@latest add <name>; free components can also be added with npx webberui@latest add https://webberui.com/r/<name>.en.json. The @webberui/mcp package lets AI agents search and install components. See the quick start.
• Stack: React and Tailwind CSS v4. Components are built on motion/react, and the CLI adds motion during install, along with clsx and tailwind-merge for the cn() helper.
• Count: 533 components, 399 of them free, and 104 full-page templates, all Pro.
• Licence: the WebberUI License Agreement. The code is source-available, not open source. Commercial use, modification and client work are allowed, and delivering a finished site to a client is not redistribution. Publishing the component source, including in a public GitHub repository, is not allowed. Free and Pro components carry the same usage rights, and attribution is not required. Installed components never contact our servers and have no remote-disable mechanism.
• Languages: documentation and component demos exist in both English and Traditional Chinese; English registry files are named <name>.en.json.
• Localisation components: the CJK localisation category has 26 components, such as the Taiwan business tax ID input (which implements the check-digit rule in force since 2023), the Taiwan national ID input, the ROC calendar date picker, the Taiwan address picker and Zhuyin ruby text.
• Paid: plans for Pro components and templates are on /pricing.

Good fit: websites and client projects for the Taiwan or wider Chinese-speaking market that need Traditional Chinese UI, local form validation and full-page templates, or teams that already use Motion and want components written the same way as their own code.

When WebberUI isn't the right pick

• You need MIT or another open source licence. WebberUI is not open source; you cannot publish its component source in a public repository or redistribute it as a package. For open source projects, public portfolios or tutorial repositories, Magic UI's MIT licence is the better fit.
• You only need one specific effect. If the effect you want is a popular one that lives in the React Bits or Aceternity UI catalogue, use that library directly rather than adopting a whole new one for a single component.
• Your project does not use Tailwind CSS or TypeScript. WebberUI components are written in TypeScript with Tailwind v4, with no plain CSS or JS variants. React Bits offers those.
• Your project is built around GSAP or three.js. WebberUI is built on Motion, and two animation engines driving the same element overwrite each other. Some React Bits components are implemented with GSAP, three.js or OGL.
• You are still on Tailwind CSS v3. WebberUI components and theme variables target v4.

Licence models side by side

The four libraries use three different licence models, and this is usually the first thing to confirm:

• MIT (Magic UI): the fewest restrictions, redistribution allowed.
• MIT + Commons Clause (React Bits): commercial use allowed, but not selling or redistributing the components themselves.
• Proprietary licences (Aceternity UI Pro, WebberUI): use in end products and client work, no distribution of the source. WebberUI's free components are covered by the same agreement.

If your company runs an open source licence review, the last two categories usually need a separate legal check.

Choosing

• MIT, with the option to publish source: Magic UI.
• Creative effects, or JS and plain CSS variants: React Bits.
• Hero sections and large visual effects: Aceternity UI.
• Traditional Chinese docs, Taiwan-specific forms, full-page templates, on Motion and Tailwind v4: WebberUI.

Using more than one is workable, since all four copy source into your project. Watch for files with the same name in components/ui/, and for which licence applies to each component. For the animation engines underneath, see choosing a React animation library in 2026.