FINDING YOUR DIRECTION

0%
← Scrollhaus Journal

AI Website Templates · Published · Updated · 8 min read

Magic UI, Aceternity UI, React Bits and 21st.dev Compared: Which Animated Library for Which Job

Four names dominate animated React components in 2026: Magic UI, Aceternity UI, React Bits and 21st.dev. They all let you copy polished, motion-heavy code into a project, but they are built for different jobs. This guide compares them side by side, says what each does best, and explains where a component library stops and a complete animated page begins.

Published by Amanjot Singh, founder of Scrollhaus. AI-assisted editorial work; product context, sources and corrections are documented in our editorial methodology.

A gold figure climbing stone steps from the Cornerstone scroll website
Scrollhaus Journal · AI Website Templates

Disclosure: ScrollHaus, a library of complete animated websites, publishes this guide. Facts about each library come from its public pages and GitHub repository, read on October 5, 2026. Counts and prices change quickly, so check the live pages before you decide.

Quick answer: which animated component library should you use?

All four are component libraries. They solve "I need a good animated button, background or card". They do not solve "I need a whole landing page that already scrolls well". That second job is where full-page templates come in, and the last section covers when to use which.

Magic UI, Aceternity UI, React Bits and 21st.dev at a glance

Magic UIAceternity UIReact Bits21st.dev
What it isAnimated components for design engineersAnimated components, blocks and templatesOpen-source animated, interactive React componentsCommunity registry of components, templates and themes
Free set150+ components and effects116+ components200+ componentsBrowse everything; 2 free component copies per day
PaidPro: 50+ blocks and templatesAll-access: 180+ blocks, 17 templates, 2 full landing pages (one-time)A Pro version existsMembership for unlimited copies and premium templates
StackReact, TypeScript, Tailwind CSS, MotionReact or Next.js, Tailwind CSS, MotionReact, four variants: JS-CSS, JS-TW, TS-CSS, TS-TWReact, Tailwind CSS, shadcn/ui
Installshadcn CLIshadcn CLI, copy and pasteshadcn CLI or jsreposhadcn CLI, or copy a prompt for an AI agent
LicenceOpen sourceCommercial use allowed per its FAQMIT with Commons ClausePer component, set by each author
AI agentsMCP availableWorks with any editorWorks with any editorMagic MCP for Cursor, Claude, v0, Lovable and Devin

Counts are the numbers each site advertises on October 5, 2026. Treat them as a guide rather than a spec, because all four add components weekly.

Magic UI: shadcn-friendly motion

Magic UI describes itself as a UI library for design engineers and a companion to shadcn/ui. Its 150+ free components cover animated text, backgrounds, bento grids, marquees and effects, all built with React, TypeScript, Tailwind CSS and Motion (the library formerly known as Framer Motion). You add pieces one at a time with the shadcn CLI, so you only ship what you use. Magic UI Pro adds 50+ blocks and templates for assembling a landing page quickly.

Best for: teams that already use shadcn/ui and want a consistent, restrained animated layer on top. Watch for: blocks and templates sit behind the paid tier.

Aceternity UI: showpiece effects

Aceternity UI offers 116+ free components such as a 3D card effect, background beams and infinite moving cards, built with React, Tailwind CSS and Motion. Its paid all-access plan unlocks 180+ blocks, 17 templates and 2 full landing pages as a one-time purchase, which suits freelancers who reuse the same kit across clients. Components are copied into your code, then customised.

Best for: hero sections and marketing pages where one memorable effect matters. Watch for: bold effects can cost performance on low-end phones, so test before you ship.

React Bits: the biggest free set

React Bits is an open-source collection of animated, interactive and customisable React components, with 200+ pieces across text animations, UI elements, micro-interactions and backgrounds. Every component ships in four variants (JS-CSS, JS-TW, TS-CSS, TS-TW), so it fits plain CSS and Tailwind projects alike. It is licensed under MIT with the Commons Clause, which allows personal and commercial use, and it installs through the shadcn CLI or jsrepo. Its GitHub repository shows about 48,500 stars.

Best for: developers who want a large free library with a variant for their exact stack. Watch for: read the Commons Clause before you plan to resell the components themselves.

21st.dev: a registry rather than one library

21st.dev is a community registry with 12,000+ components, templates and shadcn themes from many authors. You browse and preview live, then install through the shadcn CLI or copy a ready-made prompt for an AI agent. Code lands in your repository as editable code, not as a dependency. The free tier lets you browse everything and copy two components a day. A membership adds unlimited copies and premium templates, and its Magic MCP lets Cursor, Claude, v0, Lovable and Devin pull components directly.

Best for: finding a very specific component fast, or letting an AI agent choose from a large catalogue. Watch for: styles vary by author, so a page built from many contributors needs a design pass to feel coherent.

Component library or complete page: how to choose

