On this page 11 sections

A headless CMS is a content management system that stores and manages your content but has no built-in website attached. The content is sent to whatever needs it, such as a website, a phone app or a screen in a shop, through a connection called an API.
TechTarget describes it as a system where the content layer is decoupled from the presentation layer (opens in a new window). The "head" is the part that shows the content to people. "Headless" means that part has been cut off and built separately.
Short answer
- Traditional CMS: one system that holds your content and also builds the pages.
- Headless CMS: a system that only holds and manages the content. A separate front end shows it.
- The benefit is freedom: one set of content for many places, and a front end built the way you want.
- The cost is extra build work and more parts to look after.
- Most small business sites do not need one.
Start with a normal CMS
If the term CMS is new, read what a CMS is. In a traditional CMS, the editing screen and the public website live in one package. You edit, the system builds the page and its look is controlled by themes and templates.
TechTarget notes that a traditional CMS contains everything needed to create, publish and manage content, including the database and the presentation layer (opens in a new window).
What "headless" changes
In a headless set-up, the content is separated from how it is shown.
- Editors write and manage the content in the CMS, which stores it in a structured form: fields such as title, summary, price and image.
- The CMS makes that content available through an API, a defined way for other software to ask for it.
- A separate front end, such as a website or an app, asks for the content and shows it however it likes.
Think of recipe cards. A normal CMS is a restaurant that writes its recipes on its own menu board. A headless CMS is a box of recipe cards: the same cards can serve the dining room, the takeaway window and the delivery bag.
Why people choose headless
- One content store, many outputs. The same content can feed a website, an app, an in-store screen or an email.
- A front end built the way you want. Designers and developers are not limited by a theme or a template system.
- Different teams work in parallel. Editors work on content while developers work on the front end.
- Performance and control. The front end can be built to load only what it needs.
Where headless costs more
- More to build. Someone has to build the front end that a traditional CMS gives you ready-made.
- More to look after. There are at least two parts: the content system and the front end, each with its own hosting and updates.
- Editing previews are not automatic. Seeing a page as it will look before you publish may need to be built.
- It needs developer skills to change anything beyond the content.
Headless, decoupled and hybrid
These terms overlap. TechTarget explains that a decoupled CMS (opens in a new window) offers more flexibility for mixed use, sitting between a fully headless set-up and a traditional interface. A hybrid CMS combines headless features with visual editing tools (opens in a new window). The names vary between sellers, so ask what each option actually includes.
Do you need a headless CMS?
It is worth considering if:
- the same content must appear in several places, such as a website and a mobile app;
- you need a highly custom front end;
- developers will be building and maintaining the front end for a long time;
- you want to be free to change the front end later without moving your content.
It is probably more than you need if:
- you have a brochure site, a small blog or a few service pages;
- you want to see changes as they will look, exactly as you edit them;
- the budget is limited.
For most small business sites, a traditional CMS such as WordPress or a custom editor gives you more for the money. We compare them in WordPress vs a custom website. How pages get made, in advance or on request, is a separate question: see static vs dynamic websites.
What to ask a developer
- Why does this project need headless rather than a traditional CMS?
- Who builds and hosts the front end, and who looks after it?
- How will editors preview their work before publishing?
- What happens if we want to switch the CMS or the front end later?
- What will it cost to run each year, not just to build?
A simple example
Imagine a shop. The product data (name, description, price, photos) lives in the CMS. A website shows it on product pages. A phone app shows the same products. A screen in the shop shows today's offers from the same data. Change a price once in the CMS and every output can use the new price. That is the idea behind headless.
Common misunderstandings
- "Headless means no website." It means the website is separate from the content system. You still have a website.
- "Headless is the modern replacement for every CMS." It suits some projects. For many small sites a traditional system is simpler and cheaper to run.
- "Headless is automatically faster." It can be, but speed depends on how the front end is built.
- "Editors lose their tools." They keep the editing screen. They may lose the instant preview of the finished page unless it is built for them.
How we can help
If you are weighing the options, we can explain what each would mean for your project and build the pieces you choose. See our web development and software development services, or get in touch.
Facts checked on 20 November 2026. Sources: TechTarget: headless CMS (opens in a new window), TechTarget: definition (opens in a new window), Wikipedia: Headless content management system (opens in a new window).