A headless CMS is a content management system that stores and serves structured content through an API, leaving the front end entirely to a separate application. The name 'headless' is literal — a traditional CMS like WordPress ships both the database and the website templates together; a headless CMS ships only the database and a content API. Editors log in, write articles, upload images; developers consume that content through REST or GraphQL and render it however they like. Contentful, Sanity, Storyblok, Prismic, and Strapi are the common choices in 2026; WordPress itself can be run headlessly. Headless CMSes pair naturally with Next.js, Astro, and similar modern frameworks, because the framework can pull content at build time, generate static pages, and still let non-technical editors update the site without touching code. The trade-off is setup complexity — a headless CMS is more machinery to stand up than a brochure-site markdown file.
When I use one and when I skip it
For a small marketing site — five to ten pages, not updated weekly — I usually skip the headless CMS and keep content in typed TypeScript files inside the repository. The editor is the IDE, pull requests are the approval flow, and the client saves £200 to £400 a year in CMS fees. For a content-heavy site — a blog with a new post every week, multiple editors — Sanity or Contentful is worth standing up from day one.
Why most small businesses do not need one
Most small businesses do not actually need a CMS. The client who 'wants to update the site themselves' updates the site twice in the first month and never again. A headless CMS is the right answer when multiple people publish on a schedule. For anyone else, it is overhead that adds monthly cost, complicates handover, and slows the build for no visible benefit to the end visitor.
Related terms
Bespoke, live in seven days.
£1,000 flat. Paid upfront. Full refund if I miss day seven. Code, hosting, and domain all in your name.