I use Cloudinary to save files for our application, especially when users want to upload or change profile pictures. We save all those user profile pictures on the product. We also have an option where doctors can give documents to patients. We save those generated PDF prescription documents. We use Cloudinary to save our uploaded external resources so we can handle and keep them in their own buckets.

I like the tool best because it's straightforward and doesn't have too many complicated options like AWS. The dashboard is clear - you create a directory, get credentials, and then use those in your Node.js or Java application to access resources. With AWS, you have to consider many things, like bucket policies and user permissions. It doesn't have these complications. Everything on Cloudinary is clearer than other platforms I've seen. It is very easy to use. It's easier than the AWS platforms I've seen. Even general developers can use it, while AWS needs more experience.

The solution saves time and resources in several ways. It's easy to get started with, saving time from the beginning. You can implement file uploads in about thirty minutes without complications. The SDK and APIs provided to access their resources are simple and not complicated. Cloudinary is also a popular platform with good documentation and community support, making it easy to find solutions to problems.

I think Cloudinary has room for improvement, depending on the project you're working on. Changes might not be needed if your project fits what Cloudinary already offers. But if your project needs some changes, you can make them.

I have been using the product for four years.

In the two years we used the tool, we never had any issues with stability or bugs. Based on stability, I would give it nine out of ten or even ten out of ten because we didn't face any issues in two years. But saying ten out of ten might not be fair, so I'd say nine out of ten.

The tool is scalable. For example, you can expand your resources from five gigabytes to ten gigabytes. But you have to pay for the expansion whether you use it all or not, unlike AWS, where you pay according to usage.

In our organization, we have about 200,000 users using Cloudinary. Some had profile pictures, others had documents shared between users and doctors, and some uploaded pictures of their sick animals or pets.

I can't evaluate the technical support team because we never needed to use it. We didn't face any crucial issues that required support in two years, which is good. Everything was clear.

The initial setup of Cloudinary is very easy, not difficult at all. Our company created an account, and we could create teams and invite team members.

We decided to quit using Cloudinary after two years because we were getting a lot of users, and it was becoming expensive. Cloudinary had fixed charges, so if we agreed to pay 500 USD per month, it would be the same whether we used high or low resources. They would notify us if we exceeded our limit, but not if we used less—however, AWS charges according to usage, which became more cost-effective for us as we grew. With AWS, you might pay 100 one month and 200 the next, depending on your usage.

I faced a challenge when we needed to migrate from Cloudinary to AWS when we hit almost 500,000 users. I initially tried to migrate files manually, creating an API to fetch files from Cloudinary and upload them to AWS. After migrating about 100,000 files, I discovered Cloudinary has a feature to migrate resources to other platforms easily. I had spent almost a week doing things manually before finding this efficient solution. I was amazed when I discovered I could do it with a simple command, moving everything from Cloudinary to AWS in minutes. But at the beginning, it was quite hectic.

I would recommend Cloudinary to others, especially medium businesses or companies with fewer than 500,000 users.

I advise first-time users that everything is easy, and your employees don't need special skills to get started. There's also a large community of Cloudinary users, so you can easily find documentation and solutions online if you get stuck.