Cloudinary Reviews

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.

Cloudinary is a cloud hosting platform for images and videos. It provides APIs for developers to host their images on the platform. I use it to build applications where images are hosted in the cloud rather than on local storage. This helps with optimizing and managing images efficiently.

For digital asset management, I store all my images on Cloudinary instead of on my phone or laptop. This allows me to optimize the images, reduce their file sizes, and use them across various social media platforms. Depending on the use case, Cloudinary offers different options to manage and utilize images effectively.

The first time I discovered Cloudinary, I mainly used it to store my images. If you are on our website, where people must upload images, then instead of storing the images in a database, I stored them in Cloudinary, which gave me a link to the image. The link is what you store in the database, and it becomes easier. Cloudinary added a new AI feature, and it is amazing. When I tried it out, it was powerful, and I used it in a project and loved it.

The most valuable features of the solution revolve around image storage. I think that is what is cool about the tool, and I use it the most. The AI is promising. There are so many things you can do with the tool. You can edit images, and you can refine images to make them clearer. The tool supports searches, meaning you can search the elements inside the image. If there is an image of a landscape, you can use certain options to search for that image. You can search for all the images that have particular areas from your image. It could get you all the images with the particular aspect of the image you provide or choose, which I think makes working easier.

We used Cloudinary as a library within our project's tech stack, primarily for image transformation.

It was an online platform for selling artwork. There was a requirement that when an artist uploads an image to the website, it should instantly create mockups of how the artwork would look in various interior spaces. Because of this requirement, we switched from S3 on AWS to Cloudinary.

The automation tools were used most often. They are quite convenient and cover our requirements.

It actually supports the growth of the business because it gives us a lot of out of the box things. We can easily do things in a week that we weren't able to do before.

I use it to upload images. I primarily use it to store and load images. 

So far, so good. It implements most of what we need in development, including the option to upload images from other cloud storage platforms. I haven't seen any problems with it.

It's quite effective for what we use it for. It is a decent tool. 

I use the solution to host files and documents. I use it when I have an application where I want to store files online. I use the Cloudinary server to host the files, and I use the API to integrate the platform with my back end to save files and documents.

One of the best features of the platform is that we have a generous free tire that I can use for some of my projects without worrying about the platform's cost. The free-tier version is one of the biggest pros of Cloudinary. The API integration in Cloudinary is quite easy and straightforward.

I used the solution just to learn about the platform, and I used it for a couple of personal websites. Mainly, the websites have a lot of images or galleries. What I liked was that previously, when I was making websites, I had to create a lot of images manually to a certain size to be responsive for screens of different sizes. Then I learned about Cloudinary and how it does it all for you. You can upload your assets to Cloudinary, and it automatically detects the user's browser and sets up the image in the right format to optimize the right size, which is amazing.

When you're starting off, it can be a little bit overwhelming. I am just gonna look at the screen now. Once you log in, you have a management console and many different things, so you won't really know where to go. The onboarding could be made a bit easier. I did Cloudinary's courses. If you use the tool's UI, there are different icons on the left screen, and you won't know where to go first and what is important. The UX can be improved a bit.

When you open the product's management console, it can just be a little bit overwhelming at first until you figure it out. Cloudinary just needs to relook at how to simplify the tool or use the tool's guidance walkthroughs for new users.

The product needs to get noticed, it is important to have someone from Cloudinary on Stack Overflow or Syntax.fm and talk with the developer community.

We use Cloudinary to store various media related to the vehicles, such as engine sound recordings and images of the vehicle from different angles, including the interior. Recently, we've also started storing short engine videos, around 15 seconds. Additionally, vehicle documents are stored on the platform, and the front-end team uses it to handle user uploads.

The Cloudinary Dart package is poorly implemented. It works for simple use cases but fails when implementing more advanced features, like handling signatures. It appears to be outsourced, and several important elements are missing. For instance, some necessary class exports are absent, meaning if you need a class to create a request, you must import it manually. It relies on hard-coded strings, making it nearly unusable for anything beyond basic tasks. While it might work without signatures or advanced features, it's unreliable for more complex use cases.