My main use case for Contentful is building websites and managing the content. We have a public facing website where we showcase our products and offerings to people, and all of that content, images, and everything is managed through Contentful.

The best features Contentful offers include the Rich Text editor, the linking, the images, pages, and templates. I rely heavily on the Rich Text editor because that is where I create customized components. For example, Rich Text lets us paste images and links, and based on the JSON response structure we receive from Contentful with the GraphQL query, we know the structure of it, which helps render specific components on the screen, such as a banner that will have background images, buttons, and text, and the same goes for the slider and carousel.

Contentful has impacted my organization positively because the business is able to change the content without the help of a developer, and they can make a deployment very easily. This has led to measurable outcomes, such as a faster time-to-market and reduced workload for developers.

I think Contentful can be improved in several ways. Sometimes the linking is challenging. If you are using too many links, then it is actually making the application deployment time longer, so Contentful needs to figure out a way to solve that problem. Additionally, cost-wise, I feel our organization thinks it is too much because we were planning to use Contentful for our global site, which has four languages support, and for each language, we need to create different spaces. If Contentful could allow us to add the four languages in one go, that would be great.

I have been using Contentful for the last two years.

Contentful is stable.

Contentful's scalability is good.

The customer support for Contentful is good.

Previously, we used an on-premise based Content Management System, which was Adobe AEM, and we changed to Contentful because of faster deployment and evolving technologies.

I would say we have seen a return on investment because the cost in the infrastructure got saved. Contentful is a platform offering that manages the infrastructure for us, resulting in savings in terms of infrastructure.

My experience with pricing, setup cost, and licensing is that mostly, a developer will not be managing those aspects, but from my point of view, Contentful is a bit pricey.

I rate Contentful an eight on a scale of one to ten. My advice for others looking into using Contentful is to go for it. I have no additional thoughts about Contentful before we wrap up. My overall rating for this review is eight.

My main use case for Contentful is for migrating our Oracle ATG server into Contentful as a migration project.

During that migration project, we created multiple content types and developed a custom app where we map the ATG server code to our content types. We used that mapping to import the particular content to Contentful.

After the migration, we used this particular content for the website, specifically for our client Sephora, where we utilized all this content.

Contentful offers many best features including Preview, Custom Apps, migrations, Merge App, and workflows.

We used the preview feature whenever we wanted to see how particular content looks, and at that time we ran our server locally and tested it. Additionally, we used custom apps for building bulk editors and multiple features where we could reuse some of the code.

Contentful has positively impacted my organization as it has been a major breakthrough. The producers can automatically update their content without relying on developers, which is really helpful for the producers.

I could say we saved around 60% of the time for developers. Previously, we maintained all the content, but now producers handle that, which allows developers and producers to publish their content immediately when they want to update it.

Contentful needs to be improved for migration, not only for migration, but from lower to higher environments as well, as the schema diffs and everything are not working as expected. Improving the CI/CD pipelines would be greatly helpful, and it could build similar capabilities to Builder.io for enhanced growth when using Contentful.

I have been using Contentful for more than five years.

Contentful is stable.

Contentful is scalable. We can scale the application to any level we want without any problems regarding scalability.

Customer support is good. There are three levels of support available, and level one support resolves issues within 15 minutes to one hour.

We previously used ATG Oracle Cloud, which is too old and requires developers to handle the cloud architecture and content, leading to our migration to Contentful.

I have seen a return on investment. Previously, we used to have 10 developers for the ATG Oracle cloud, but for Contentful, we only need two developers, and once it is streamlined, producers can handle everything without the need for developers.

I evaluated Strapi, but Strapi requires everything to be done by the developer only, including in-house premises and deployments, while Contentful allows us to do everything on the fly.

Others looking into using Contentful can use it seamlessly without relying on any other deployments. Everything is present in Contentful itself, and any custom apps can also be deployed within Contentful without needing separate servers.

My main use case for Contentful is optimizing images and videos. While people use Contentful to build websites, Contentful does not provide an inbuilt image and video optimizer. ImageKit fills this gap, allowing people who use Contentful to optimize their images and providing a digital asset management solution inside the Contentful UI itself. That is the kind of integration I am working with in Contentful.

I have a website and want to optimize my images and videos using Contentful to build that website, which is very easy. I can use my own frontend and then use the API to build that website, while also integrating ImageKit, which is my current organization. It is a mixture of these two approaches.

The best features Contentful offers are its APIs and how easy it is to integrate them. Feature-wise, the majority of CMSs are the same; I have used Strapi, and feature-wise, those are similar. The ease of use and the way Contentful provides the APIs and how easy it is to fetch the data directly and use it in your frontend is the best part. I have not explored many features, having mostly built a basic web page, so there could be features that I am not aware of, but the ones I have used were quite intuitive and easier to use.

