If you are building a React site, choose shadcn/ui when you need a free, editable base in your repository. Choose 21st.dev when the harder part is finding a finished visual pattern, such as a hero section, dashboard block, animation, shader, or template. Many projects can use both, with shadcn/ui supplying the foundation and 21st.dev supplying additional starting points.
Neither product hosts your website. They do not provide storage, email, domains, uptime commitments, data centers, or hosting backups. This is a decision about React source code, design direction, tooling, usage limits, and the license attached to each component.
Key takeaways
- Use shadcn/ui for standard controls, project tokens, forms, dialogs, tables, and source code you will maintain yourself.
- Use 21st.dev when searching, previewing, and adapting a finished visual component takes less time than starting from a primitive.
- The shadcn/ui core repository is free and MIT licensed, with no subscription renewal.
- 21st.dev has a free tier with two component copies or installs per day, while Builder starts at $6 a month billed yearly (checked November 18, 2026).
- Inspect each component’s code, dependencies, responsive states, accessibility, and license before shipping it to a client.
Which one are you actually choosing: a base or a marketplace?
You are choosing between two layers, not two interchangeable component libraries. shadcn/ui gives you an open-code base. You add source files to your React project, edit them, and keep the resulting code in your application repository. That suits a project where you want direct control over markup, styles, props, and supporting files.
21st.dev adds a marketplace and tooling layer around compatible registry conventions. Its catalog includes more than 12,000 components, 298 templates, 991 themes, 29,000 icons, 646 shaders, and 138 apps on the plans page checked November 18, 2026. Those numbers describe the size of the catalog, not whether any one item fits your project.
The practical question is what is missing from your project. If you need a dialog, form, table, navigation menu, or consistent set of design tokens, start with shadcn/ui. If you need a finished landing-page section, animated background, dashboard layout, shader, or visual direction, 21st.dev may reduce the time spent searching and adapting.
A React developer who already uses shadcn/ui should ask whether the project needs another primitive or a more complete visual pattern. You can search both places today and compare the actual source before choosing.
The cleanest answer is often conditional: use shadcn/ui as the base, then add a 21st.dev component only when its code and license fit the project.
What shadcn/ui gives you for free
When you need code that belongs to your application, shadcn/ui gives you a direct source-based workflow. Its repository describes the components as composable, accessible, customizable, and intended to become the foundation of your own component library. You add the files to your project rather than depending on a locked runtime package for every visual change.

The shadcn CLI initializes project configuration and adds registry items. A registry item can include source files, npm dependencies, other registry dependencies, aliases, destinations, and an item type. The format can support components, blocks, hooks, utilities, pages, design tokens, configuration files, documentation, workflows, and templates.
That changes how you maintain the site. You can adjust the component to match the project’s tokens, remove unused behavior, rename props, change the markup, or add a client-specific requirement. The tradeoff is that shadcn/ui does not automatically maintain copied source files. You are responsible for updates, testing, accessibility checks, dependency changes, and consistency across the application.
The CLI can consume the built-in @shadcn registry as well as custom namespaces, direct registry URLs, local files, and public GitHub registries. This makes the base useful beyond the official catalog, but it also means a successful installation does not prove that a third-party item is suitable.
The core shadcn/ui repository is MIT licensed. That license permits use, modification, distribution, sublicensing, and sale, provided the copyright and permission notices remain in copies or substantial portions of the software. It does not provide a blanket license for code from every other registry.
For a client site, the free base is usually the better starting point when you already have a design direction and want the source in your own repository. It gives you control without adding a paid shadcn/ui subscription.
What does 21st.dev add to a shadcn workflow?
If you can write a component but are spending time deciding what it should look like, 21st.dev adds a catalog, previews, prompts, themes, templates, and AI-oriented tooling. It is built around the shadcn-compatible registry model, so the source can fit a workflow where components are copied into the project.
You can search the catalog, inspect a preview, retrieve a component, and install its source files. The tooling can install declared dependencies and rewrite imports to match project aliases. 21st.dev also documents CLI installation, MCP access, and use through compatible coding agents.
The benefit is most visible with components that take longer to design than to code. A marketing hero, animated section, dashboard block, shader, or themed page may provide a useful starting point. You can then remove the pieces that do not fit and adapt the rest to the project’s existing tokens and layout rules.
That convenience has limits. 21st.dev does not replace React, Tailwind CSS, the shadcn CLI, or code review. Its catalog is not a single audited design system. Different authors can make different choices about dependencies, responsive behavior, accessibility, browser-only APIs, client and server boundaries, and licensing.
A component that looks right in a preview may still need repair on a small screen or keyboard review. An animated effect may add a runtime that the site does not otherwise need. A template may assume a particular alias, Tailwind setting, or project structure. The practical workflow is to treat 21st.dev as a source of candidates, then inspect and adapt the selected code.
A 2026 Maker Jury review called 21st.dev useful for React developers who already understand Tailwind, shadcn conventions, dependency review, responsive repair, accessibility checks, and component-level licensing. It called the marketplace a poor fit for teams that need one audited design system, uniform licensing, or components that ship without engineering review. Treat that as one reviewer's opinion, not a quality measurement.
What does it cost, what is free, and what renews?
If you are deciding whether the marketplace saves enough time, compare the complete paid commitment, not only the monthly-looking figure. These prices come from the 21st.dev pricing page, checked November 18, 2026. The shadcn/ui core repository remains free and MIT licensed, with no paid renewal.

