A headless CMS is a content management system without its own front end. Editors still log in, write pages and upload images, but instead of the CMS rendering a website, it hands the content out through an API to whatever site, app or display a developer builds.
How content travels from editor to page
First a developer defines content models: a "Service" might have a title, price, description and photo; a "Location" has an address and opening hours. Editors fill in entries through a web dashboard. The website, built separately in a framework such as Next.js or Astro, requests those entries via a REST or GraphQL API, either at build time or on each request, and decides how they look. When an editor publishes, the CMS can fire a webhook so the site rebuilds or refreshes its cache.
The "head" in the name is the presentation layer. A traditional CMS like WordPress (in its classic setup) keeps body and head together, with themes deciding the look. Headless cuts them apart.
Products and a worked example
Contentful, Sanity, Storyblok, Strapi, Hygraph and Payload are widely used headless systems; WordPress can also run headless through its REST API. Example: a fitness chain wants class timetables on its website, its mobile app and the screens in each gym lobby. Staff update the timetable once in the headless CMS, and all three read from the same API, so the lobby screen never disagrees with the app.
Does your business need one?
Honestly, most single-location businesses do not. Headless pays off when the same content feeds several channels, when developers want full control of the front end, or alongside a Jamstack build. It costs more up front because someone has to build and maintain the front end, and editors lose the "what you see is what you get" page preview unless it is set up deliberately.
Where headless projects stumble
- No live preview. Editors publish blind and discover layout problems on the live site.
- Over-modelled content. Dozens of tiny fields make simple edits tedious.
- Forgetting SEO fields. Titles, meta descriptions and alt text must be modelled explicitly; nothing adds them for you.
- Free-tier limits on users, records or API calls hit just as the site grows.
Related terms
- CMS: the coupled, all-in-one model.
- API: how a headless CMS delivers content.
- Static site generator: a common consumer of headless content.
- Jamstack: the architecture headless CMSs grew up with.