Contentful's impact on my organization is that we do not use it very much. Contentful has not helped my organization or our customers achieve any measurable benefits, such as saving time or improving workflows, as we have not measured that. It does help customers who are using Contentful, but I have not quantified it.

Contentful works well for me; I might need to explore it a bit more to identify improvements. As I mentioned, I have been using it for a specific task, which it accomplishes quite well. I built a web page and integrated ImageKit successfully, so it works well in that way. Perhaps in the future, I can provide more feedback for this question.

I have been using Contentful for around a year, mostly integrating it with my current company, ImageKit, which is an image CDN and image and video CDN, and that integrates well with Contentful. That is how I started working on Contentful.

Contentful is stable in my experience; it is quite stable. The UI works well, as I did not encounter any issues with it and the APIs seem to work without problems.

I have not scaled Contentful to that level, so I would not be able to comment, but I would assume it is scalable.

I have not had any experience with customer support, as I managed to figure out the majority of things using the documentation and other resources. Therefore, I did not need to reach out for support.

I have used multiple solutions before Contentful because I work with many customers using different systems. I have used WordPress, Magento, Shopify, Strapi, and then Contentful. Strapi and Contentful stand out to me because they are next-generation CMSs, where the APIs and functionality are much easier to understand. It is JavaScript-based, making it a very easy way to start building websites. While I have not switched away from others, I see a definite improvement compared to WordPress and other traditional CMS systems.

My experience with pricing, setup cost, and licensing is that I did not use the price plan; I was using the free plan, which did what I wanted it to do. Therefore, I cannot comment on the cost. The setup was easy, which I think would be the same even for the free plan and the pricing plan, but since I have not used the paid tier, I cannot speak on it.

I was using the free plan which did what I wanted it to do. Therefore, I cannot comment on the cost.

I have seen a return on investment with Contentful, as it definitely saves time. Even if someone is not technical, they can provide a structure, and then someone from the technical team can pull data. Contentful gives a lot of control in terms of what you want, allowing even non-technical people to contribute positively. As a SaaS, it also helps significantly since you do not need to host it and deal with associated complexities.

My experience with pricing, setup cost, and licensing is that I did not use the price plan; I was using the free plan, which did what I wanted it to do.

Contentful works well for me; I might need to explore it a bit more to identify improvements. As I mentioned, I have been using it for a specific task, which it accomplishes quite well. I built a web page and integrated ImageKit successfully, so it works well in that way. Perhaps in the future, I can provide more feedback for this question.

Contentful has not helped my organization or our customers achieve any measurable benefits, such as saving time or improving workflows, as we have not measured that. It does help customers who are using Contentful, but I have not quantified it.

My advice to others looking into using Contentful is to definitely try it because if they have a use case of providing some sort of tool for their non-technical people to build things, Contentful stands out. I have used Strapi, which can be a little more technical and tougher for people to understand. Contentful, in contrast, enables non-technical users to build things while their technical team can then integrate it.

I would rate my overall experience with Contentful as a 7 out of 10.

My main use case for Contentful is that I built my personal brand called immediatetiger.com and I needed a section called blog where I could post articles from time to time about anything that I found interesting and related to my work. I needed something where I could log in and manage my articles with a basic API that would expose my data and I could read them through a microservice.

Because I use the Next.js framework, I found Contentful very easy to integrate and basically expose that to the front end so I can see articles and manage them through Contentful's content management system.

I use Contentful solo. I worked at one company and integrated Contentful as well, but for my personal brand, it is literally just a solo solution to manage my personal blog. That's why I also have a free account, because I set up my account a long time ago, but I didn't have a real solution that I could utilize Contentful for. I can see that right now it works for me long-term, so it's a great choice.

I have only four articles so far because it's been since January 2025, so it's just basically this year and we're currently in March, so it hasn't been a long time. What I found very interesting is that I can upload images. Because I can upload images and publish them through Contentful, that simplifies a lot of things because usually I use Google Cloud storage. When you write articles, it's better to keep images and articles in one place in Contentful because it's just so easy to think about. For now, because I'm very slow with doing my articles, it's a really great choice. I know that Contentful also does GraphQL, which is great as well.

Contentful offers several valuable features. The most valuable feature is Content, where I can create new articles. I also found the Media section interesting, where I can upload my images. When I look at the content, I found it interesting how I can model content. When I click on my article, I have ID, title, description, and images fields. This feature where I can add fields of a specific type is really great when you look at a project in the initial stage, because you never know how long-term you will expand or what will happen with the project.

Apart from these features, I found that it's easy to integrate, and the documentation is easy as well. I could easily create the API key and everything else. When you look at the API keys feature, I think it's very stable. I never had any problem. Webhooks also exist, but I don't use them right now. Maybe I will use them at some point. Because I publish my articles very slowly and not many, I use mainly these features for now.

