These seven are not one market, which is why a single ranking flatters some of them and buries others. Two of them sell components: shadcnblocks sells whole page sections under a one-off licence, and shadcn.io sells a subscription. Two of them are catalogues of other people's work: 21st.dev and shadcn.io both hold far more than anybody reads. Two of them are lists rather than shops: shadcn's own registry directory is the one the CLI already knows about, and awesome-shadcn/ui is the only entry that publishes its acceptance criteria in full. Shoogle and BlockDex are indexes over all of it, and the difference between them is the unit: Shoogle lists registries, BlockDex lists items inside registries and probes whether each one still resolves. The question that decides your answer is not which is best, it is whether you are buying a component, finding a registry, or finding one component inside 997 registries.
CriterionBlockDex21st.devshadcnblocks.comshadcn/ui registry directoryawesome-shadcn/uishadcn.ioShoogleWhat you get without payingAll of it, including the APINo account, no key and no paid tier anywhere on the site, and the same is true of the index itself: "No key, no account, CORS open to everyone. Every screen on this site makes exactly one call, and these are the calls." The whole corpus is readable as JSON by anyone, which is the part none of the paid catalogues in this table offer at any price.Not publishedThe pricing page publishes three plans — Builder, Builder + AI and Team — and none of them is a free tier. Browsing the catalogue does not appear to require an account, but the site publishes no free plan, so this is what the page carries rather than what a visitor can infer.Free blocks, behind a login"Try our free blocks first. Browse free blocks in the library-ready to copy/paste. Basic-tier blocks only require a login; see the full catalog for every category." The site reports 22,162 free users against 5,420 pro customers.All of it"Discover community registries for shadcn/ui components and blocks. These registries are built into the CLI with no additional configuration required." No account and no key; what each listed registry charges is its own business.All of it, MITA public GitHub repository — 20.3k stars, MIT licence shown in its own sidebar — and free use is also a condition of being listed: "It is free to use. Open source is the norm here … What does not get in is a product that is paid end to end, with no free tier and no public code."A $0-forever tier, community supportThe plan comparison publishes four columns and the first is "Free — $0 forever", whose support row reads "community". The same column carries a dash rather than a value on its commercial-use and MCP-usage rows, so what the free tier buys is browsing rather than shipping — that is the page's own table, not an inference about the account.Everything on the siteThere is no pricing page — https://shoogle.dev/pricing returned 404 when this row was checked — and no account gate on browsing, the directory or the MCP endpoint. The only commercial surface anywhere in the navigation is Sponsor, which is the same model SkillWorks runs and the opposite of a per-seat catalogue.Cheapest paid optionNot publishedThere is no pricing page and no paid tier. BlockDex does not sell components — it indexes the registries that do, including the paid ones, and says which is which.$6/month, billed yearly (Builder)"Builder — for individuals. $6 per month billed yearly." Builder + AI is $15 a month on the same terms and adds 500–2,000 monthly AI credits; Team is per seat. A yearly/quarterly toggle on the page offers "save 25%".$149 one-time (Pro, lifetime)"Pro plan — lifetime access $149 /one-time … single user, lifetime access & updates, 2093+ pro components, 1678+ pro blocks." Premium is $299 and Elite $399, both one-time, adding templates, a Figma kit, an admin kit and pre-built pages. The only lifetime licence of the four.Not publishedThe registry directory and the registry documentation publish no price, plan or tier of any kind. Read on ui.shadcn.com's own directory page on 14 August 2026.Not publishedThere is nothing to buy: the list is a repository, and it publishes no price, plan or sponsorship tier for readers. Read on the repository's own page on 14 August 2026.$32/month, billed annually as $389 (Individual)"Individual — solo developer. $32 per month · billed annually as $389", covering "all access 1 seat, personal & OSS use"; the same plan is $49 a month on monthly billing. Team is $66 a month billed annually as $789 for 5 seats with commercial use, and Organization is $132 a month billed annually as $1589 for unlimited seats. A third tab on the same control offers "lifetime · pay once".Not publishedNo plans, no tiers and no purchase surface. /pricing 404s and the MCP page's only call to action is the Discord. Read as sponsor-funded rather than free-forever: the site publishes no commitment either way, so this is what the page carries rather than what a visitor can infer.What it publishesEvery item in every public registry it can findItem-level rather than registry-level: the unit is the component, not the library it lives in. The live figures are deliberately not printed here — the crawl runs nightly, so any number in this table is wrong within a day. /api/stats is the current one. The method page publishes the coverage limit too: source is read for the first 150 items per registry, "a size decision, not a coverage one".12,000+ components, templates and themes"The living library of interfaces. 12,000+ crafted React components, templates, and shadcn themes." Broken down on the same page as 2,000+ marketing blocks and 2,100+ UI components, with "used by 3,190,767 builders".2104+ components, 1858+ blocks"2104+ Pro Components" and "1858+ Pro Blocks" on every one of the three lifetime plans, with 20 Premium Templates and a 484-screen Figma Kit on the higher two. The page also publishes its own rate of change — "50+ New components each month", "100+ New blocks each month" — which is why a figure copied from it goes stale: it read 2093+ components and 1678+ blocks on 2026-08-21 and 2104+/1858+ eleven days later.Not publishedThe directory lists community registries but publishes no total for how many it carries and no per-registry item count. Read on ui.shadcn.com's own directory page on 14 August 2026 — which is the specific gap BlockDex crawls to fill.Not publishedThe list is a set of markdown tables with a Name, Description, Link and Date column, and publishes no total. Its headline numbers are repository numbers — 20.3k stars, 1.3k forks — not item counts.6,000+ marketing blocks, 14 premium templates, 59 themes, 285k+ React iconsThe plan-comparison rows enumerate the catalogue by kind rather than as one total: "premium templates (14)", "marketing blocks (6,000+)", "themes (59)", "react icons (285k+)", plus unnumbered rows for UI components, AI components, React hooks, charts, shaders and animations. BlockDex's own nightly crawl counts 7,847 items served from its registry manifest, of which 1,430 item endpoints answered as paid and 70 returned source — the largest single registry in this index.372 registries; item count not published"S 372 registries" on the directory, over the same community set shadcn's own directory lists. The count was 292 when this row was read on 6 September 2026. The MCP page carries a UI-components counter and a registries counter, but both render as animated digit rollers rather than a number, so the page states no item total. The registry endpoint is bounded rather than complete in another way too: https://shoogle.dev/r/registry.json?q=button answers with pagination {"hasMore":false,"limit":100,"total":100}, a top-100 per query, not a corpus size.How you install from itCopy the shadcn CLI command off the rowEvery row carries the command that installs that item from its OWN registry — BlockDex is not in the install path and mirrors nobody's source. The command is verified rather than constructed: the crawler fetches "the exact URL npx shadcn@latest add would fetch", which is also how free and paid are decided, so a row that says free is a row whose install has already been made once.Copy a prompt, or MCP and CLIThe primary route is the prompt — "Copy the prompt. Paste it anywhere" — with unlimited MCP and CLI retrieval listed on every paid tier: "search components via mcp & cli", "unlimited installs via mcp & cli". The only one of the four that installs by pasting into an agent.The official shadcn CLI"All components and blocks available via the official shadcn CLI 'npx shadcn add'", with "all blocks searchable via the official shadcn MCP" and an IDE extension for VS Code and Cursor listed beside it.npx shadcn add @<registry>/<component>The canonical command, and the reason the other three all reference this CLI rather than shipping their own. The docs add that "the registry works with any project type and any framework, and is not limited to React".Not publishedThere is no installer and no manifest; every row is a link, and installation is whatever the linked project documents. What the list does require is that the thing be installable somewhere — its first acceptance rule names "a registry you can install from, a port, a plugin, a tool built for shadcn projects".Its own MCP server, or the editor you already use"One MCP. Every AI agent. Ship faster." is a front-page heading, alongside "Works with the editors you already use". It also serves a shadcn registry manifest from the published site rather than only from a repository, which is what makes its items installable by URL and what BlockDex indexes it through.Through the official shadcn CLI, as a namespace"Search with npx shadcn@latest search @shoogle — filter by type, limit, and offset without leaving your terminal." It is a shadcn registry namespace, so results come back already addressed to their SOURCE registry — the button row of that endpoint carries "addCommandArgument": "@animate-ui/primitives-buttons-button" — and the install runs against the origin registry rather than through Shoogle. The same index is also served as an MCP server over streamable HTTP for Claude, Cursor, Windsurf, VS Code and Cline. No other entry in this table is reachable from inside the CLI.How something gets listedNothing is listed; everything is crawled"Every number on this site is derived from something a registry actually served. There are no submissions, no editors and no way to buy a position." Registries are found four ways — seeds, GitHub code search for registry.json, GitHub topics, and the ecosystem's awesome-list mined for site links as well as repo links — and roughly two thirds of what that finds never reaches the index.Not publishedNeither the pricing page nor the front page publishes a submission or contribution route for getting a component into the marketplace, or terms for authors who do. Both were read on 14 August 2026.Not publishedNo submission, contribution or author route is published on the pricing page. What that page does publish is a first-party production cadence — "50+ new components each month, 100+ new blocks each month, 10+ new pages each month, 1+ new template each month" — which describes a catalogue the site writes rather than one it collects.A documented add-a-registry route"Don't see a registry? Learn how to add it here", with "Add a registry — learn how to add a registry to the directory" as its own documentation page beside Getting started, Authentication and Namespaces.Pull request, against five published rules"Two ways to submit" — a form on awesomeshadcn.dev that opens the pull request for you, or editing README.md directly — and "either way, one resource per pull request". Acceptance is explicit: "a resource has to clear all five", the first being that it is genuinely about shadcn/ui rather than merely using it.Not publishedNeither the front page nor the pricing page publishes a submission route, contribution terms, or an arrangement for third-party authors. Both were read on 20 August 2026. The showcase sections on the front page — "Built with shadcn.io", "Devs love shadcn.io" — are sites using the catalogue, not authors publishing into it.Pulled from shadcn's own directory, plus submissions"Community registries pulled from the shadcn/ui directory, with sorting to make it easier to track newly added registries." So the inclusion decision is shadcn's, not Shoogle's, with a documented route for a registry that is not in it yet. Categories are assigned per registry — Design System, Marketing UI, AI Blocks and twenty more — and the sort is by when the registry was added.What it says about the code's qualityWhether it installs and whether it still exists"Crawled, not curated" — there is no taste judgement and no editorial ranking anywhere on the site. What is checked is mechanical and per item: whether the registry's own item endpoint serves the source (free), refuses it (paid), or was never reachable (unknown, and never rendered as free), and whether an item that was once indexed has since disappeared. An item that vanished keeps its page and says so, because that is the page someone arriving from a stale tutorial needs.Authorship, stated as the guaranteeThe claim is about who wrote it rather than about what checks it: "built by real design engineers", under a pricing-page headline that reads "Keep the web free of AI slop". No review process, test or automated check is published.Hand-designed in-houseThe templates are "hand designed and built Next.js & Astro multi-page marketing templates built with shadcn/ui and figma files". As with 21st.dev the claim is about authorship rather than about a review step, but here everything is first-party, so there is no third-party code to review.Explicitly not reviewed, and it says so"Community registries are maintained by third-party developers. Always review code on installation to ensure it meets your security and quality standards." The only one of the four that states the limit of its own vouching rather than implying there is none.Human review plus three CI workflows"Three workflows run on your pull request and on main": Format README, which "fails if any name or url is duplicated, or if a row has no usable link"; Add dates, which stamps the date column; and Link check, which "runs weekly across the whole list and reports broken links in an issue". The only automated ongoing check of the four — and it checks that links resolve, not that code works."Production-ready", asserted"Production-ready React components your team can copy, paste, and ship today" is the pricing page's own subtitle, and the front page repeats the word. Nothing on either page describes a review step, a test suite or an automated check that a component builds — the claim is authorship and finish, made directly. No entry in this table publishes a build check, which is the gap BlockDex crawls all of them for.Not publishedNothing on the directory or the MCP page claims review, curation, testing or any check of the code behind a listing. The one quality statement the site makes is about itself: every page carries an Alpha badge beside the wordmark.
BlockDex is one of the 7 compared and publishes this table. "Not published" means that company does not state the figure on the page cited below. It is not a claim that no such figure exists: this table prints what was read, not what was inferred.
What is the difference between a shadcn registry and a block library?
A registry serves a registry.json manifest the shadcn CLI can install from, so `npx shadcn add` works against it with no copying. A block library sells or gives away page sections you paste in yourself. Several entries on this grid are both, which is why the install row is on it: it is the row that tells you whether you will be running a command or opening a file and selecting all.
Which shadcn registries are free?
shadcn's own registry directory and awesome-shadcn/ui cost nothing and never ask for an account. Shoogle and BlockDex are free indexes over the rest, and BlockDex publishes its whole corpus as an open API with no key and no account. 21st.dev, shadcnblocks and shadcn.io all have a free tier and a paid one, and the grid above prints the cheapest paid option each of them publishes, with the page it was read off. The free row and the paid row are separate on purpose: a catalogue that is free to browse and paid to install from is a different thing from one that is free to install from.
How is this different from the best shadcn registries ranking?
That page ranks, this page registers. The ranking scores four measured inputs with published weights and produces an order, which is the right shape when the question is which one to use. This grid produces no order at all: every column answers the same six criteria and you decide which criterion matters. If you already know what you need, read the ranking. If you do not yet know what the options are, read this.
How current are these figures?
Every cell carries the day it was read, and a job re-reads them rather than a person promising to. On 2026-09-19, scripts/verify-competitors.mjs re-fetched every source cited on this grid and 37 of 39 checks passed. The two that did not are this site's own item count, which moves every night as the crawl runs, and one shadcn.io cell whose quoted figures are spread across separate elements on their pricing page rather than sitting in one sentence. Both are named here rather than left in a log.
When you should pick one of these instead of BlockDex
BlockDex is not the right answer to every version of this question. Each case below is a real one.
21st.dev: You want breadth and you work by pasting a prompt into an agent rather than by running a CLI. It is the largest catalogue of the four at "12,000+ crafted React components, templates, and shadcn themes", it is the only one whose delivery mechanism is the prompt itself — "every component ships as a prompt. One copy - and it builds itself in whatever tool you live in" — and it is the cheapest recurring entry here at $6 a month billed yearly, with unlimited MCP and CLI retrieval on that tier.
shadcnblocks.com: You want whole page sections rather than components, you want them from one hand, and you would rather pay once than subscribe. It is the only one of the four with a lifetime licence — $149 one-time for 2093+ components and 1678+ blocks — the only one shipping a Figma kit and an admin kit alongside the code, and the only one publishing a maintenance cadence you can hold it to: "50+ new components each month, 100+ new blocks each month", established 2023.
shadcn/ui registry directory: You want the first-party answer and the shortest possible path from finding a component to having it in your repository. This is the mechanism every other entry here sits on top of, it costs nothing, and the registries in it are "built into the CLI with no additional configuration required" — so `npx shadcn add @<registry>/<component>` works with no account, no key and no config. It is also the only one of the four that tells you plainly what it does not do.
awesome-shadcn/ui: You want the rules a listing was judged by written down where you can read them, and you want to browse rather than install. It is the only one of the four that publishes its acceptance criteria in full — "this page is the full set of rules a submission is judged by - nothing is checked that isn't written here", five conditions, one resource per pull request — and the only one running an automated link check across its whole list every week. It is also the only one whose free-to-use requirement is a listing criterion rather than a pricing decision.
shadcn.io: You want one paid licence that covers the whole surface — sections, icons, themes, hooks — and you drive your editor with an agent rather than a CLI. It is by a wide margin the largest registry in this index at 7,847 items crawled, its own pricing page counts "marketing blocks (6,000+)" and "react icons (285k+)" behind a single seat, and it publishes an MCP server so an agent pulls from it without a copy-paste step: "One MCP. Every AI agent. Ship faster." It also has the lowest-commitment way in of the paid entries here, a $0-forever tier you can browse from before deciding.
Shoogle: You want the answer inside the tool you are already in rather than in a browser tab. Shoogle is the only one here that registers as a shadcn NAMESPACE, so `npx shadcn@latest search @shoogle` searches across community registries from the terminal and the install runs through the official CLI — no site, no copy-paste, and the same route works from any MCP client that speaks streamable HTTP. It is the shortest path from "is there a component for this" to the component being in the project. It also labels itself Alpha, and it publishes no figure for how many items that search covers.
Other shadcn registries and block libraries compared head to head
Prices and limits move. Every source is printed here so a reader can check it on the day they read this, and a job re-fetches each of these URLs on a schedule and fails when a figure above no longer appears on the page it came from.
shadcnblocks.com, www.shadcnblocks.com/pricing: Cheapest paid option, What it publishes, How you install from it, How something gets listed, What it says about the code's quality. Read 2026-09-18.
shadcn/ui registry directory, ui.shadcn.com/directory: What you get without paying, Cheapest paid option, What it publishes, How you install from it, How something gets listed, What it says about the code's quality. Read 2026-09-18.
shadcn.io, www.shadcn.io/pricing: What you get without paying, Cheapest paid option, What it publishes, What it says about the code's quality. Read 2026-09-18.