A component library gives you parts. You still decide the layout, the pacing of the scroll, the media, the copy, and how the whole page behaves on a phone. That is the right unit when you are building an app or a product site and need animated pieces inside a design you control.

A complete animated page is a different unit. It is a finished scroll experience with its media, scroll timing and sections already worked out. ScrollHaus is built around that second unit: each website opens as a live, scrollable preview, then you take its source and a build prompt into your AI builder. Many projects use both. A marketing page can start from a complete template, while the product UI behind it uses components from Magic UI, Aceternity UI, React Bits or 21st.dev.

A simple decision rule

  1. Need one animated element inside an existing design: use a component library.
  2. Need a whole landing page with a scroll story: start from a complete page, such as the ones in our animated website templates for AI builders guide.
  3. Need prompts for an AI builder to generate a direction: see our MotionSites review and three-way library comparison.
  4. Building with Claude Code or Cursor: combine a registry or MCP with a complete reference page.

Copy-and-paste UI versus a package dependency

Traditional React component libraries ship as an npm package you import. These four work differently: you copy the code into your repository, so you own it, can edit any detail and add no runtime dependency beyond React, Tailwind CSS and Motion. The trade-off is maintenance. When a component improves upstream, you update your copy yourself. Many teams pair copy-and-paste animated components with an unstyled primitive layer such as Radix UI, which handles accessibility and keyboard behaviour while the animated library handles looks. If you are building a SaaS landing page, that mix works well: reusable Radix primitives underneath, animated UI blocks on top, customised to your design system in your own Next.js app.

When you compare options, ask four things: can I read and change the code, is the licence compatible with my use, does it support my stack (Tailwind or plain CSS, JavaScript or TypeScript), and does it stay fast on a phone. Beautiful UI that stutters on a mid-range device costs more than it earns.

Using these libraries with AI coding tools

Because all four copy code into your project, they suit AI builders well: the agent can read, edit and extend the code it received. 21st.dev's Magic MCP and Magic UI's MCP make that explicit, and any of the libraries works when you paste a component's code or prompt into Claude Code, Cursor or Lovable. Keep prompts specific ("add the background beams component to the hero, keep the existing headline") instead of asking an agent to rebuild a page from a screenshot.

Performance and accessibility checklist

For motion performance in depth, read our scroll animation performance guide.

What these UI component libraries have in common

Comparisons of Aceternity UI vs Magic UI can make the libraries sound more different than they are. All four are copy-paste collections for the modern React interface, not installed dependencies in the old sense. You copy and paste UI code into your app and own it from then on.

For SaaS products, the practical question is which library has components that are ready for your design and development workflow. Smooth animations help you build a page that is beautiful and functional only when they are used sparingly.

Which one should you start with?

If you are on shadcn/ui already, start with Magic UI. If you want maximum free choice, start with React Bits. If you want a dramatic one-off effect, try Aceternity UI. If you want to search a huge catalogue or hand the choice to an AI agent, use 21st.dev. And if what you actually need is a finished animated page, browse the live previews on ScrollHaus and take one as your starting point.

Frequently asked questions

What is the difference between Magic UI and Aceternity UI?

Both are Tailwind and Motion based animated component libraries. Magic UI is positioned as a companion to shadcn/ui, with 150+ free components and a Pro tier of blocks and templates. Aceternity UI emphasises showpiece effects, with 116+ free components and a one-time paid pack of blocks, templates and landing pages.

Is React Bits free for commercial use?

React Bits is licensed MIT with the Commons Clause, which permits personal and commercial use. Read the Commons Clause if you plan to sell the components themselves.

Can I use Magic UI, Aceternity UI or React Bits with Claude Code or Cursor?

Yes. They install by copying code into your project, so an AI editor can read and change it. 21st.dev also offers a Magic MCP that lets agents such as Cursor and Claude pull components from its registry.

Which animated React library is best for landing pages?

Magic UI and Aceternity UI both sell landing-page blocks and templates, while React Bits and 21st.dev offer large catalogues of individual sections and components. If you want a finished scroll experience rather than parts, a complete page template is the closer match.

Do these libraries replace a full website template?

No. They supply components. A website template supplies the layout, media, scroll pacing and responsive behaviour for the whole page. Many projects use both.

Are animated components accessible?

It depends on each component. Test keyboard use and contrast, and make sure motion respects the prefers-reduced-motion setting before you ship.

What is the difference between Magic UI vs Aceternity UI vs React Bits?

Magic UI is a shadcn companion with 150+ free animated components and paid blocks. Aceternity UI focuses on dramatic effects with a one-time all-access pack. React Bits is the largest free open-source set, with four code variants per component. 21st.dev is a community registry of 12,000+ components rather than a single library.

Browse Scrollhaus website designs and build resources →

Need help with a template, account, or project? Email admin@scrollhaus.ai.