Headless CMS in 2026: Sanity, Storyblok or something else?
Want to manage content without the WordPress headaches? A headless CMS is a powerful option — but not for everyone. Here's what it is, which options exist, and when I recommend it.
Whenever I explain to clients how I build their website, two questions always come up: “But how do I update text later?” and “Do I need to call a developer every time I want a new page?”
Those questions are fair. And they are precisely the reason headless CMS has become so popular over the past few years.
What is a headless CMS?
Traditional systems like WordPress combine two things: where your content is stored and how it looks on your website. Those two are tightly coupled.
A headless CMS separates them. The content lives in a standalone environment — a kind of intelligent database with a friendly admin panel. Your website fetches that content via an API and presents it in its own way.
The result: you can use the same piece of content on your website, in an app, in a newsletter, or in another language — without retyping it everywhere.
Why now?
Three years ago, headless CMS was largely a concern for large tech companies with development teams. That has changed.
Frameworks have matured. Astro, Next.js and SvelteKit are now mature enough that a freelancer can realistically use them for SME clients. Integrations with external CMS platforms are easier than ever.
AI is accelerating content production. More content, more languages, more variants — a headless system with structured content handles this far better than a WordPress page full of shortcodes.
Clients want more autonomy. They want to publish blog posts, update prices, add new team members — without calling a developer. A good headless CMS delivers that without sacrificing technical quality.
The main options
Sanity
Sanity is my personal favourite when I need to choose a CMS for a client. The reasons:
- Free up to a decent volume — the free tier is generous enough for most SME websites
- Fully customisable — you define your own content structure in code, so the CMS fits the project exactly
- Real-time collaboration — multiple people can edit content simultaneously, similar to Google Docs
- Portable text — a rich text editor that works with structured blocks rather than HTML spaghetti
- Strong ecosystem — native integrations with Astro, Next.js, Vercel and virtually every modern framework
The downside: Sanity is somewhat more technical to set up. You write schemas in JavaScript. For a client, the end result is great — for a developer, it takes a bit of time to learn.
Storyblok
Storyblok leans more towards the visual side. It has a live preview editor: you see directly on the page how your content looks as you edit it.
That’s a strong selling point for clients used to Elementor or the WordPress Gutenberg editor. It feels more familiar.
Storyblok works well for clients who regularly build new pages — landing pages, campaigns, news — without wanting to involve a developer. The component model is flexible and easy to learn.
The downside: pricing scales up faster than Sanity when usage grows.
Contentful
Contentful is the market leader, but targets larger organisations. The interface is mature and powerful, but the pricing reflects that: the free tier is limited, and serious usage quickly costs €300+ per month.
For most of the clients I work with, Contentful is overkill. But if you have a team managing content across multiple markets and languages, it’s a solid choice.
Directus and Strapi
Directus and Strapi are open-source alternatives you can self-host. That means: no monthly SaaS fees, but hosting and maintenance overhead.
For clients with sensitive data or those who simply don’t want recurring SaaS costs, this can be attractive. The interfaces have improved significantly in recent years — Directus in particular looks genuinely professional these days.
Downside: you’re responsible for updates, security and uptime. That requires a more technical client or a managed hosting solution.
Payload CMS
Payload is newer but growing quickly in popularity among developers. It’s fully TypeScript-native and combines CMS functionality with backend logic — you define your data models in code, and Payload automatically generates an API and admin panel.
If you’re building an Astro or Next.js project that also needs backend logic (forms, user management, e-commerce), Payload is a compelling option. It replaces both your CMS and your backend simultaneously.
When do I recommend a headless CMS?
Not always. Honesty matters here.
Yes, when:
- The client regularly publishes content (blog, news, vacancies, products)
- The website is built on Astro or Next.js
- Multiple people manage content
- The content is also used elsewhere (app, newsletter, social media tooling)
No, when:
- The website has few pages and rarely changes
- The client has little experience with digital tools and ease-of-use outweighs everything else
- The project is built in Webflow — Webflow has its own built-in CMS that works well for most cases
My preference in practice
For Astro projects where the client manages their own content: Sanity. The free tier is generous, the Astro integration is excellent, and the editor is perfectly usable for non-technical users after a short briefing.
For clients who want maximum visual control and are willing to pay a bit more: Storyblok.
For Webflow projects: Webflow CMS itself, unless there’s a specific reason to manage data outside of Webflow.
Conclusion
Headless CMS is no longer reserved for enterprise organisations. The tooling is mature, the integrations are solid, and the client experience — when set up properly — is comparable to WordPress.
It requires a deliberate choice and a bit more setup. But the gain is a website that is blazing fast, easy to maintain, and free from the usual WordPress headaches. Read more about how I approach this on my professional website page.
Curious whether a headless CMS suits your project? Get in touch — I’m happy to think through what’s the best choice for you. Or take a look at my web design services to see what I offer.
Related articles:
Web designer and developer from the Netherlands. I specialise in Webflow and Astro and help small businesses build websites that look great and rank well.
Get in touch
