Headless CMS: what it is and who it is for
What a headless content management system does differently, when a business benefits from one, and when content as files in the repository is the better choice.
The short answer
A headless content management system stores and edits content but does not render pages. Editors work in its interface, the content is delivered through an API, and your website, built separately, fetches it and renders the pages itself, either at build time into static files or on demand. The separation means the site’s code is free of the CMS, several sites or apps can draw on the same content, and the CMS can be swapped without rebuilding the site. It suits organisations with several editors, frequent publishing, editorial workflow or content shared across channels. For a small business whose site changes a few times a month, content as structured files in the repository, edited through previews, is simpler, free and just as fast. The choice comes down to who edits, how often, and in how many places the content appears.
Three ways to manage content
| Approach | Where content lives | Who edits and how | Cost | Suits |
|---|---|---|---|---|
| Files in the repository | Structured files versioned with the code | A small team through an editor or a lightweight interface, with previews | Free | Small sites, occasional edits, technical comfort or a partner |
| Headless CMS | A content service accessed through an API | Editors in a familiar interface with roles, scheduling and workflow, with previews | Subscription | Several editors, frequent publishing, content across sites and apps |
| Traditional CMS | A database inside the site platform | Editors in the platform’s admin, which also renders pages | Hosting plus maintenance | Sites built on that platform; brings its own maintenance and security surface |
When a headless CMS earns its place
- Several editors who need roles, permissions and an interface they recognise.
- Frequent publishing, daily or many times a week, where the editing experience matters.
- Editorial workflow: drafts, review, approval, scheduling.
- Content in several places: the website, an app, a partner site, a kiosk, all from one source.
- Localisation at scale, with translators working in the tool.
- Non-technical ownership of content is a hard requirement and a partner-mediated file workflow is not acceptable.
What stays the same either way
The site is static and fast, built by a pipeline, served from an edge network. Previews exist for every change. Content is structured, not free-form. The code is in your repository and the accounts are in your name. Whether the content comes from files or from a CMS is an implementation choice behind that, and a site built properly can move from one to the other later when the team changes.
What this means for you
A headless CMS separates editing from rendering: editors get a proper interface and workflow, the site stays static and fast, and the content can feed more than one place. It is worth its subscription for teams that publish often or in several channels, and unnecessary for small sites with occasional edits, where files in the repository do the job. Decide by team size and rhythm, and keep the site built so the choice can change later.
Frequently asked questions
What does headless mean?
The head is the part that renders pages. A traditional CMS does both storage and rendering; a headless one only stores and edits content and hands it over through an API. Your website, built separately, fetches that content and renders it with its own code. The CMS is invisible to visitors and can be swapped without rebuilding the site.
Is a headless CMS better than editing files?
Different, not better. Files in the repository are versioned, free, and edited through previews with structured fields; they suit a small team editing a few times a month. A headless CMS adds an editing interface non-technical people find familiar, roles and permissions, scheduling and workflow, and the ability to feed several sites or apps. It costs a subscription and one more system. The size of the editing team and the publishing rhythm decide.
Will editors still get previews?
Yes. A well-integrated headless CMS shows a draft on the real site before publishing, through preview deployments or a preview mode, and publishing triggers a rebuild or a cache update so the change goes live in minutes. Editors work in the CMS; the site stays static and fast.