Contentful has positively impacted my work because I have people browsing Google and because I use SEO as well, and my articles are indexed and written by me. People come and read them. The most valuable part is that some people find them attractive and actually read about topics like the difference between chatbots or agents, what is a chatbot, what is fine-tuning, or remote work. These are actually my articles, which are quite important looking at the market right now. Some people come and view and read them.

To be honest, I don't work so deeply with Contentful to see anything that I would change. Based on what I do, everything is really done in the sense that I don't need any changes. Maybe in the future something will change, but at this specific moment, I think I got everything I need from Contentful.

The only thing I would mention is basically fields and types. That's what I found quite difficult at the beginning to understand how all that works. So there is some space to improve. Apart from that, I didn't have really any big requirements in terms of any changes. I would need to look very deeply once again at what I did because I did that some time ago. For now, I don't need any updates from Contentful. At least, I don't see it at this specific moment. The job I really do by using Contentful is really little. I don't post every week or every single day to basically expect something more in terms of quality.

I just noticed that there's a new AI Automation tab. I have not seen that before. At this specific moment, I think everything works in a really great way. It's very stable. That's the most important when you post content. The last thing you want to see is that the service disappears or your content is somehow changed. For me, it's been very stable. Even though I have just four articles, they're very important for me, and my personal brand is very important for me as well. I just try to make sure that I stick to basically stable solutions. For one year and six months, I never had any problems with Contentful. Even when I was updating the module, I never had any problems.

I have used Contentful for about one year and six months, starting when I began building my personal brand and one of my sections is a blog, where I needed to manage my blog articles somehow.

At this specific moment, I think everything works in a really great way. It's very stable. That's the most important when you post content. The last thing you want to see is that the service disappears or your content is somehow changed. For me, it's been very stable. Even though I have just four articles, they're very important for me, and my personal brand is very important for me as well. I just try to make sure that I stick to basically stable solutions. For one year and six months, I never had any problems with Contentful. Even when I was updating the module, I never had any problems.

In terms of Contentful, I would rate it 10/10 based on my usage and driven by the stability of the service. When I was building my personal brand for the last one year and six months, I never saw the service go down or break my articles in any way. So there was no downtime. At least I have not noticed that. This is the reason why I rate it 10/10 because when you publish your content and you have articles, even though you have just four of them, the company Contentful may not understand the value of my ideas and why I do it. However, it is very important that there are no downtimes periodically since I bought my domain and I build a lot of other things on that domain as well. My service is quite big. When I choose companies, I look at how stable they are, what's the downtime, and if I had any problems during the time I was working with that actual integration or something. There are companies where things fail and so on. To be honest with Contentful, since I signed up and used this service twice, I didn't have any problems in terms of downtime.

Contentful scalability in my experience is great.

There were challenges because when I was creating a solution, I didn't know Contentful very well. I found a lot of problems with types and matching in TypeScript types with the fields I was using and with the API and the full module. The biggest problem I found was to actually set up correctly and match types so I could build the project and deploy that correctly. This was causing me at the beginning a lot of problems when I was trying to pull data and display my articles. Also quite challenging was displaying the image. It took me a while before I actually did that. However, I managed to display everything the way I want it.

I was using Drupal and Joomla a long time ago. I was also using WordPress. However, all these systems are not headless. I was using those content management systems for a while for different reasons. For my personal brand, I was looking for a solution where I could create different types of fields and I could connect to the API and get the actual values of these fields.

I found a lot of problems with types and matching in TypeScript types with the fields I was using and with the API and the full module. The biggest problem I found was to actually set up correctly and match types so I could build the project and deploy that correctly. This was causing me at the beginning a lot of problems when I was trying to pull data and display my articles. Also quite challenging was displaying the image. It took me a while before I actually did that. However, I managed to display everything the way I want it.

I use Contentful solo. I worked at one company and integrated Contentful as well, but for my personal brand, it is literally just a solo solution to manage my personal blog.

For one year and six months, I never had any problems with Contentful. Even when I was updating the module, I never had any problems.

Contentful has positively impacted my work because I have people browsing Google and because I use SEO as well, and my articles are indexed and written by me. People come and read them. The most valuable part is that some people find them attractive and actually read about what the difference is between chatbots or agents, what is a chatbot, what is fine-tuning, or remote work. These are actually my articles, which are quite important looking at the market right now. Some people come and view and read them.

I'm on a free plan just because I don't post a lot and the basic setup is free. So at the moment, I'm on a free plan.

I was looking at Netlify or something, and looking at WordPress.

I do use Google Analytics. I track my views and I can see how popular my articles are. It's not a lot of views, but people systematically come and read something, which is good.

