Why does my account's usage report show a relatively high transformation rate?

Each newly processed asset, original upload, and transformation counts toward your transformation usage. For more information see: How are transformations counted?

The following operations and features may result in unintentional transformation usage:

• Initial migration: This process usually entails a high volume of uploads.
• Repeat uploads: Misconfigured upload scripts that repeatedly upload the same asset may result in additional transformation charges. If the script uses the same public ID for each upload, the existing asset is overwritten instead of creating additional assets.
• Failing uploads: Corrupted or invalid files may fail during processing, sometimes after transformation processing has already begun. In these cases, the upload may still count toward your transformation usage.
• Default images: Incorrect use of the default image placeholder feature may create unnecessary placeholder images that count toward your transformation usage. For example, repeated requests for an image before it has been uploaded may generate placeholder images unnecessarily.
• Multipage/GIF/Video files: Processing these files incurs charges per second or per frame, and not only once as for images.
• Auto formatting: Using the auto format feature (f_auto in delivery URLs) may generate up to four derived assets per transformation (for example, the original format, WebP, animated WebP, and WDP).
• Responsive design: Using responsive features such as automatic width and DPR may generate a large number of derived assets for a single transformation to support different device displays. You can tune this behavior by overriding default values.

Also note that Cloudinary usage quotas, such as transformations and bandwidth, are calculated using a rolling 30-day window. Quotas don't reset at the beginning of each month, but update continuously based on usage during the previous 30 days.

If you have any questions, feel free to contact support.