Skip to content

shadcn/ui blocks, templates and themes

1043 items you install with the shadcn CLI, plus 26 complete website themes. Pick where you want to start.

Start here

Where themes.dev fits next to shadcn/ui

shadcn/ui gives you the parts and leaves the pages to you. That is the right split for a component library, and it means every project starts by building the same hero, pricing and settings screen again. We build those, on the parts you already have: 831 of our 860 blocks import shadcn/ui components directly, and all of them use its tokens.

Nothing here replaces shadcn/ui or wraps it. Each item is a file the CLI writes next to your own components, with the shadcn parts it needs pulled in as dependencies. Delete it tomorrow and nothing else breaks.

New to shadcn/ui, or coming back after a year? shadcn/ui explained is our long guide to how it works now: the CLI, the three foundations, theming, registries and the trade-offs.

How it works with shadcn

From the catalogue to your components folder

  1. Add the registry

    Once per project: the @themesdev entry in components.json, with your API key read from THEMESDEV_TOKEN. Making a key takes a free themes.dev account.

    components.json
    {
      "registries": {
        "@themesdev": {
          "url": "https://www.themes.dev/r/ui/{name}.json",
          "headers": { "Authorization": "Bearer ${THEMESDEV_TOKEN}" }
        }
      }
    }
  2. Install by number

    Every item has a store number. This one is hero-09 (Ferrow); the CLI adds the shadcn/ui parts it needs first.

    terminal
    npx shadcn@latest add @themesdev/hero-09
  3. Edit it as your code

    The file lands in components/hero/ in your project. No package, no runtime, no lock-in: change the markup, the copy and the classes like anything else you wrote.

See it on the item’s own page: hero-09 (Ferrow). Set up your key in your account.

Questions

shadcn/ui and themes.dev

The short version of what people ask us about shadcn/ui. Something missing? Send us a message.

  • What is shadcn/ui?

    An open-source set of React components on Base UI, Radix or React Aria and Tailwind CSS, made by shadcn. Instead of installing a package, a CLI copies each component’s source into your project, so you own and edit it.

  • Is themes.dev part of shadcn/ui?

    No. themes.dev is independent. We build blocks, app screens, page templates and website themes on top of shadcn/ui and serve them from our own registry, which the shadcn CLI installs from like any other.

  • What is a shadcn registry?

    A URL that serves components as JSON the shadcn CLI understands. Ours is @themesdev: add it to components.json once, and npx shadcn add @themesdev/<number> installs any item by its store number.

  • What do I get for free?

    29 blocks and 57 components, plus 30 UI Pro blocks with a free account. Everything else is UI Pro, from €199 once.

  • Which frameworks does it work with?

    Anything shadcn/ui works with: Next.js, Astro, Vite, React Router, TanStack Start. The website themes come as complete Astro projects, and as Next.js + Sanity with UI Pro Complete.

Frank Spin

Not sure where to start?

Tell us what you are building and we point you to the blocks or theme that fit.

Frank Spin · Founder of themes.devSend a messageEvery message reaches him directly

UI Pro

Everything for shadcn/ui, paid once

Every block, page template and website theme from €199, paid once, with every update and everything we add later. Not ready? The free blocks are open to everyone.

blocks
860
page templates
14
website themes
26
The Case study page template from UI Pro, built from its blocks.

This page is built from UI Pro blocks: Brouwlab (page-header-01), Straalnet (faq-10), Rooilijn (call-to-action-07).