Headless CMS definition
A headless CMS is a content management system that stores and manages content but has no built-in frontend for displaying it. Content is delivered through an API, usually REST or GraphQL, to any channel: a website, mobile app, smart display or kiosk. Developers choose the presentation layer, while editors keep a familiar editing interface.
How does a headless CMS work?
Content is modeled as structured types, such as article, product, author or FAQ, each with defined fields. Editors create and publish entries in a web interface, and the CMS stores them as data rather than as finished pages. A frontend built with Next.js, Astro, a mobile framework or anything else fetches that content through an API, either at build time or on each request, and decides how it looks.
The "head" in the name is the presentation layer. A traditional CMS like classic WordPress couples templates, plugins and the database in one system that renders pages. A headless CMS removes that layer. Webhooks notify the frontend when content changes so it can rebuild or refresh, and images are usually served from a CDN with on-the-fly resizing.
Headless CMS vs traditional CMS
A traditional CMS is page-centric: editors control layout through themes and page builders, preview is instant, and plugins add features quickly. A headless CMS is content-centric: the same content feeds many channels, developers can use any framework, and the public site exposes no admin or database. The trade-offs are more moving parts, a dependency on developers for layout changes, and preview that has to be set up deliberately.
Middle paths exist. WordPress and Drupal can both run headless through their APIs, and visual headless platforms let editors arrange components on a page while the content underneath stays structured and reusable across channels. This suits teams that want structure without giving up visual control.
Popular headless CMS platforms
- Contentful: mature SaaS platform popular with enterprises.
- Sanity: highly customizable editing studio with real-time collaboration.
- Strapi: open-source and self-hostable, built on Node.js.
- Storyblok: headless with a visual page editor for marketers.
- Payload and Directus: open-source options that sit close to your own database.
- Hygraph: GraphQL-native content federation.
- Prismic: reusable page slices that marketers can arrange themselves.
- Kontent.ai and Contentstack: enterprise platforms with governance features.
- Headless WordPress via the REST API or WPGraphQL.
Example: one content source, many channels
A retail brand stores product stories, size guides and promotions in a headless CMS. The website, the iOS and Android apps and the in-store screens all pull the same entries through the API, each rendering them in its own layout. When the marketing team updates a promotion, every channel changes together, and translations flow through one localization workflow instead of three separate ones. Editors schedule campaigns once instead of updating each channel by hand.
How to choose and implement a headless CMS
Start with the content model, not the vendor. Map the content types, fields, relationships and languages you need, then test candidates against real editor tasks. Check roles and approval workflows, preview support, localization, API rate limits, pricing by users or records, and whether you need to self-host for data residency. Nexzem designs the content model with editors before building, which prevents the most common headless failure: a flexible API that editors find hard to use.