Question about how credits are used
I'm trying to understand how Cloudinary uses credits. I have read several posts on this but none of them directly addressed my question. Given the scenario below, can someone confirm that my credit usage calculations are correct?
Period 1
1000 images are uploaded ⇒ uses 1 credit (for transformations)
These 1000 images equal 10 GB in size ⇒ uses 10 credits (for managed storage)
These same 1000 images are downloaded once each ⇒ uses 10 credits (for bandwidth)
Total credits used for Period 1 = 21
Period 2
2000 images are uploaded ⇒ uses 2 credits (for transformation)
These 2000 images equal 20 GB in size ⇒ uses 20 credits (for managed storage) + uses 10 credits (also for managed storage for images stored during Period 1)
These same 2000 images are downloaded once each ⇒ uses 20 credits (for bandwidth)
Total credits used for Period 2 = 52
Are my calculations correct for Period 1 and Period 2?
Answers
-
Hey there,
Your breakdown is correct, BUT, we do not recommend delivering assets without applying at least some transformation.
By applying any transformation to your images (e.g. width, height, etc), Cloudinary automatically optimizes the image using the industry's best practices. The easiest and often times most effective optimizations would be to add both f_auto (automatic format) and q_auto (automatic quality) to the URL.
In any event, by optimizing your assets, your bandwidth should be reduced significantly and your transformations will be increased slightly as well as your storage. Ultimately, bandwidth is typically the most important to focus on reducing, not just from a cost perspective but also site performance and delivery.
I hope this helps! 😁
Let me know if you have any questions.0 -
Hey thanks Zachary for the confirmation and the advice on how to reduce credit usage. I will definitely apply those suggestions.
0