Each newly processed asset, original upload or transformation, counts toward your Transformations quota. For more information see:
Below are some operations/features which may result in an unintentional charge of your Transformations quota.
- Initial migration: This process, usually consists of a high volume of uploads.
- Repeat uploads: Bugged upload-scripts may sometime repeatedly upload the same image over and over again, resulting in an extra Transformations charge (the default behaviour of an upload action is to overwrite existing resources).
- Failing uploads: Sometimes, due to corrupted files, uploads may fail in a relatively advanced stage when Cloudinary tries to process the file. This can result in a charged Transformation.
- Default images: Incorrectly utilizing our default-image feature may result in the unnecessary creation of placeholder images which are also counted against your Transformations quota. For example, frequently issuing requests to images before it's actually uploaded.
- Multipage/GIF/Video files: Charges for processing these files are made according to their length, and not only once as for images.
- Auto formatting: Utilizing the Auto Format feature (
f_autofor URLs) may result in the generation of up to 4 images per transformation (original format, webp, awebp and wdp)
- Responsive design: Taking advantage of our Responsive tool for supporting auto
dpr, may result in a high number of derived images that are generated for every transformation in order to provide for different device displays. This can also be tuned as described here.
Note that Cloudinary's features are very useful and shouldn't be avoided, just make sure to understand how they are charged beforehand to avoid surprises (their benefits generally far outweigh their costs).
Finally, note that monthly quotas (i.e. Transformations and Bandwidth) are counted within a last-30-days rolling window, therefore they never actually reset but are updated every day.
Feel free to contact our support for any question that arises.