What is a headless CMS? A plain-english guide
A headless CMS splits a website in two: a content store on one side, and whatever front end you like on the other, connected by an API. It is powerful and increasingly popular — and overkill for most business sites. Here is what it is, in plain English, and when it earns its complexity.
By the Media On Tap editorial team · Published 10 September 2026 · Updated 10 September 2026
“Headless” sounds dramatic; the idea is simple. A traditional CMS manages both your content and how it is displayed, together. A headless CMS keeps only the content — the “body” — and removes the display layer — the “head” — delivering content via an API to whatever front end you choose. Hence headless: a content backend with no fixed front end attached.
What a headless CMS is
A headless CMS is a content management backend that stores and organises your content and makes it available through an API, rather than rendering web pages itself. Developers then build the front end separately — a website, a mobile app, a digital display, whatever — and pull the content in. The content is written and managed in one place and can be delivered to many destinations. It decouples what your content is from where and how it appears.
Headless vs traditional CMS
The difference is coupling. A traditional CMS like WordPress is coupled: content and presentation live together, so it produces a website out of the box, which is simpler and needs less technical work. A headless CMS is decoupled: it handles content only, giving you total freedom over the front end but requiring developers to build and connect that front end. Coupled is easier and complete; headless is more flexible and more work. Note that some traditional systems, including WordPress, can also be used in a “headless” way — see WordPress vs headless for that specific decision.
Pros and cons
Where headless shines
- Total front-end freedom — build with any technology
- Deliver the same content to many channels (web, app, more)
- Potential for excellent performance with a modern front end
- Clean separation of content and presentation for large teams
Where it costs you
- Much more complex — needs developers to build the front end
- Higher cost and longer build than a ready-made CMS
- No out-of-the-box website — more to assemble and maintain
- Overkill for a standard business website
Examples
Well-known headless CMS platforms include Contentful, Sanity, Strapi and Storyblok, among others. They differ in detail — some are hosted services, some open-source and self-hosted — but share the same model: manage content centrally, deliver it by API. As with any fast-moving category, check current capabilities and pricing before choosing one; the right pick depends on your team and requirements.
When to use one
Be honest about whether you need it. A headless CMS earns its complexity when you are delivering content to multiple channels beyond a website, when you want a bespoke, high-performance front end built by developers, or when a large content operation benefits from that clean separation. For a standard business website — a brochure, a service site, a typical store — it is usually more complexity, cost and maintenance than the job warrants, and a traditional CMS serves better. Match the tool to the need, not the trend.
Not sure whether headless is right for you? We’ll give you a straight answer — most business sites do not need it — and build the right thing either way. Our website design and development service is fixed price; get a fixed-price quote.
Frequently asked questions
A headless CMS is a content management backend that stores and organises content and delivers it through an API, without rendering web pages itself. Developers build the front end (a website, app or other channel) separately and pull the content in. It decouples what your content is from where and how it appears — the ‘head’ (the display layer) is removed, leaving just the content ‘body’.
A traditional CMS like WordPress is coupled — content and presentation together — so it produces a website out of the box, which is simpler. A headless CMS is decoupled — content only, delivered by API — giving total front-end freedom but requiring developers to build and connect that front end. Coupled is easier and complete; headless is more flexible and more work. Most business sites are well served by a traditional CMS.
WordPress is a traditional (coupled) CMS by default, producing a website out of the box. However, it can also be used in a ‘headless’ way — using WordPress purely as a content backend via its API, with a separate custom front end. So WordPress is not inherently headless, but it can be run headless when a project genuinely needs it. Our WordPress vs headless guide covers when that trade-off makes sense.
When you are delivering content to multiple channels beyond a single website, when you want a bespoke, high-performance front end built by developers, or when a large content operation benefits from cleanly separating content from presentation. For a standard business website — a brochure, service site or typical store — a headless CMS is usually more complexity, cost and maintenance than the job needs; a traditional CMS is the better fit.
Well-known headless CMS platforms include Contentful, Sanity, Strapi and Storyblok, among others — some hosted services, some open-source and self-hosted. They share the same model: manage content centrally and deliver it via API to any front end. They differ in detail and pricing, and the category moves quickly, so check current capabilities before choosing; the right one depends on your team and requirements.
Go deeper on the decision
The platform guides and the framework behind this comparison.
WordPress vs headless
The specific WordPress-vs-headless decision, in full.
Read the guide LearnWhat is a CMS?
The traditional content management systems headless is an alternative to.
Read the guide Platform guideWordPress website design
The coupled CMS most businesses use.
Read the guide DecideHow to choose a website platform
Match the approach to your business.
Read the guide