The free tier includes browsing, previews, search, unlimited inspiration and SVG-logo search, two component copies or installs per day, and five Design Bug Bot reviews. It is a free tier, not a free trial of a paid subscription.
Builder removes the component-copy limit and includes themes, verified templates, shaders, gradients, ASCII art, and MCP and CLI search. Builder + AI starts with a 500-credit option and also has 1,000- and 2,000-credit options. Monthly credits reset and expire at that reset. Separately purchased 100-credit packs cost $5 and roll over until used.
Team pricing is for two to 50 seats and adds centralized billing, shared collections, admin controls, and private team components. Before relying on a monthly allowance, check the displayed credit balance and usage information in the account.
21st.dev says paid plans can be cancelled at any time, with access continuing through the current billing period. Its terms state that payments are non-refundable, including for non-use, accidental purchase, unused time, downgrade, or changes in marketplace availability, except where applicable law or 21st gives a different written right at checkout. Recheck the displayed price before purchase and before each annual renewal.
How do the CLI, registry, MCP, and AI work together?
If you want to work from a terminal or editor, the tools form a connected path. A registry describes the files and dependencies. The CLI retrieves and writes those files. MCP lets a compatible coding agent search or retrieve components from an editor workflow. AI can generate or adapt UI on eligible 21st.dev plans.
The CLI flow has four steps. Free accounts receive two component-code retrievals per day across the web, MCP, and CLI, while paid plans provide unlimited installs through MCP and CLI.
The shadcn CLI remains relevant because the component source follows compatible registry conventions. A 21st.dev item may declare npm packages, other registry items, files, and aliases. The tooling can resolve those declared requirements and adjust imports, but it does not decide whether the dependency belongs in your project.
MCP can reduce the interruption of switching between a browser and an editor. AI can help create or adapt a component, but the generated result still belongs in your normal review process. Test it in the target project, inspect the diff, and check what runs in the browser.
Choose this workflow when search and retrieval are slowing down development. If your team already has the right primitives and can create the missing pattern quickly, the extra CLI, MCP, or AI subscription may not save enough time.
What are the tradeoffs in dependencies, maintenance, accessibility, and licensing?
Your main tradeoff is control versus preparation time. shadcn/ui gives you source files that you can maintain directly, but it does not automatically update those files. 21st.dev can help you start from a more complete visual pattern, but each marketplace item brings its own implementation choices.

