# Storyblok review: headless CMS with a real visual editor

*Source: https://www.editorstack.cc/libraries/storyblok — last updated 2026-08-19. Licensed CC BY 4.0 with attribution to EditorStack.*


## Summary

- Storyblok is a headless CMS whose visual editor shows a live preview of your front end and lets editors click a component to edit its fields, so content stays structured while editing feels visual.
- Vendor-published pricing is quoted in euros — free Starter, Growth around €99 per month, Growth Plus around €349, quote-only Elite — and attaches to a space, so multiple projects mean multiple subscriptions.
- It is a tool for your content team, not an editor you ship to your customers: layout comes from components your developers build, and the editing UI is Storyblok's.

## Quick facts

| Fact | Value |
| --- | --- |
| Type | cms |
| Licence | Proprietary |
| First release | 2022-03 |
| Language | TypeScript |
| Frameworks | Any (framework-agnostic) |
| SSR support | full |
| Bundle (min+gzip) | Not measurable |
| Pricing | Free tier, paid plans undisclosed |
| npm weekly downloads | 106,460 |
| GitHub stars | 68 |
| Latest version | 7.3.1 |
| Last verified | 2026-08-19 |
| Drag & drop canvas | Partial |
| Responsive breakpoints | No |
| Visual style manager | No |
| Custom components | Yes |
| Data binding | Yes |
| E-commerce blocks | Partial |
| Email HTML export | No |
| AI generation | Yes |
| Editor i18n | Yes |
| White label | No |
| Self-hosted | No |

## 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](/categories/open-source-visual-editors) 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](/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](/compare/storyblok-vs-contentful-studio) if you are already in the
Contentful ecosystem, with [Sanity](/compare/storyblok-vs-sanity) if you want the studio itself in
your repository, and with [Puck](/compare/puck-vs-storyblok) 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](/compare/storyblok-vs-contentful-studio) its advantage is straightforward:
published pricing and visual editing in every tier, against a quote-only add-on. Against
[Sanity](/compare/storyblok-vs-sanity), the difference is philosophy — Storyblok gives you a polished
hosted app, Sanity gives you a studio in your repository. Against
[Directus](/compare/directus-vs-storyblok), it is hosted-and-content-shaped against
self-hosted-and-database-shaped.

And against [Puck](/compare/puck-vs-storyblok): 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.

## Who it fits, and who it does not

**Good fit**

- Marketing sites where a content team needs click-to-edit preview of a developer-built front end
- Multilingual content operations that need translation workflow alongside visual editing
- Teams that want structured, typed content rather than stored HTML

**Poor fit**

- Embedding an editor that your own customers use inside your product, which is not what a CMS visual editor is
- Free-form page design, since layout comes from components developers ship
- Organisations that must keep content on their own infrastructure


## Storyblok against its nearest neighbours

| Product | Type | Licence | Frameworks | Bundle (min+gzip) | Price from | Self-hosted | White label | Score |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [Storyblok](https://www.editorstack.cc/libraries/storyblok) | cms | Proprietary | Any (framework-agnostic) | Not measurable | Free tier, paid plans undisclosed | No | No | not scored |
| [Contentful Studio](https://www.editorstack.cc/libraries/contentful-studio) | cms | MIT | React | Not measurable | Quote only | No | No | not scored |
| [Sanity Visual Editing](https://www.editorstack.cc/libraries/sanity) | cms | MIT | React, Vue | Not measurable | from $15/mo | Partial | No | not scored |
| [Builder.io](https://www.editorstack.cc/libraries/builder-io) | sdk | Proprietary | React, Vue, Angular | Not measurable | from $19/mo | No | Partial | not scored |


## Our scores

Not scored. We publish scores only for products we have run hands-on; see the methodology page.


## Alternatives

- [Storyblok vs Builder.io](https://www.editorstack.cc/compare/builder-io-vs-storyblok)
- [Storyblok vs Directus](https://www.editorstack.cc/compare/directus-vs-storyblok)
- [Storyblok vs Puck](https://www.editorstack.cc/compare/puck-vs-storyblok)
- [Storyblok vs Contentful Studio](https://www.editorstack.cc/compare/storyblok-vs-contentful-studio)
- [Storyblok vs Sanity Visual Editing](https://www.editorstack.cc/compare/storyblok-vs-sanity)


## Frequently asked questions

### How much does Storyblok cost?

Vendor-published tiers: free Starter, Growth around €99 per month including five seats, Growth Plus around €349 per month, and Elite by quote. Prices attach to a space, so several projects mean several subscriptions, and monthly billing costs more than annual.

### Is Storyblok a page builder?

Not in the sense this site usually means. Editors compose pages from components developers have built and registered, with no free-form styling. That constraint is the point: it keeps output inside your design system.

### How does Storyblok's visual editor work?

Your front end runs in an iframe inside the Storyblok app with a bridge script. Clicking an element in the preview selects the corresponding content entry, so editors work against the real site rather than a form.

### Can I use Storyblok to give my customers an editor?

It is not designed for that. The editing UI is Storyblok's product with Storyblok's accounts; for a customer-facing editor you want an embeddable library or SDK.


## Sources

1. [npm registry metadata for @storyblok/react (licence, first publish date, latest version)](https://registry.npmjs.org/@storyblok/react) — accessed 2026-08-19
2. [Storyblok pricing page (vendor-published plan prices)](https://www.storyblok.com/pricing) — accessed 2026-08-19
3. [Storyblok documentation](https://www.storyblok.com/docs) — accessed 2026-08-19