The choice between a template and a set of components is really a choice about which week you want to spend. A template gives you a finished application and asks you to live in its structure. Components give you the structure and ask you to build the pages. Both are correct answers, to different questions.
There are 324 public templates in the collection, 142 of them free, and 31 hosted here with a pinned commit. Here is when each shape is the right one.
Take a template when the constraint is time
A template is not twenty components in a folder. It is the decisions already made: routing, layout, auth wiring, theme, the responsive breakpoints, the empty states. Assembling those from scratch is most of the work in a new project, and none of it is the part that makes the product yours.
The signals that a template is right: you are validating rather than differentiating, the deadline is this week, or the surface is a marketing site where the structure genuinely is conventional.
Take components when the design is the point
The trade a template makes is structural. You inherit someone's file layout, their state approach, their component boundaries and their opinions about where things live. That is invisible while you are shipping and expensive when you start changing things, because every change happens inside a structure you did not choose.
If the product's interface is a differentiator, or the team will still be editing it in a year, components let you own the structure and borrow only the pieces.
What to check in a template before you commit
Four things, and they are all cheaper to check than to discover.
When it was last updated. Frameworks move. A template written for an older router version is a migration you did not plan.
Whether the demo is the template. A polished marketing page for a template is not evidence the code inside it is polished. Look at the repository, not the screenshot.
How much is stub. Many templates ship a beautiful shell over placeholder logic. That is fine when you expected it and painful when you did not.
The licence and what it covers. Single project or unlimited, whether you can resell, whether attribution is required.
The hosted ones
The 31 verified templates here are pinned to a specific commit and packaged, which removes the two usual failure modes: the demo that no longer matches the code, and the repository that changed under you between looking and downloading.
The hybrid, which is what most projects actually do
Take the template for the shell and the routing. Replace the hero, the pricing section and the components that carry the product's identity with pieces chosen deliberately. The pattern guides exist for exactly that half.
That combination gets the week back without inheriting somebody else's landing page, and it is why "template or components" is usually a false choice.
Where else to look
The honest list, because the answer is not always us:
| Source | Best for | Trade-off |
|---|---|---|
| Templates on 21st | 324 public, 142 free, 31 pinned and hosted | Community-made, so check the four things above |
| Framework starters | The most current routing and config, from the source | A skeleton, not a design |
| Components | Owning the structure, borrowing the pieces | You are building the pages |
| Premium template shops | Depth and support on a conventional shape | Paid, and shared with everyone else who bought it |
Taking one
Templates download as a repository; components install through the shadcn CLI against our registry:
That key comes from your 21st account, and installs require a membership. Set API_KEY_21ST once in your shell and the command works for anything in the catalogue.
Frequently asked
- Should I use a template or build from components?
- A template when the constraint is time and the structure is conventional: routing, layout, auth wiring and empty states are most of the work in a new project and none of it is what makes the product yours. Components when the interface is a differentiator or the team will still be editing it in a year, because then you want to own the structure.
- What should I check in a template before committing?
- When it was last updated, since frameworks move and an old router version is an unplanned migration. Whether the polished demo reflects the code, by reading the repository rather than the screenshot. How much of the logic is stubbed. And the licence: single project or unlimited, resale, attribution.
- Are free templates good enough?
- Often, for validation and for conventional marketing shapes. 142 of the 324 public templates in the collection are free. The four checks above matter more than the price, and a free template that was last touched two framework versions ago costs more than a paid one that was not.
- What is the hybrid approach?
- Take the template for the shell and the routing, then replace the hero, the pricing section and anything else carrying the product's identity with components chosen deliberately. That gets the week back without inheriting somebody else's landing page, which is why template-or-components is usually a false choice.