Storyblok Reviews & Product Details

Since I first wrote my review, Storyblok has continued to evolve, both in the application itself and with their official libraries. As a PHP and Laravel user, I was very happy to see them release new official PHP clients made in conjunction with Symfony. They’re also continually improving their AI integrations. I’ve not used these much with my client work, but they provide a lot of flexibility and different ways for content editors and developers to interact with content. Review collected by and hosted on G2.com.

They’ve had a couple of breaking changes as they standardized their API, such as one changing the case of a request header which required a quick, emergency fix for some websites. I think they’ve learned from this and improved their communication and testing. Review collected by and hosted on G2.com.

My non-technical editors can build and rearrange pages in the visual editor without asking me. On a recent project for a client of ours, I set up the block library once, and they’ve put together new landing pages on their own since. Initial setup took 3 days, and the block-based structure fits how we design pages anyway. Review collected by and hosted on G2.com.

Component schemas are defined in the UI, not in code. In Sanity or Payload my schema lives in TypeScript next to the frontend, goes through PR review and deploys with the app. In Storyblok I have to keep the two in sync by hand or through the CLI. The editor also gets cluttered once blocks are nested more than 2 to 3 levels deep. Review collected by and hosted on G2.com.

I've been working with Storyblok for over 4 years now - and my experience is only getting better. I'm a content manager responsible for blog content and landing pages - this CMS made this tasks so much easier than WordPress.

What I especially like about Storyblok is that content management is easy thanks to the block system + constantly updated features. The content blocks are a breeze to manage, and thanks to some tweaks, I can also add html code from AI assistants to publish more diverse types of content without having to worry about compatibility.

Also, they've been adding AI features - I rarely use the text editor (although I can see it being super helpful to those working on content inside a CMS), but Alt text generator in particular has been a time saver recently.

I've never had to contact support because everything works well. Review collected by and hosted on G2.com.

Nothing to share here, everything works well. Review collected by and hosted on G2.com.

I love how flexible and reusable Storyblok is. It empowers us developers to write code once and give the power to style, tune and change at any time to the content creator without the need for a new developer implementation. Storyblok also has an incredible uptime, I cannot remember any downtimes in the last three years, not even short ones. Just NONE at all! This shows the robust overall system architecture. I also love the AI Features Storyblok introduced to ease content creators day to day life. Compared to other SaaS providers Storyblok seems to ship features tested and REALLY ready for production, so there are virtually no issues over time. Review collected by and hosted on G2.com.

Better monitoring of Storyblok API usage and a customer success manager that checks these metrics every once in a while to spot deviations from best practices. The support Tickets take ages to resolve. We had production incidents where some changes made by Storyblok caused problems and some of our content was served stale. Such production incidents should be resolved within hours, but it took weeks with very little to no status updates. Luckily we have so little issues with Storyblok all over. Review collected by and hosted on G2.com.

Storyblok is still very easy to get started with, build a POC, and demonstrate the value of a headless CMS to a client. The component-based approach is approachable for editors and relatively easy to explain to teams already familiar with other headless CMSs. Review collected by and hosted on G2.com.

The main reason I eventually moved away from Storyblok was that, for more advanced CMS use cases, the platform felt too opinionated and created more vendor lock-in than I was comfortable with. The Story/Component model works very well for page-oriented content, but I found it more limiting when I wanted a highly customized back office, richer relationships between domain entities, or workflows that did not naturally fit Storyblok's content model. At the time, reproducing a space or environment was also cumbersome, and the Visual Editor / Bridge integration could be frustrating: preview and in-context editing did not always behave reliably. I know Storyblok has since introduced or improved environments, CLI synchronization and extension APIs, so some of these issues may have improved since I last used it. Review collected by and hosted on G2.com.

Storyblok gives us the freedom to build the frontend exactly the way we want using Astro while giving the client an intuitive visual editing experience that does not expose them to the complexity of website management. They only ever have to deal with content. Exactly what a CMS should do. Review collected by and hosted on G2.com.

Its pricing can make relatively basic operational features feel artificially restricted. Bandwidth limits and Enterprise-only capabilities such as S3 backups can force a significant plan upgrade when a smaller paid add-on would be more reasonable. Review collected by and hosted on G2.com.

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.

When editing content, it’s also easy to see when something was last updated, since the time and date are clearly available. It’s exciting to use - not just a pretty interface - and even as a beginner, I’ve had no issues navigating the dashboard.

Support/onboarding - I don't need much help actually because I can easily navigate the Dashboard. AI/intelligence - amazing. The keyword analyzer feature saves me a lot of time. I just need to choose the keywords the best suit to my content. Review collected by and hosted on G2.com.

One thing I dislike about Storyblok is that the learning curve can feel a bit steep at first, especially for anyone who isn’t already familiar with headless CMS concepts or component-based content modeling.

I also think the documentation and troubleshooting experience could be more straightforward for beginners. When it comes to more complex implementations, developers may need to spend extra time researching the best approach, or figuring things out while working with APIs and integrations.

Finally, the pricing and ROI can take a while before you recover the initial investment. Review collected by and hosted on G2.com.

I like that Storyblok makes it very easy to manage content for different countries and languages. It has a very flexible API that has allowed us to create our own products and streamline much of the work. I also value its reliability, its ability to manage content, the features it offers, and how quickly it evolves. We can test beta features and integrate them from early stages. It has integrated very well with our stack, including Next.js, and the initial setup was easy and smooth. Storyblok fit our needs very well and we are very happy with how we manage content today; moreover, using it does not create friction for us. Review collected by and hosted on G2.com.

The AI tokens from Storyblok can be very expensive compared to the amount we receive, so I prefer to create our own products with our own services instead of using their tokens. However, this has never been an obstacle to taking advantage of Storyblok's features. Review collected by and hosted on G2.com.

Beyond the visual editor, I now rely heavily on nestable blocks. I build a component once and reuse it across pages, which keeps content structure consistent. The JavaScript SDK also works well with Next.js, and generating Typescript types from my component schemas has made the frontend code safer to maintain. Review collected by and hosted on G2.com.

Asset management is still my main pain point. Beyond that, setting up the visual editor preview on localhost needs extra steps like configuring HTTPS, which slows down first-time setup. The price jump from the free plan to paid tiers is also steep for solo developers and small teams. Review collected by and hosted on G2.com.

Storyblok is probably the sweet spot of all composable / headless CMS. It brings flexibility in content management, yet familiar metaphors for content editors and marketers. The interface is intuitive and does not need long onboarding processes.

The developer experience is great as well, it is very simple to get started and easy to build complex web pages. It also comes with a good documentation for different programming languages.

Through the Content delivery API, it is easy to integrate Storyblok into different endpoints of content deployment, such as Apps, OOH, and obviously web sites.

The Content management API and the MCP server makes it easy to integrate Storyblok in AI workflows. The publishing workflows maintain accountability, consistency and the human in the loop or integrate with existing approval or compliance processes. Review collected by and hosted on G2.com.

The CLI tool is confusing to work with at times, a lot of documentation on that is outdated or confusing. But with the availability of the new version this might quickly change.

The overall asset management is sometimes a bit bare. However it is easy to integrate external Asset Management systems. Review collected by and hosted on G2.com.