Self-Hosted / Projects / Payload CMS
Payload CMS
StableSpecs verified September 6, 2026 · against v3.x
Overview
Self-hosted headless CMS and TypeScript application framework for custom websites and products.
Payload CMS is a self-hosted headless CMS and application framework for developers building content-driven websites and custom products with TypeScript, React, and Next.js.
Why people choose Payload CMS
Payload puts the admin panel, API, access control, content modeling, and application code in one Next.js project. That is a practical alternative to a hosted CMS when a team wants code-defined schemas, control of deployment, and direct ownership of content and infrastructure.
What is included
The official project combines a TypeScript backend and admin panel with REST and GraphQL APIs, a local API, authentication, access control, localization, uploads, rich text, and database adapters. It can serve as a headless CMS or the backend for a full web application.
Requirements and tradeoffs
Payload is not a single-container, no-dependencies service. Official installation requires Node.js 20.9 or newer, a supported Next.js version, and a database adapter for MongoDB, Postgres, or SQLite. Production guidance also calls out permanent file storage, an email provider, a CDN, TLS, a strong secret, backups, and carefully tested access control.
Best fit
Choose Payload when developers want a self-hosted, code-first CMS tightly integrated with Next.js. WordPress is usually easier for a conventional non-technical publishing workflow, while Payload is a better fit when custom data models and application behavior matter.
Interface previews
Screenshots of the Payload CMS interface.
Feature support
| Feature | Support |
|---|---|
| TypeScript and React admin panelThe official project is built for TypeScript and React and includes an admin panel. | Supported |
| Headless CMS and application frameworkPayload supports headless CMS projects and broader custom applications. | Supported |
| REST, GraphQL, and local APIsOfficial documentation lists REST, GraphQL, and a local API. | Supported |
| MongoDB, Postgres, and SQLiteThese are the officially supported database adapters in the current database documentation. | Supported |
| Authentication and access controlProduction guidance requires reviewing access-control rules; authentication-enabled collections are supported. | Supported |
| File uploads and image processingUploads are supported; Sharp is optional when image resizing, cropping, or focal-point processing is needed. | Partial support |
| Localization and rich textThe database documentation notes broad feature support, while rich text is available through the supported editor package. | Supported |
Community signals
- Stars
- 45.4k
- Forks
- 4.3k
- Open issues
- 1.4k
- Last commit
- 13h ago
- Latest release
- v3.91.0
- Repo created
- Jan 2021
Includes open pull requests
1w ago
Refreshed nightly from the GitHub API.
Questions
What is Payload CMS used for?
Payload CMS is used to build self-hosted content APIs, admin-backed websites, and custom Next.js applications.
Is Payload CMS a self-hosted alternative to WordPress?
Yes, but the products target different workflows. Payload is developer-first and headless, while WordPress is typically easier for conventional editorial sites and has a larger plugin ecosystem.
What database does Payload CMS use?
Payload officially supports MongoDB, Postgres, and SQLite through separate database adapters.
What are the requirements for Payload CMS?
The current installation docs require Node.js 20.9 or newer, a supported Next.js version, a package manager, and one compatible database adapter.
Can Payload CMS run in Docker?
Yes. Official production documentation includes Docker and Docker Compose deployment patterns, but persistent storage and database configuration remain your responsibility.
Is Payload CMS free and open source?
The official repository is open source under the MIT license. Your hosting, database, storage, email, and CDN costs are separate.
Who should use Payload CMS instead of WordPress?
Payload is a stronger fit for teams that need code-defined schemas and custom Next.js behavior. WordPress may be better when non-developers need a ready-made traditional publishing workflow.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.