Best shadcn/ui blocks, registries and block collections

Start with the official shadcn/ui blocks for dashboards, sidebars and login pages, then add one or two community registries for what they do not cover: marketing sections, product screens or advanced components. This guide covers nine block collections and registries that install with the shadcn CLI, with what each contains, who it suits, license, cost and one limitation apiece.

Blocks, registries and the CLI

A block is a composed section or page (a sidebar layout, a login screen, a pricing section) built from components. A registry is a JSON index that the shadcn CLI can read, so npx shadcn add @registry/item writes the block's source into your project along with its dependencies. The official registry directory lists community registries that work with no configuration and warns that they are maintained by third parties, so review the code on installation. Our shadcn registry glossary entry and the custom registry guide explain the format if you want to publish your own.

At a glance

1. shadcn/ui blocks

The official blocks are clean, modern building blocks you copy and paste into your apps, free forever and installable with commands such as npx shadcn add dashboard-01. The current set covers a dashboard with sidebar, charts and data table, sidebars that collapse to icons or carry submenus, and login pages with and without an image panel, and the February 2026 changelog added blocks for both Radix UI and Base UI so you can pick the primitive your project uses.

Who it suits: every shadcn/ui project; the dashboard and sidebar blocks are the fastest honest start for an app shell. License and price: MIT, free. Limitation: the set is small and app focused. There are no marketing sections, pricing tables or settings screens, which is exactly what the rest of this list exists for.

2. Tailark

Tailark is an open source shadcn/ui registry of marketing blocks and pages, the sections a landing page is made of. The repository describes itself as shadcn marketing blocks and is released under the MIT License, and the blocks are browsed on tailark.com.

Who it suits: a product site that should look like it belongs with a shadcn/ui app. License and price: MIT for the open source registry; the site may offer more than the repository, and we could not read its pricing when we checked, so look before you plan around it. Limitation: it is marketing only, so you still need an app registry for the product screens behind the sign up button.

3. Launch UI

Launch UI is a landing page kit built with Next.js, shadcn/ui and Tailwind CSS that you copy and paste into your project. The README splits the sections in two: navbar, hero, items, logos, FAQ, stats, CTA and footer are included, while the bento grid, feature, social proof, tabs, carousel and testimonials sections belong to the Pro version.

Who it suits: a single polished landing page where the free sections are enough. License and price: the repository is MIT; Pro is paid and priced on its pricing page. Limitation: the sections that make a landing page feel complete, such as testimonials and feature grids, are the Pro ones, so budget for the upgrade or source those from another registry.

4. Kibo UI

Kibo UI is a custom registry of composable, accessible and open source components designed for use with shadcn/ui, described by its maintainer as free and open source, forever. It fills gaps in the core set with more advanced, reusable building blocks that reduce boilerplate while keeping flexibility, and installs with the shadcn CLI.

Who it suits: adding a few hard components to a standard shadcn/ui project without adopting another library's look. License and price: MIT, free, no paid tier. Limitation: it is components rather than page blocks, so it answers the question of how to build a thing, not how to lay out a screen.

5. coss ui

coss ui is the official design system of Cal.com: beautifully designed, accessible and composable components for React apps, built on Base UI and styled with Tailwind CSS, with ready compositions called Particles. The repository also holds Origin UI, the pre-acquisition collection of Radix based, shadcn style components, which remains available with limited support while active development focuses on Particles.

Who it suits: a clean, neutral application base shaped by use in a real product, especially on Base UI. License and price: the apps/ui and apps/origin directories are MIT, while the rest of the repository is AGPLv3, so copy from the UI apps and not from elsewhere. Limitation: the mixed licensing needs attention, and the Origin UI collection many people know is now in maintenance mode.

6. MiniDev UI

MiniDev UI is a shadcn-compatible registry of over 500 items built on Base UI, Tailwind CSS v4 and motion, and more than 40 of them are full blocks and pages: dashboard home, billing, settings, sign in, analytics, chat, pricing plans, marketing landing, status page and more, all reading one set of semantic OKLCH tokens. Browse them by type at blocks, or install one with npx shadcn@latest add @minidev/dashboard-home.

Who it suits: SaaS teams that want the app screens and the marketing site from one registry so they share tokens, materials and motion. License and price: MIT, free, no paid tier. Limitation: it is built on Base UI, so a project that standardised on Radix will end up with both primitive layers if it mixes in these blocks, and it is React only.

7. Cult UI

Cult UI describes itself as components crafted for design engineers: pieces styled with Tailwind CSS that work with shadcn/ui and are added by copying and pasting. The repository is MIT.

Who it suits: teams that want distinctive components to lift a marketing page or onboarding flow above the shadcn/ui defaults. License and price: MIT for the open source components; the site lists more than the repository and we could not read its prices when we checked. Limitation: it leans toward expressive components rather than complete page blocks, so it is an addition to a base, not the base.

8. blocks.so

blocks.so is an open source library of UI blocks built with React, Tailwind and shadcn/ui: accessible, customisable blocks you copy and paste, free and open source. It serves a registry, so the CLI installs any block from https://blocks.so/r/{name}.json, and the repository is MIT.

Who it suits: quick sections in the plain shadcn/ui look, installed by URL without adopting another library's opinions. License and price: MIT, free, no paid tier. Limitation: it is a personal project with a smaller catalogue than the commercial collections, so check that the block you need exists before you plan around it.

9. 21st.dev

21st.dev calls itself an open source community registry for React UI components, and its repository description puts it as npm for design engineers: a marketplace of shadcn/ui based React and Tailwind components, blocks and hooks that anyone can publish to and that install with the npx shadcn command. The platform code is MIT.

Who it suits: finding a specific component someone has already built, and comparing several versions of the same idea. License and price: the platform is MIT; each published component carries its own author's terms, so read the listing. Limitation: quality varies with the author. Treat it like any package registry and review the code before it ships, which is the same warning shadcn/ui attaches to its own directory.

How to choose

Pick one base and at most two specialists. The base is the official blocks for the app shell, or MiniDev UI or coss ui if you want finished product screens on Base UI. The specialists depend on the gap: Tailark or Launch UI for marketing sections, Kibo UI for advanced components, Cult UI for expressive pieces, blocks.so for quick app sections, and 21st.dev when you are hunting for one specific thing. Paid marketing collections such as Magic UI Pro ($199 one time) and Aceternity UI's blocks are worth it when a launch page needs more polish than the free sections give you, and Shadcn Studio pairs an MIT theme generator with free and premium templates if you want to retheme everything first.

• Match primitives. shadcn/ui now defaults to Base UI, and so do coss ui and MiniDev UI; Origin UI and many older registries are Radix based. Mixing works, but one layer keeps the bundle and your mental model smaller.
• Check what the tokens are. Blocks that read --background, --primary and the other shadcn/ui variables follow your theme; blocks with hard coded colors do not. Switch to dark mode right after installing.
• Watch file collisions. Several registries ship their own button or card. The CLI asks before overwriting; decide which version you keep.
• Review third party code. Every community registry is someone else's code going into your repo. Read it once, the way you would read a dependency's changelog.