A registry item can add npm packages, another registry item, animation code, client-side logic, browser-only APIs, or assumptions about Tailwind configuration. 21st.dev’s documentation warns that the CLI does not judge whether a dependency is appropriate. Installation can succeed while adding a runtime your project did not need.
Copied registry source also creates maintenance work. The documentation identifies possible file-name collisions between registries and the absence of a version mechanism for copied registry source. Keep the diff small, record what you added, and decide how the component will be updated before it becomes part of a client site.
Accessibility needs its own check in your code. A preview does not prove that keyboard focus, labels, contrast, reduced motion, screen-reader announcements, or error states work in your application. Test the component with the project’s actual navigation, form handling, content length, and responsive breakpoints.
Licensing needs the same attention. shadcn/ui’s MIT license allows commercial use, modification, distribution, sublicensing, and sale when the required notice remains. 21st.dev’s terms say marketplace code and materials are owned by their authors and 21st Labs. The terms also restrict redistributing, selling, or licensing marketplace content without authorization, and prohibit copying it to another site or medium without a clear visible link to the original component page.
Generated components from 21st AI are described by 21st as owned fully by the user with no licensing restrictions. Do not extend that statement automatically to marketplace components. Check the license attached to each third-party registry item, then confirm the individual component’s license and attribution requirements before delivering it to a client.
Which workflow fits a React project?
For a new React project, start with shadcn/ui when the site needs dependable primitives, a consistent token system, and code your team will edit in place. Add the base controls first, then compare 21st.dev when the missing piece is a finished visual section.
For an existing shadcn/ui project, 21st.dev is worth using when visual search, previews, or AI-assisted retrieval take less time than designing the component yourself. It is less useful when the project has strict architecture rules, a small approved dependency set, or a requirement for one consistently audited source.
The most practical split is simple. Keep forms, dialogs, tables, navigation, tokens, and project-specific controls close to the shadcn/ui base. Use 21st.dev for a candidate hero, dashboard block, animation, shader, theme, or template, then copy only the source that fits.
Compare the time required for the specific component with the project’s review and adaptation time. A polished preview is useful only when it survives that comparison.
What should you do before shipping a component to a client?
Before release, review the individual component page, repository, license, and dependency list. Compare its imports, client and server boundaries, tokens, responsive states, animation behavior, and accessibility details with the target project.

Install it in a branch and run the project’s checks. Test keyboard use, screen-reader behavior, mobile layouts, long text, loading states, errors, and any browser-only code. Remove dependencies and files that the project does not need.
For a 21st.dev item, read the applicable marketplace terms and keep any required attribution or visible link. Do not place a marketplace component into a reusable public library, competing marketplace, or separate paid asset unless the license and authorization permit that use.
If the free 21st.dev allowance is enough, do not pay simply because a paid plan exists. If two copies per day interrupt the work, compare that interruption with the $72 yearly Builder commitment and its annual renewal. For a broader look at the service before deciding, read the 21st.dev review covering its marketplace, Magic MCP, costs, and fit. If the decision is mainly about billing, compare the 21st.dev free and paid plans, credits, and monthly use. Prices checked November 18, 2026.
Frequently asked questions
The next questions usually concern compatibility, ownership, limits, and client delivery.
Is 21st.dev a replacement for shadcn/ui?
No. shadcn/ui is the open-code component and registry foundation, while 21st.dev adds a marketplace, previews, prompts, themes, templates, MCP, CLI tools, and optional AI generation. A project can use 21st.dev components through a shadcn-compatible workflow.
Can 21st.dev components work with shadcn/ui?
Yes, when the individual component’s dependencies, styling, framework assumptions, and license fit the project. 21st.dev documents installation through the shadcn CLI, its own CLI, and MCP-connected coding agents.
Is shadcn/ui completely free?
The core shadcn/ui repository is free to obtain and MIT licensed. You may use, modify, distribute, sublicense, and sell copies while retaining the required copyright and permission notices.
How many 21st.dev components can I copy for free?
Free accounts receive two component copies or installs per day across the web, MCP, and CLI. The free tier also includes five Design Bug Bot reviews and does not require a card.
Does 21st.dev have a free trial?
The free tier is not a free trial of a paid subscription. It provides ongoing free access with its own copy and review limits.
Do 21st.dev paid plans renew automatically?
Paid plans renew annually at the then-current displayed yearly rate until cancelled. Cancellation stops future renewals at the end of the current billing period.
Can I get a refund after cancelling 21st.dev?
21st.dev’s terms say paid payments are non-refundable, including for non-use, accidental purchase, unused time, and downgrade. Check the checkout terms for any right provided by applicable law or written by 21st at purchase.
Can I use a 21st.dev marketplace component for client work?
You may be able to, but payment does not automatically change the component’s license. Check the author, repository, license, attribution requirements, and applicable 21st.dev terms before delivery.
Does installing a registry item prove it is production-ready?
No. Installation confirms that the tooling could retrieve and write the declared files. You still need to inspect dependencies, test accessibility and responsive behavior, run project checks, and review the license.
Who should pay for Builder + AI?
Builder + AI fits a team or developer who will use AI generation and monthly credits often enough to justify the yearly commitment. Check the current credit balance and usage information first, because monthly credits reset and separately purchased credit packs follow different rollover rules.
Do either shadcn/ui or 21st.dev host my website?
No. Neither provides web hosting, domain registration, email hosting, uptime service, storage, or hosting backups. You need separate services for those parts of a website.
Glossary
Find more reviews and guides on Even Reviews. Spotted something to correct? Contact us and include the page title.




