Headless CMS
Headless CMS is a content management system that separates content storage and editing from the application that presents it. Content is delivered through APIs to a website, app or other channel. This allows reuse across experiences while giving the team responsibility for implementing and maintaining the front end.
Also known as: API-first CMS, decoupled CMS, content platform
Last reviewed
Why headless matters
The traditional CMS assumed one destination: a website it also rendered. Content and presentation were tied together in themes and templates, which was efficient until an organisation needed the same content somewhere else.
Going headless separates the two. The content model describes what a thing is — a product, a case study, a webinar session — rather than how it looks, and any number of front ends read it over an API. That reuse is the main commercial argument. The secondary argument is freedom: a front end can evolve independently of the CMS's templates.
The trade is ownership. Nobody ships you a new theme, so every layout is something a developer built and somebody has to maintain it.
How a headless CMS works
Editors work in an admin interface backed by a content model that a developer defined: collections, fields, validation and relationships. Saving a document writes to a database and makes it available over a REST or GraphQL API.
A separate application then requests that content and renders pages, usually server-side for search visibility, and often caches the result. The two halves can deploy independently, although a redesign that changes content structure may still require a migration.
Platforms differ mainly in two ways: whether they are hosted for you or run in your own infrastructure, and whether the content model is defined in a web interface or in code in your repository. Code-defined schema is reviewable in pull requests and reproducible across environments.
Headless CMS vs WordPress
WordPress bundles storage and rendering, and its ecosystem of plugins and themes is the reason it is often the cheaper correct answer for a marketing site. Its content model is built around posts and pages, extended with custom fields.
A headless API can serve different front-end languages. Many platforms have plugins and integrations, and WordPress itself supports custom post types and a headless REST API setup. The differences that decide it:
- Rendering. WordPress produces the pages itself; a headless CMS hands content to a front end you build.
- Content model. Compare support for your content types, relationships and validation rather than assuming one system can only store pages.
- Extending it. Both approaches may use plugins, integrations and custom development.
- Editing. Near-total layout freedom in a page builder, against the fields a developer defined.
WordPress can be run headless through its REST API, including custom content types configured for API access.
When you need one
Choose headless when content has more than one destination, when the front end is doing real work rather than presenting text, or when the content model is genuinely yours. Avoid it for a brochure site with no developer to maintain the front end. We rebuilt this site on Payload CMS for the schema-in-code property, and wrote up the comparison in why we love Payload CMS.
Further reading
Payload: plugins and extensions explains the underlying approach.
Headless CMS: common questions
A traditional CMS usually combines editing with page rendering. A headless CMS exposes content to a separate presentation layer. Some products support both approaches, including WordPress through its REST API.
Neither architecture guarantees better SEO. Ensure important content is crawlable, links and metadata work, pages perform well and changed URLs redirect appropriately. Migration quality matters more than the headless label.
Compare implementation, hosting, licences, support and ongoing changes. Some core products are free to self-host, while paid features and licence conditions differ. For example, Directus documents specific licence terms; do not assume every self-hosted platform is free for every organisation.
Want to talk about your project?
Tell us what you’re trying to achieve and we’ll map the fastest credible path.