What is a headless CMS?
API-delivered content, where rendering lives, and decision criteria before you pick a platform.
A headless CMS stores and serves structured content over APIs (REST, GraphQL, or vendor-specific query languages) without mandating how the public site looks.
Why teams adopt it
- One content hub for web, apps, email, and partners
- Framework freedom — Astro, Next.js, mobile clients
- Clear separation between editors and front-end releases
Tradeoffs
| Benefit | Cost |
|---|---|
| Portable front ends | You operate two systems (CMS + site) |
| Strong modeling | Up-front schema design required |
| Preview flexibility | Preview/auth wiring is custom work |
Headless is not always the answer
Marketing microsites with a single WordPress theme may be simpler on a coupled CMS. Headless shines when multiple channels or strict engineering standards justify the split.
Compare platforms
Read Best headless CMS for criteria, then our platform reviews.