A headless CMS is a content management system with no presentation layer ("head"): it stores content and delivers it through APIs to any site, app or device.
The difference from a traditional CMS
In a traditional CMS like WordPress, content and presentation are tied together. In a headless CMS the "head" — the front-end that renders pages — is detached: the CMS only manages the data and delivers it through an API. The site or app that displays it is built separately.
Benefits of the headless approach
- Multi-channel: the same content feeds a website, a mobile app and other channels.
- Performance: the front-end can use modern, fast technology with a framework of your choice.
- Security: separating the layers reduces the attack surface.
When it makes sense
Headless is worthwhile when you publish the same content across several platforms or want maximum technical freedom on the front-end. For a simple brochure site it is often overkill. If you're unsure which approach fits, our web development service weighs the costs and benefits with you.
Related terms: CMSAPIFramework
Frequently asked questions
What is the difference between a CMS and a headless CMS?
A traditional CMS combines content and presentation; a headless CMS manages only content and delivers it via API, leaving presentation to a separate, freely chosen front-end.
Examples of headless CMS?
Well-known ones include Strapi, Contentful, Sanity and Storyblok. WordPress can also run in headless mode using its APIs.
Is a headless CMS harder to manage?
Editing content stays simple, but building and maintaining the separate front-end needs more technical skill. That is why it suits structured projects best.