Payload CMS: Scalable Headless CMS for Developers
Discover how Payload CMS combines the power of headless content management with developer-focused features for project flexibility and control.
Payload CMS: Scalable Headless CMS for Developers
Discover how Payload CMS combines the power of headless content management with developer-focused features for project flexibility and control. Payload is an open-source, fullstack CMS and app framework built in TypeScript that installs directly into your Next.js /app folder.
What is Payload CMS?
Payload is an open-source, fullstack CMS and application framework built entirely in TypeScript. It installs directly into your Next.js /app folder, gives you a REST and GraphQL API, and generates a fully customizable admin panel - all from a single config file in your codebase.
Most headless CMS platforms are hosted services. You get an API, a managed admin, and a pricing tier that someone else controls. Payload is MIT licensed, self-hosted, and lives in your codebase like any other part of your application. Collections and access rules are just TypeScript config. Your admin UI is a React app you can override at the component level.
How to Install Payload CMS
The fastest way to get started is create-payload-app. One command creates a full Next.js project with Payload already wired in: npx create-payload-app@latest. The CLI asks three things: project name, database adapter (MongoDB, PostgreSQL, or SQLite), and a starter template.
Payload CMS Features
1. Custom Fields and Content Modeling: Payload CMS ships with around 20 field types out of the box: text, richText, number, date, select, relationship, array, blocks, and more. The blocks field lets editors build pages from a predefined set of components.
2. Drafts and Version Control: Payload separates the act of saving from the act of publishing. Draft mode gives editors a working copy that never affects the live document. Autosave keeps progress safe in the background.
3. Access Control: Access control in Payload is a function, not a settings page. You define who can read, create, update, or delete at the collection level, the document level, or the individual field level.
4. Localization: Localization is configured once at the top level of payload.config.ts, then each field opts in with localized: true. Payload handles storing separate values per locale.
5. Live Preview: Live preview is built in. Point it at your frontend URL and editors see their changes rendered in real time before publishing.
Payload CMS Pricing and License
The core is MIT licensed and free. No usage limits, no seat pricing, no API call quotas. You run it on your own infrastructure and the only costs are hosting, database, and file storage. Payload Cloud was discontinued for new projects after the Figma acquisition in 2025. Self-hosting is now the only path.
AI and MCP
Payload now has an official MCP plugin that enables advanced agentic CMS workflows: autonomous content chains via hooks, RAG embeddings in your DB, local LLM support. AI agents (Claude, Cursor, or any MCP-compatible client) can read, create, and update content in your CMS directly, without custom integrations layer.
When to Choose Payload CMS
Payload fits best when the project has a developer on it and data ownership actually matters. It's ideal for SaaS products and internal tools where the admin panel is a React app, eCommerce content layers, regulated industries (healthcare, finance), and existing Next.js projects. Skip it if there's no developer available for the initial setup, or if editors need to manage schema changes themselves.
