
A headless CMS is a content management system that keeps and organises your content but has no built-in website to show it on. That missing website is the "head". Instead, the CMS sends your text, images and product details through an API to each front end a developer builds. That can be a website, an app or a screen in a shop.
In a traditional content management system (CMS), the content and the pages that display it are built and run as one system. A headless CMS separates them, which gives developers more freedom but also more work.
Headless CMS vs traditional CMS: what's the difference?
A traditional CMS comes with its own front end, while a headless CMS keeps only the back end and leaves the front end to developers. The back end is the part where you write and store your content. The front end is what your visitors see and use, the templates and pages of your website. In a traditional CMS the two are tied together, so a page you write appears on your website in your theme's design.
| Traditional CMS | Headless CMS | |
|---|---|---|
| Front end | Built in, with themes or templates | None: developers build their own |
| Channels content can reach | Usually one, often only the website the CMS runs | As many as you need: any website, app or device that can read the API |
| Who builds the pages | You, with themes and plugins | Developers, in the framework they choose |
| Editing | You edit pages and see them as visitors will | You fill in structured content fields |
| Good for | One website you run yourself | Several channels fed from one place |
Is a decoupled CMS the same as a headless CMS?
Not quite. A decoupled CMS also keeps the content apart from the way it's displayed and can deliver it through an API. But it still comes with a front end you can use if you want to, and a headless CMS has no front end at all. Because both separate the back end from the front end, people often use the two terms as if they meant the same thing.
How does a headless CMS work?
Your content passes through three parts on its way to your visitors.
- The content store. This is where your team writes, edits and organises content. It's saved in structured fields, such as a product name and a description, rather than as finished pages.
- The API. An API (application programming interface) is a set of rules that lets one piece of software work with another. The front end asks the CMS for content, and the CMS sends it back as plain data with no design attached.
- The front ends. Each website, app or other channel takes that data and decides how it looks. Your website might show a full product description, for example, while a screen in your shop shows only the name.
Because the content isn't tied to one layout, you write it once and use it wherever you need it. Change a product description in the CMS, and the new text appears in both your online shop and your app. Each one shows it in its own design. Nobody has to copy and paste it from one system to the next.
What are the benefits of a headless CMS?
Keeping content apart from its presentation gives you more freedom in how and where you publish.
- You can add new channels without moving content. When you add an app or a new device later, developers connect it to the same API, and your existing content stays where it is.
- Developers can build the front end with the frameworks and tools they know best, instead of the templates a CMS comes with.
- Each front end can be designed for its own screen, so the user experience in your app doesn't have to copy your website.
- Content and design change separately. A new website design leaves the content alone, so you don't have to rewrite or move it when the look changes.
What are the drawbacks of a headless CMS?
The freedom comes at a price, mostly in development work.
- You need developers. Every front end has to be built and maintained by someone who codes, so without one a headless CMS has nowhere to show your content.
- Editors lose the visual view. The content fields show no finished page, so a live preview has to be built before they can see how their work looks.
- Adding a new type of page or component can mean waiting for a developer. In a traditional CMS, you can build new pages yourself from the templates it comes with, within the limits of what those templates offer.
- The CMS and each front end need their own hosting, updates and security. Besides any fee for the CMS itself, you pay for hosting each front end and for the developer time to build and maintain it.
Should you choose a headless CMS or a traditional CMS?
Choose a headless CMS when the same content has to appear in several places, such as a website, an app and screens in your shop. You also need developers to build and look after each front end. That means a business with its own development team or with an outside agency.
If you're unsure, list the places your content has to appear in the next year or two. Google Analytics shows which devices your visitors use today. Visitors on phones still open the same website, so they don't add a channel.
Our advice: if that list holds only your website and you update it yourself, choose a traditional CMS or a website builder. You get the design, the editing and the publishing in one place.
You don't need coding skills to build your website with us, and every plan includes hosting and professional email.
Build my websiteIf your website is the only place your content needs to go, build your website with our website builder and publish it without a developer.
If your website is the only place your content needs to go, build your website with our website builder, keep your content and design in one place and publish it without a developer.
Frequently asked questions
Is WordPress a headless CMS?
Not by default. WordPress is a traditional CMS that stores your content and displays it with a theme. It also has an API, the REST API, that lets other applications read and update its content. That way, developers can run WordPress as a headless CMS with a separate front end.
What are some examples of a headless CMS?
Examples include Strapi and Hygraph. Strapi is an open-source headless CMS, so its code is public and developers can inspect and extend it. Before you choose one, compare how each is hosted and what the whole setup costs, not only the fee for the CMS.
Recommended reading
HostingNov 6, 2026504 Gateway Timeout: what it means and how to fix it
A 504 Gateway Timeout means a server in between got no answer from the website in time. See whose fault a 504 error is and how to fix it, WordPress included.
HostingAug 4, 2026What is website cache?
What does cache mean? And how to clear your cache? Read the importance of cache and why it's necessary to clear your cache once in a while.
HostingAug 4, 2026What is SSH?
How does SSH work & what does it do? Learn about the history of Secure Shell's predecessor Telnet and how SSH improved our internet security in this article.
