Blocks
creative-tim/ui blocks: 111 sections with preview
All 111 blocks published by creative-tim/ui, with categories, file counts and licence. The table lists the biggest sections and links to each preview.
Key points
- 111 blocks in 111 files, with ecommerce and testimonials as the main categories.
- One npm dependency: the rest are shadcn primitives.
- MIT licence, though the catalogue still says see source.
creative-tim/ui publishes 111 blocks in 111 files: one file per section, all in the same shape. The densest categories are ecommerce and testimonials with 17 blocks each, then contact and footers with 15.
Blocks with the most files
| Block | Registry | Files | Category |
|---|---|---|---|
| account-2fa-01 | creative-tim/ui | 1 | account |
| account-avatar-upload-01 | creative-tim/ui | 1 | account |
| account-basic-info-01 | creative-tim/ui | 1 | account |
| account-change-password-01 | creative-tim/ui | 1 | account |
| account-integrations-01 | creative-tim/ui | 1 | account |
| account-notifications-01 | creative-tim/ui | 1 | account |
| account-sessions-01 | creative-tim/ui | 1 | account |
| ai-chat-streaming-01 | creative-tim/ui | 1 | ai agents |
What this source contains
- Repository: creativetimofficial/ui
- Site: https://creative-tim.com/ui
- Licence: MIT (LICENSE file in the creativetimofficial/ui repository)
- Categories: taken from the publisher manifest, not invented.
When to use it
It pays off when you need a complete marketing page and want sections that share one language: 111 blocks with a single npm dependency, date-fns. The limit is the reverse: no block targets a dashboard, and the eleven modals are variations on one schema.
Ecommerce and testimonials: the two halves of the catalogue
With 17 ecommerce blocks and 17 testimonial blocks, creative-tim/ui covers both ends of a sales page: the goods and the proof. In between sit 15 contacts and 15 footers, the parts usually copied last and adapted worst.
The surprise is how few dependencies it needs: date-fns and nothing else. Everything else comes through shadcn registry dependencies, button, card, input, select, calendar, so adoption costs depend on the primitives you already have. A shadcn project starts without installing anything new.
Eleven modals and seven account screens show where the catalogue is weaker: they are variations on one schema, not complete flows. If you are building the signed-in area, expect to wire the sections yourself; if you are building a landing page, the material is there.
curl "https://ui.eneawork.it/api/blocks?source=creativetimofficial-ui&limit=8"Three examples from the table: account-2fa-01, account-avatar-upload-01, account-basic-info-01; the full inventory is at /blocks. For the counting method read how the block catalogue is built, for the copy-versus-compose comparison read the economics of sections, and for heroes read the shadcn hero guide.
Frequently asked questions
How many blocks does creative-tim/ui publish?
111 blocks in 111 files, measured on 1 November 2026: one file per section, with no shared components in the package.
What licence does creative-tim/ui use?
MIT in the creativetimofficial/ui repository, which has over twelve thousand stars. The catalogue shows see source, so read it with the LICENSE file.
Which categories does creative-tim/ui cover best?
Ecommerce and testimonials with 17 blocks each, then contact and footers with 15. Modals and account screens stay at eleven and seven sections.
How many npm dependencies does it need?
Just one, date-fns. Everything else arrives as a shadcn registry dependency, so the cost depends on the primitives you already have.
Can I use it for a dashboard?
No, the catalogue targets marketing pages. A back office needs sidebar and table blocks, which are not here.