I didn't check support, but when I was doing that I found out that it's easy to generate the API key and easy to look at the documentation and easy to integrate Contentful with Python as a module. Contentful's module in Python is easy to set up, plus the ability to create the API key easily. Looking at Contentful itself, adding articles is really easy. You upload the image first, then you create the content, you publish, and that's it. It works. Because of that, I think it's good as well. The UI is very normal. I could suggest to Contentful that maybe there are some ideas in terms of content. Now we have AI and a lot of great designs you can create with basically AI. Maybe that's where Contentful could look at, how to innovate or reinvent that part. Even though it looks good, maybe there is space to innovate something.

Make sure your API key is safe. That's what I would suggest. Focus on your content and try to divide your content into different sections and think about what type of section that is and what type of format that should be. That's how I would advise people to look at Contentful. Think about what you want to do, what you want to build, divide this into smaller pieces and think about what type of field that is, and then try to match this with Contentful fields.

There is an AI and automations tab. I didn't look at this section, but I don't see any chatbot available on the app when I sign in. Agents are very important right now because, for example, if you had a section when I look at content, I may have a question about anything. I could ask anything about my article and there's no chatbot that I could talk to when I log in myself. Probably something very important right now is that if you build an article and you are very new to Contentful, it's very hard to understand everything at once. Even though it may look very simple, it's actually not when you build and integrate the module in Python, for example, and then you need to expose that to the front end and so on and so on. You need to use Postman, make requests, and try to understand how it all works. It's actually a lot of things. A chatbot would help your clients for sure because they will have questions. For example, how to connect Contentful through GraphQL and how to connect Contentful through REST. Even though documentation is there, I think questioning an agent is actually much better for me.

I rate this product 10 out of 10.

My main use case for Contentful is to create the content for a website for a bigger company as mine, and I'm also a backend developer and design the Contentful model and the content that uses it. A quick specific example of how I used Contentful for my website is the e-commerce website for a bigger company in Germany.

In my experience, the best feature Contentful offers is the application plugin mechanism. The add applications I can add to Contentful to customize the application is highly beneficial.

What I appreciate most about the application plugin mechanism is everything around the deployment and the chosen front-end framework for my project was great, and React also. There are some limitations, which is in the nature of how the plugin mechanism was designed. The iframe technique was the blocker to implement SSO for connecting to other services. However, there are other techniques you can use.

Besides the application framework, something that stands out about the features is that the publishing mechanism can be improved further. With the start of 2025, the local-based publish was introduced by Contentful. That is a great feature, but it had some limitations. Backend implementation for validation, the bulk validation was no longer supported for this feature. This is a big bug. Contentful never lined out the timeline when it can be fixed, and I have two bugs open on Contentful now. That is not favorable for me.

Contentful can be improved to have a full-featured free account, perhaps with fewer content types. However, with all features, a free developer could test everything without having a company that subscribed to an enterprise account, which would be great.

The rate limit on the management API is a big deal for most developers and is something that would make Contentful better. The inability to search for JSON objects, meaning content types that contain fields with JSON objects and looking for some field values in the JSON, is not supported. It would be nice to have something like this.

I have been using Contentful since 2018, for eight years.

Contentful is stable. It is really stable.

Contentful's scalability is fine. Sometimes it was going slower, but most of the time there was a fix available by Contentful. The stability and scalability were good.

The customer support reacts relatively fast if you have the right subscription. I would rate the customer support a nine on a scale of one to ten.

I previously used a different solution from IBM. I do not remember the name. It was a well-known system from IBM. On one hand, and on the other hand was Drupal. Both were on-premise, and the company looked for a SaaS solution. Contentful made sense a few years ago, and we developed for a few years with Contentful.

I cannot tell you much about the pricing, setup cost, and licensing. It was in the field from another colleague. I think it was easy, and I cannot tell you anything about that.

I had a team of five developers dealing with Contentful, but we are facing some bugs, and the support was not as good.

There was no return on investment. It was very expensive to implement all the needed specialties a company needs for its public publish strategy, to publish the content in different countries, different markets, and different languages. This was a concept that Contentful does not support out of the box, and we had to deal with a complicated content model. It was very expensive to implement, but we had chosen Contentful, and so we had to deal with it.

I evaluated other options before choosing Contentful. I do not remember the names we evaluated. It was in late 2018, and I cannot recall which specific alternatives were considered.

Contentful has positively impacted our organization because it is seamless and almost 60% of the content is flowing well with no dependency on any particular part of AEM. We are directly using the content we create with GraphQL into the UI.

There are many time savings and positive outcomes after switching to Contentful. Product owners who use Contentful are very happy because they can create content themselves, which eliminates the need to depend primarily on developers. This is a significant positive point.

Deployments could be somewhat easier for migrating content from lower environments to higher environments, which is a challenge we are currently experiencing with Contentful.

My advice for others looking into using Contentful is that they can use it seamlessly with no problems. I would rate this review as a positive recommendation for Contentful.