Dev Resources
Payload Components favicon

Payload Components

CMS/Programming/Tooling

An MIT registry and CLI that installs typed Payload CMS blocks into Payload v3 and Next.js projects with automated collection, renderer, type, and admin import-map wiring.

Payload Components's website screenshot

About Payload Components

Payload Components is an open-source registry of Payload CMS blocks, distributed via a CLI (npx payload-components add) rather than copy-paste. Running the install command for a given block copies the block's source files into the project and also wires it into the surrounding codebase: registering the block in the collection config, patching the render mapping file, and regenerating Payload's types and admin import map. The resulting changes are presented as a single reviewable git diff.

The registry is built for Payload CMS v3 projects using Next.js 15/16, Tailwind v4, and TypeScript in strict mode, and follows a shadcn-style registry pattern. The catalog includes page-builder blocks such as hero sections, feature grids, pricing/comparator tables, call-to-action sections, and contact forms, each defined by a field schema (eyebrow, title, description, items, links, etc.) and rendered live from source in the catalog rather than shown as screenshots. The project states it is MIT licensed and runs integration/e2e test suites plus a nightly fresh-repo install smoke test on every PR, with the underlying registry manifest exposed as JSON at /r/registry.json.

The product is intended for developers already working with Payload CMS who want to add prebuilt page blocks without manually writing the collection schema, render-mapping, and type-generation steps by hand for each one.

Key features

  • CLI installs Payload CMS blocks with full wiring in one command (npx payload-components add)
  • Automatically registers blocks in collection schema and render mapping files
  • Regenerates Payload types and admin import map after install
  • Open registry with browsable component catalog rendered from real source
  • MIT licensed with integration and e2e test suites gating every PR
  • Nightly fresh-repo install smoke tests against Payload 3 and Next 15/16

Frequently asked questions

What does payload-components actually install beyond the raw component files?

It copies the block source files and also patches the collection schema, render mapping, regenerates payload-types.ts, and regenerates the admin import map, landing all changes as one reviewable git diff.

What stack does this require?

It installs into projects running Payload CMS v3, Next.js 15 or 16, a shadcn registry, Tailwind v4, and TypeScript strict.

Is it free to use?

Yes, it is open-source and MIT licensed.

Who is this for?

It is for Payload CMS developers who want to install page-builder blocks (heroes, feature grids, pricing tables, CTAs, etc.) without manually wiring collection config and render mappings.

How can I browse available components before installing?

The site provides a docs/components catalog and an open registry JSON at /r/registry.json where each block is rendered live from its real source.

Ad
SerpApi - Search API favicon

SerpApi - Search API

SerpApi's Search API makes it easy and fast to scrape Google and other search engines.

Learn more

Featured products

  • SerpApi - Search API favicon
  • TranscriptFetch favicon

Show your product to thousands of developers

· 100k monthly pageviews
· 7k newsletter subscribers

Advertise your product