Most explanations of a headless CMS are written by companies trying to sell you one, which is why they tend to be either baffling or breathless. I build on this stuff for a living, so here is the version I would give a business owner over a coffee. No jargon, no sales pitch.
The short version
A headless CMS is a place to keep your content that does not care how the content gets shown. The content lives in one system. Your website, your app, a screen in a shop, all of it pulls the content from that system through an interface called an API. The word headless just means the content store has been separated from the front end, the part people actually see. Traditional systems like WordPress glue the two together. Headless splits them apart on purpose.
The bit that trips people up
The confusion usually comes from the word content. In a normal website builder, when you edit a page you are editing the page itself, the words and the layout and the look, all in one go. In a headless setup you edit the content as plain, structured information. A blog post is a title, a body, an author and a date. Where those bits appear and what they look like is decided somewhere else, by the front end. It feels odd at first because you cannot see the finished page while you type. The payoff is that the same blog post can appear on your website, in a newsletter and in an app without you writing it three times.
A worked example
Say you run a shop with a website and a mobile app. With a traditional CMS your product descriptions live inside the website. If you want them in the app as well, someone copies them across, and now you have two copies to keep in step. With a headless CMS the description lives in one place. The website asks for it, the app asks for it, and both get the same thing. Change it once and it changes everywhere. For a business with content in more than one place, that single source is the whole point.
What you gain
- One source of truth for your content, so nothing drifts out of date in one place while it is fixed in another.
- Freedom to rebuild the front end without touching the content, which matters a lot when a redesign comes round.
- Usually faster pages, because the front end can be built lean instead of carrying a heavy template engine.
- Fewer easy ways in for attackers, because there is no public login page bolted straight onto your database the way there is with a standard install.
What it costs you
None of this is free. A headless setup needs a front end built by a developer, because it does not arrive with a ready made theme you can switch on. There is more to wire up at the start. For a simple brochure site that is never going to change much, that extra effort buys you very little, and I will happily tell a client so. I have written before on whether a headless CMS is overkill for a small business, and the honest answer is that for a lot of them it is.
How it compares to WordPress
WordPress is the thing most people are moving from, so it is the fair comparison. WordPress can be run headless too, but out of the box it is the classic joined up system, content and presentation in one. That is why it is so quick to get going and why so many small businesses are on it. Headless earns its keep when you have grown past a single website, when speed genuinely affects sales, or when your content needs to feed several places at once. I have written a longer piece on headless CMS versus WordPress for a small business if you want the side by side.
So do you need one
Here is my honest take after building on plenty of these. A headless CMS is a tool, not an upgrade. If your content only ever appears on one website that rarely changes, a traditional system is probably the right call and you should not feel behind for using one. If you are running content across a website and an app, if page speed is costing you sales, or if you keep hitting the ceiling of what your current setup can do, then headless is worth a proper look. If you want to talk it through against what you have now, the platforms page lays out how I think about the choice, and services covers how I actually help people make the move.