What I like most about Storyblok is its visual editor—it makes content changes easy to preview in real time, which really helps collaboration between developers and content teams.

I also appreciate the component-based structure, which keeps things consistent and reusable. The headless CMS setup is super helpful too, letting us push content to different platforms without extra effort.

It’s flexible, supports multiple languages out of the box, integrates well with modern frameworks, and has a clean interface that’s easy for anyone to use. Overall, it strikes a great balance between power and simplicity. Review collected by and hosted on G2.com.

One thing I dislike about Storyblok is that its learning curve can be a bit steep at first, especially for those unfamiliar with headless CMS concepts or component-based content modeling. Review collected by and hosted on G2.com.

I find Storyblok easy to use, and appreciate that it has on-going updates, new features and support. It integrates well with frameworks such as Next.js and Astro, and has good documentation for this. Review collected by and hosted on G2.com.

Some of the ways in which data/blocks/content is organised could potentially be improved. There can be a bit of a learning curve for new users. But generally it is pretty good. Review collected by and hosted on G2.com.

I like that Storyblok has an easy interface and provides an easy way to configure different block libraries. I appreciate all the SDK and endpoints it provides. I also loved the copy/paste feature between workspaces, even though it's gone now. Review collected by and hosted on G2.com.

I dislike that the copy/paste between workspace is gone, which I loved. Also, some rate limits were a bit complex to understand. Review collected by and hosted on G2.com.

Storyblok offers a fantastic visual editor that makes it easy for both developers and content editors to work together. Its component-based architecture allows us to create reusable blocks and streamline content management across multiple projects. The headless nature of the CMS makes it easy to integrate with any frontend framework. The documentation is solid, and the UI is clean and intuitive. Review collected by and hosted on G2.com.

Storyblok has a bit of a learning curve at the start—especially for non-technical users. The pricing can also be a bit high for smaller teams or startups. At times, the UI can lag when working with complex content trees, and more flexibility in customizing workflows or permissions would be a great improvement. Review collected by and hosted on G2.com.

Storyblok is quite easy to understand. It offers a nice developer experience. CMS editors do not need exhausting onboardings (if the blocks are developed carefully). Storyblok offers a nice feature set out-of-the-box. Fast responses over the Discord channel. Review collected by and hosted on G2.com.

I am missing same basic feature and it does not seem like these features are even on the list. For example hide/show components, a field type to select folders, a field type to select one or multiple tags. All of that need to be developed by the integration team. Review collected by and hosted on G2.com.

Storyblok is for me the fundament for successful websites and web apps. I implemented it across several companies and it was so flexible for a whole range of different use cases. Review collected by and hosted on G2.com.

Ofc it needs dev capacity for our advanced use cases that can break certain things easily also it requires training first, but all doable with the right team and resources Review collected by and hosted on G2.com.

Storyblok separates content from the code. Our content team can now update things like homepage banners and sliders without needing a developer. The visual editor is also great; it has a live preview in all. It’s made the change process faster and less frustrating. Review collected by and hosted on G2.com.

As someone who is new to headless CMS platforms, there might be a steep learning curve; you need to understand the component structure. But once we got the hang of it, it’s been mostly smooth. Review collected by and hosted on G2.com.

The customisability of Storyblok is the biggest USP for us. As a headless CMS it allows us to work with developers to make award-winning websites with no restrictions.

It is a very clear and easy to use system and integrates perfectly with our Shopify store to give us the best of both design and ecommerce. Review collected by and hosted on G2.com.

Like with any system there are quirks (eg favours Chrome over Safari) but no more than any other system I've used. Review collected by and hosted on G2.com.

For our developers, it is very straightforward to program with it. Our editors also find the operation easy. Review collected by and hosted on G2.com.

Storyblok unfortunately pursues a very expensive pricing strategy in the enterprise sector, which used to be significantly cheaper. The support could also be improved. Review collected by and hosted on G2.com.

It is definitely the best of its kind - a block based system natively integrates with the component system of React and thus makes it easy as a developer to "translate" the structure content editors define into something visual. Compared to WordPress or other legacy CMS systems, it is definitely the go-to-way for people using React, Next.js or similar technologies. If you have simple requirements, you will have a great time using Storyblok. For very simple blog pages and the-like there should be no issues. It is actually pretty easy to get up and running with extensive guides that show you exactly what you need to do. It is easy to integrate as there are example repositories, blog posts, and documentation entries. If you intend to build something more complex though, your are way more likely to run into some limitation though and you may even be bottlenecked by the guides down the line (see below in dislike part).

I work with Storyblok almost daily since we adopted it about 9-10 months ago and definitely like the ease of use in the editor interface, even though I am not really an end-user but you still spend much time in there when testing stuff. Our marketing team had great feedback too, especially in comparison to our old, slow WordPress instance.

It is great that the SDKs are open-source - this helps understanding some internal functionality and can help in resolving bugs without the need to contact anyone. It also allows to potentially directly contribute, but I would say that is a whole different discussion if you as a company want to/should contribute to an SDK of a software you potentially already pay thousands per month for. Review collected by and hosted on G2.com.

The first thing that really startled me was that the API sometimes has a really weird data format - numbers come as string, empty fields are "" instead of null (this also applies to e.g. booleans), etc. We built custom wrappers to normalize the data format and validate content coming from Storyblok. It is a pretty common pattern that you need to do some kind of custom solution building or creating workarounds, especially if you plan to use it extensively for all different kinds of content with different functionalities in mind. While that is not necessarily bad, I have seen multiple GitHub issues mentioning "XYZ should [already] be in the library". I don't want to know how often the same basic stuff has already been (re-)implemented all over the world.

I have found myself countless times scouring through the OSS source code of the React and JS library to find a bug, a solution or undocumented special case. Additionally, some in my opinion "no-brainer" features are definitely missing and resulted in us having to invest many hours into building something custom again and again (for example text alignment in RichText does not exist) - it is great that it is even possible to extend and workaround the system using additional fields or custom plugins, but every time I think about the fact that the Enterprise pricing plan is pretty expensive I say to myself everything should be buttery smooth out of the box.

While the support team is super friendly, at least in all cases I had to reach out to them, out of all feature requests we ever submitted over the course of almost a year now none have landed in the software yet (so prepare yourself to build custom stuff and workarounds). The feature request process is also pretty intransparent and you don't know if it has been considered, rots in their backlog forever or if it was internally discarded. Review collected by and hosted on G2.com.