Checked against official sites on November 2, 2026.
You need a pricing section, a hero and a footer. The useful question is not which library has the most components. It is which registry gives you a complete section that fits your project, and what happens when your agent installs it.
My shortlist: shadcn/ui for free application layouts, Shadcnblocks for a broad marketing catalog, Tailark for marketing pages, VibeUI for a visual pick → AI instruction → install workflow, and Magic UI for animated details.
Disclosure: I build VibeUI. It is included below with its account requirement, free limit and paid restrictions. This is a documentation-based comparison, not a benchmark of installation speed or agent accuracy.
What a registry actually gives you
A shadcn registry distributes source files and their declared dependencies into your project. It can contain a small control, a section or several files for a page. The format does not guarantee a shared visual style, license or dependency list.
The official registry documentation describes the distribution model. Check the actual block and access terms before choosing a library for a client project.
Quick comparison
| Registry | Where I would start | Free access | Paid boundary | Install route |
|---|---|---|---|---|
| shadcn/ui | Sidebars, login screens, dashboard layouts | Official blocks are free and open source | No paid tier for the official blocks page | shadcn CLI |
| Shadcnblocks | Heroes, pricing, product and marketing sections | Free blocks; Basic blocks require login | Pro blocks and larger bundles | Namespaced shadcn CLI; key for Pro |
| Tailark | Marketing websites with a selected design style | Free pages, blocks and snippets | Premium blocks, illustrations and page collections | Registry workflow; follow the selected block's instructions |
| VibeUI | Pick a designed block and hand it to Cursor or Claude Code | Free account: 20 different components per month | PRO-only items and scenarios; unlimited copies with PRO | Copy for AI or authenticated shadcn namespace |
| Magic UI | Animated text, backgrounds and UI effects | Public component documentation and source | Separate Pro blocks and templates | shadcn CLI |
The rows describe different products. A background effect and a whole dashboard are both installable source, but they do not replace the same amount of work.
1. shadcn/ui: start here for application layouts
The official blocks page includes dashboards, collapsible sidebars and authentication layouts. It shows the files, preview and install command together.
For example, the documented dashboard command is:
npx shadcn@latest add dashboard-01 Choose it when: you want an application layout built around the shadcn system and are comfortable doing the product-specific design yourself.
Check first: the file list. A dashboard can add a page, several components and example data. An agent still needs instructions about where that page belongs and which sample data to replace.
2. Shadcnblocks: a wide marketing catalog
Shadcnblocks separates blocks, components and templates. Its categories include heroes, pricing, testimonials, product sections and dashboards. Free blocks are available, while Pro access and higher bundles cover more of the catalog.
The CLI guide documents the registry configuration and API-key authentication for Pro. Its example command is:
npx shadcn@latest add @shadcnblocks/hero1 Configure the registry as the guide describes before using the command.
Choose it when: you want many section variants to compare for a commercial site.
Check first: whether the exact block is free or Pro, and which primitive-library build matches your project. A large catalog is useful only if the chosen section installs into your actual setup.
3. Tailark: a marketing-site starting point
Tailark focuses on marketing sites, with blocks, pages and illustrations in multiple styles. It states compatibility with Radix UI and Base UI.
Its pricing page distinguishes free pages, blocks and snippets from premium blocks, illustrations and fuller page collections. Do not assume every page shown in a preview belongs to the free tier.
Choose it when: the design of a marketing page is the main decision, and you want to work within one of its styles.
Check first: access to the exact section and the installation instructions attached to it. I would select the hero and the following content section together before committing to a style.
4. VibeUI: visual selection with an agent instruction
VibeUI (vibeui.club) is a shadcn-compatible catalog of React/Tailwind components, landing blocks and animations. Each item has a Copy for AI instruction with the install command, dependencies, what to preserve and what can change.
The useful distinction is the handoff: choose a preview, give the instruction to the agent, and ask it to install that component. The instruction is intended to preserve the selected design; it is not a guarantee that an agent will follow every rule.
The installation guide covers Copy for AI and an authenticated namespace. Use the command generated for your account instead of copying somebody else's temporary link.
Choose it when: you already know which block you want and need to communicate that choice to an AI coding agent.
Check first: a free account allows 20 different components per month. Some blocks, animations and page scenarios need PRO. The English pricing page lists $9 for a month or $69 for a year, paid once with crypto and no automatic renewal. Those restrictions matter if you prefer open-source-only tools or another payment method.
5. Magic UI: add motion where it earns its place
Magic UI's installation guide uses the shadcn workflow. Its catalog includes animated text, backgrounds, marquees and other effects; Pro blocks and templates are offered separately.
The guide's example is:
npx shadcn@latest add @magicui/globe Choose it when: the page layout is already settled and you need a specific animated element.
Check first: the selected component's dependencies and motion behaviour. A visual effect is an addition to the page, not a substitute for its structure or content.
How to hand a registry block to an agent
A bare URL leaves too much room for interpretation. I would send a brief like this:
Install the exact block using its documented command. Read the registry files and dependency list before editing. Put it on the existing landing page. Keep its layout, spacing, typography and motion initially. Replace only the copy, links and brand assets. If installation or access fails, report the error before substituting another block. Check the result on mobile and with reduced motion enabled. For private registries, the shadcn namespace documentation supports authentication headers using environment-variable placeholders. Keep the actual token out of the prompt, repository and screenshots.
My selection rule
Start with shadcn/ui for the app shell. Compare Shadcnblocks and Tailark for marketing sections. Consider VibeUI when the design-to-agent handoff is the problem. Add Magic UI when you can name the effect the page needs.
Before paying or installing, check three things on the exact item: access, dependencies and license. Then install one representative block and inspect it in your project. That tells you more than the library's total component count.
