Senior Software Engineer at a tech services company with 11-50 employees
Real User
Top 20
Jun 22, 2026
I believe there are some parts that definitely can be improved inside Storyblok, such as the way content is listed out in certain areas, which makes it a little difficult to delete content. I would add another point about the content import and export feature. If Storyblok could implement that inside the platform, that would be great. I encountered a few projects where clients needed that feature, as other CMS have that capability. Having import and export options would help editors enter a lot of content rather than editing it one by one. While there is an API that can be used, there is no interface for easy content import and export by the editor within Storyblok. Regarding areas where Storyblok could use further improvement, I suggest implementing the import and export feature. Also, the content editing experience could be enhanced; for example, in pages with a long list of components, it becomes challenging to navigate when items start to accumulate. For instance, if we implement many redirects, the load more option becomes cumbersome. A list view for editing experiences would be helpful, and implementing multiple selection or select all features could significantly enhance usability.
Technical Architect at a tech vendor with 10,001+ employees
MSP
Top 10
Jun 21, 2026
Storyblok can be improved by offering more flexibility in terms of schema creation, and it could also possibly improve the way assets are saved and persisted. Storyblok can be improved in the assets area to make it more appealing to business editors.
Full Stack Developer at a consultancy with 11-50 employees
Real User
Top 10
Jun 20, 2026
I am uncertain if this issue with tags has been improved, but whenever I added or removed them in pages, the changes were not pushed through the webhook. Also, if it were not for the limitations on pricing and rate limiting, I would say it would be greater.
The only downside I would mention about my use of Storyblok in these projects was the cache management system that Storyblok has; it was not very good, but all the rest was amazing. I liked the idea to have React components and map them into blocks inside Storyblok and then have the live preview. You could drag and drop components, rearrange everything, and see the live preview. That was a really amazing experience working with a headless CMS such as Storyblok, one of the best I have ever worked with. Storyblok can be improved in terms of cache issues, as it was not resetting the cache. The customer was making edits to the website and wanted to see that in real-time right after publishing the changes, but they were not live at that moment. Sometimes they needed to wait two minutes, thirty seconds, or sometimes more than five minutes to see the changes getting applied to the live website.
Storyblok is a great platform, and it's definitely the best CMS I've ever used, but maybe some of the more advanced features such as custom plugins have a little bit of a learning curve to implementing them. When you're on the lower plans, there's a bit less flexibility with how you can set up your system, such as user roles, and we've had cases before where clients went in and actually edited block definitions because they clicked on the wrong buttons. That's more of an issue with the cheaper plans or the free plan, which is great, but it doesn't give you the control that you need, but that's understandable and expected. I don't want to add more about needed improvements in terms of documentation, integrations, or support, as the support is really good. I'm an MVP for them, so I probably get more direct support than other people, and the docs have been fine, but as I've written the package and that's been going for a couple of years now, I barely need to touch the documentation because things just work as they need to.
I think it is a perfect tool for me, but it would be nice to have some examples of best practices to set up content there, as I have a lot of freedom, and it is not really clear how to build it from scratch; I may run into problems if I do not know best practices right away. I think some tutorials on how to build from scratch content for a big website would be great. I think Storyblok is the best CMS out there; however, I would rate it a nine because there is still room for improvement, particularly with the documentation. I take off that one point because the documentation and best practices examples are missing.
Storyblok is a flexible headless CMS designed to manage content efficiently through a hierarchical structure, allowing developers and marketers to work collaboratively without disruptions. Storyblok empowers businesses by facilitating easy content management and consistent digital experiences across channels. It holds a unique position by combining visual editing with advanced content workflow capabilities. Developers appreciate its API-driven approach that separates content from its...
I believe there are some parts that definitely can be improved inside Storyblok, such as the way content is listed out in certain areas, which makes it a little difficult to delete content. I would add another point about the content import and export feature. If Storyblok could implement that inside the platform, that would be great. I encountered a few projects where clients needed that feature, as other CMS have that capability. Having import and export options would help editors enter a lot of content rather than editing it one by one. While there is an API that can be used, there is no interface for easy content import and export by the editor within Storyblok. Regarding areas where Storyblok could use further improvement, I suggest implementing the import and export feature. Also, the content editing experience could be enhanced; for example, in pages with a long list of components, it becomes challenging to navigate when items start to accumulate. For instance, if we implement many redirects, the load more option becomes cumbersome. A list view for editing experiences would be helpful, and implementing multiple selection or select all features could significantly enhance usability.
Storyblok can be improved by offering more flexibility in terms of schema creation, and it could also possibly improve the way assets are saved and persisted. Storyblok can be improved in the assets area to make it more appealing to business editors.
I am uncertain if this issue with tags has been improved, but whenever I added or removed them in pages, the changes were not pushed through the webhook. Also, if it were not for the limitations on pricing and rate limiting, I would say it would be greater.
The only downside I would mention about my use of Storyblok in these projects was the cache management system that Storyblok has; it was not very good, but all the rest was amazing. I liked the idea to have React components and map them into blocks inside Storyblok and then have the live preview. You could drag and drop components, rearrange everything, and see the live preview. That was a really amazing experience working with a headless CMS such as Storyblok, one of the best I have ever worked with. Storyblok can be improved in terms of cache issues, as it was not resetting the cache. The customer was making edits to the website and wanted to see that in real-time right after publishing the changes, but they were not live at that moment. Sometimes they needed to wait two minutes, thirty seconds, or sometimes more than five minutes to see the changes getting applied to the live website.
Storyblok is a great platform, and it's definitely the best CMS I've ever used, but maybe some of the more advanced features such as custom plugins have a little bit of a learning curve to implementing them. When you're on the lower plans, there's a bit less flexibility with how you can set up your system, such as user roles, and we've had cases before where clients went in and actually edited block definitions because they clicked on the wrong buttons. That's more of an issue with the cheaper plans or the free plan, which is great, but it doesn't give you the control that you need, but that's understandable and expected. I don't want to add more about needed improvements in terms of documentation, integrations, or support, as the support is really good. I'm an MVP for them, so I probably get more direct support than other people, and the docs have been fine, but as I've written the package and that's been going for a couple of years now, I barely need to touch the documentation because things just work as they need to.
I think it is a perfect tool for me, but it would be nice to have some examples of best practices to set up content there, as I have a lot of freedom, and it is not really clear how to build it from scratch; I may run into problems if I do not know best practices right away. I think some tutorials on how to build from scratch content for a big website would be great. I think Storyblok is the best CMS out there; however, I would rate it a nine because there is still room for improvement, particularly with the documentation. I take off that one point because the documentation and best practices examples are missing.