
I like how quickly I got Cloudinary working with Django. The Python SDK is easy to use, and I had uploads working the same day. I can resize, compress, and change image formats right from the URL without writing extra code, and use the same file for thumbnails and full-size images. Images load fast through the CDN, and automatic quality and format settings save storage and bandwidth. Quick uploads and instantly opening files help our document checks and operator onboarding move faster. Smaller images also make our dashboard and app load faster for staff on slower networks. Storing just the URL and public ID in Django saves development time and keeps our server costs low. I also like that the same media shows up across our internal tools and that the docs cover the setup basics. Review collected by and hosted on G2.com.
I find the credit system confusing at first, and it’s hard to estimate monthly usage as our uploads grow. The dashboard has a lot of options, so new team members need time to get comfortable with it. I’d like more Django examples in the docs, especially for advanced transformations and signed uploads. A usage estimate that shows how credits go to storage, transformations, and bandwidth, plus alerts before we hit a limit, would help. A short guided tour or a simpler default view would also make it easier for new team members to get started. Review collected by and hosted on G2.com.