← Glossary·Web tech

Headless CMS

A content management system that exposes content via API instead of rendering its own pages. Decouples editing from presentation.

A headless CMS is a content store with an admin UI for editors and an API (REST or GraphQL) for developers — but no built-in front end. Sites built on a headless CMS pull content via API and render it in their own framework, free to design the frontend however they want.

The trade-off versus an integrated CMS like WordPress is engineering effort. A headless setup demands a separate build, a separate deploy, and a separate frontend codebase — which is the right answer when the content team is small and design quality matters, and the wrong answer when the team is large and content velocity is the constraint.

For studio work, headless CMSes (Contentful, Sanity, Notion, Airtable used as CMS) usually outperform monolithic systems because the resulting site is statically generated, image-optimized, and styled exactly to the brand — none of which are WordPress’s defaults.