Cloudinary counts all image processing.
For example, if you upload an image, then apply a transformation (e.g., w_200,h_200,c_fill
), two transformations will be counted towards the transformations quotas. Once for the original image's upload, and an additional one for the initial transformation generation (the first time the 200x200 image's URL is accessed).
After the transformation is generated, the transformed version of the image is stored in your account for quicker recurring access. Therefore, for the next requests of the transformed image's URL, Cloudinary returns an already generated image that doesn't require further processing and therefore isn't counted as additional transformations.
Another matter that should be taken into account is the media-lib-thumb version which is being automatically processed upon uploads via the media library or while browsing through your uploaded images.
In addition, using the explicit
API to process resources (e.g. generating eager transformations, extracting an asset's metadata, colors, pHash, and others) is also considered as a transformation.
For more information regards counting of Transformations and other plan limits, see:
Comments
2 comments
What happens to chained transformations? Would two chained transformations get counted as 2 or 1?
Hi,
Thanks for reaching out.
We count transformations as a newly created asset (original or derived). it means that chained transformations only count as a single transformation, regardless to its complexity:)
For more information on how we calculate our quotas -
https://support.cloudinary.com/hc/en-us/articles/203125631-How-does-Cloudinary-count-my-plan-s-quotas-and-what-does-every-quota-mean-
Please sign in to leave a comment.