Storyblok review: headless CMS with a real visual editor

What Storyblok is, and who it is for

Storyblok solves a problem that sits next to, but is not the same as, the one most libraries here address. Its users are your own content team, not your customers, and its job is to let them edit a site that your developers built without either side compromising: content stays typed and validated, and editing still feels like pointing at the page.

The mechanism is a live preview. Your front end runs inside the Storyblok app, a bridge script connects DOM elements to content entries, and clicking a section opens its fields. Editors are looking at the real site — the same code that serves production — rather than a form or an approximation.

If your requirement is an editor your customers use inside your product, this is the wrong category and an embeddable library is the right one. If your requirement is a marketing site your content team owns, Storyblok is one of the strongest options in this dataset.

Architecture

Content is modelled as typed components ("bloks") with defined fields. Your front end registers matching components, fetches content through the API, and renders it. The visual editor overlays that rendered output with selection affordances.

The consequence developers care about: layout is a function of the components you ship. An editor cannot invent a three-column section that does not exist in code, and cannot change padding on a whim. Whether that is a feature or a limitation depends entirely on who is asking — content teams occasionally find it constraining, and design systems survive it.

Pricing attaching to a space rather than to an account is an architectural fact as much as a commercial one: agencies running many client projects should model that before comparing headline prices with per-account competitors.

How we assessed it

We have not run Storyblok hands-on under our test procedure, so this page carries no score and no code sample, per our methodology. Registry metadata confirms the React SDK's licence, publication history and current version; pricing and capabilities come from the vendor's published pages with the date we checked them. Prices are quoted in euros by the vendor, so our dataset records paid_from_usd as null rather than converting at a rate that would be wrong tomorrow.

Strengths

Visual editing without giving up structure. The main reason teams choose it over a page builder: content remains typed, queryable and reusable across surfaces.

Genuinely framework-agnostic delivery. First-party SDKs for React and Vue, community support elsewhere, and content delivered as data so any renderer works.

Strong internationalisation. Multi-language workflow is built in rather than modelled by hand, which is unusual and valuable.

A mature app. Roles, workflow, asset handling and versioning are all present, which is what separates a CMS from a content API.

Editors like it. Adoption by non-technical teams is the metric that decides whether a CMS project succeeds, and this is where Storyblok consistently does well.

Limitations

Per-space pricing punishes multi-project teams. An agency with ten client sites is buying ten subscriptions. Model that before comparing with per-account products.

Not free-form. Editors cannot restyle; they fill fields in components you built. For a marketing team used to Webflow, that is a real adjustment.

Not embeddable in your product. Storyblok's editor is Storyblok's product.

Hosted only. Content lives with the vendor, which is a hard stop for some procurement processes.

Preview setup is real work. The bridge, preview URLs and draft handling need doing properly, and a half-finished preview integration undermines the entire value proposition.

Pricing

Vendor-published: free Starter with one seat; Growth around €99 per month with five seats; Growth Plus around €349 per month; Elite by quote. Monthly billing costs roughly 20% more than annual, and each space is billed separately.

Compare with Contentful Studio if you are already in the Contentful ecosystem, with Sanity if you want the studio itself in your repository, and with Puck if what you actually need is an editor inside your own application rather than a CMS.

Questions to ask before you buy

1. How many spaces will we actually need? Pricing attaches per space, so this question determines your cost more than the tier does.
2. What does the preview integration require from our front end? Get the specifics before estimating, because a partial preview undermines the product's whole value.
3. How are component schema changes handled for existing content? Ask about removing a field from a component used by a thousand stories.
4. What are the API request and bandwidth allowances, and what happens beyond them?
5. How does the translation workflow behave with our language set? Multi-language is a strength here, but the workflow shape matters.
6. What does an export look like if we leave? Structured content exports better than most formats; confirm it includes assets and references.

Where it sits in this dataset

Storyblok is the CMS in this dataset that comes closest to feeling like a page builder without becoming one. Editors compose from components and see a live preview; they cannot restyle. For a marketing team that is either exactly right or exactly wrong, and knowing which before you buy is most of the evaluation.

Against Contentful Studio its advantage is straightforward: published pricing and visual editing in every tier, against a quote-only add-on. Against Sanity, the difference is philosophy — Storyblok gives you a polished hosted app, Sanity gives you a studio in your repository. Against Directus, it is hosted-and-content-shaped against self-hosted-and-database-shaped.

And against Puck: if the editor needs to be inside your own product for your own customers, no CMS in this group qualifies, and that is the distinction most shortlists get wrong.