Cloudinary offers tremendous capabilities for managing your online media, starting with our free-to-use plans. Our paid plans include greatly increased usage quotas, and detailed below is an explanation of what the different quotas mean and how your account's usage is calculated.
- Transformations - Transformations are counted for newly processed assets including original asset uploads and the creation of derived versions of images and videos. Repeated requests to deliver the same derived / transformed asset do not count towards your transformations usage multiple times, because we store the result of the transformation in your account's storage and deliver that on subsequent requests.
- Managed Storage - The accumulated file size of all of assets in your Cloudinary account's storage, including derived versions created using transformation options, and backup copies of assets if you use the backup functionality and store your backups in Cloudinary's storage (more information).
- Net Viewing Bandwidth - Total calculated bandwidth of content delivered from your account within the last 30 days.
- Total Images & Videos (this limit applies to some older plans) - Represents the total number of resources maintained by Cloudinary at a given moment. This includes both original resources and their derivatives (e.g. thumbnails).
On our credits plans, the combined usage of your account is expressed as a number of "credits" calculated based on your usage of transformations, storage, and bandwidth. Your account's usage in credits is compared to your account's quota, unlike our older plans which had separate limits for different types of usage.
Also note that monthly quotas (i.e. Transformations and Bandwidth) are being counted within a last-30-days rolling window, therefore it never actually reset but updates every day.
Q: How are uploads counted toward my quota?
A: Every uploaded file increases your Total Images & Videos, Storage, and Monthly Transformations. Bandwidth is not counted for uploads or for bandwidth used by Cloudinary to copy an asset from a remote storage service or server. Transformations will not be counted for uploads of `Raw` resource-type uploads.
Q: How does enabling backup affect my Storage?
A: When a backup is enabled on your settings page, every resource (Originals only) is backed-up and counts toward your Storage Utilization. If you choose to backup to your own AWS S3 or Google Cloud Storage bucket, your Storage usage will not increase.
Q: For images, will complex transformations be counted as multiple Transformations?
A: A transformation, no matter how complex it is (even when using multiple chained transformations), is counted as a single transformed resource.
Q: How do videos, animated files, and files containing multiple pages count towards my Transformations quota?
A: Such files, when transformed, are counted based on the dimensions and number of frames:
- Animated images (e.g. GIF)- 1 transformation, plus an additional transformation for every 10 frames.
- Animated images to video - Every 5 frames = 1 transformation.
- Multi-page PDF assets - 1 transformation plus an additional transformation for every 10 pages.
- SD Video - 1 second = 2 transformations
- HD Video - 1 second = 4 transformations (Frame contains over 921,600 of total pixels, e.g., 1920 x 1080)
- Audio - 1 second = 0.1 transformations
Note that when uploading an image or video asset, 1 Transformation is automatically counted for the creation and processing of the original file.
Q: How do "Fetch"-ed resources count toward my quotas?
A: When using our Remote Image Fetch URL feature, the fetched image will be stored in your Cloudinary account and counted towards your Storage and Total Images. If the fetched image was also transformed within the URL, a Transformation will be counted for the creation of the derived copy of the image. Fetched images are not backed-up, so you if you use Cloudinary's backup feature, your Storage will not be additionally affected by fetched images.
Q: What is "Net Viewing Bandwidth" and how is bandwidth calculated?
A: For every viewed/downloaded asset, we count the data used to deliver the requested copy of the asset. When you use transformation options to reduce the file size of a delivered asset, your bandwidth count is based on the size of the actual copy delivered, not the size of the original asset. We do not count "Midgress" bandwidth, charge extra per request, for traffic in different geographical regions, for HTTPS requests or for traffic to origin. There is also no additional cost for CDN invalidations, if requested when you delete or overwrite an asset.
Q: When do my Transformation & Bandwidth quotas reset to zero?
A: Your Transformations and Bandwidth usage is based on the last 30-days of activity in your account and does not reset to '0' on a fixed period like a calendar or billing month. Your 'current' usage goes up and down based on the recent activity in your account, and should remain within your account's quota.
Q: How are default image placeholders counted towards my usage?
A: Placeholder resources contain derived versions of the default image which were previously generated. These images count against your account's number of assets and storage calculations. Also for every unique transformation, a Transformation is consumed when the derived asset is created.
Q: How does using the automatic format transformation
f_auto affect my usage?
A: Transformations are counted for each derived image created. Using the automatic format transformation can create multiple derived assets for a single delivery URL because
f_auto will deliver assets in different file formats based on the formats supported by the browser making the request.
Q: How does using add-ons work?
A: Each add-on offered by Cloudinary has its own quota as well. When using a transformation or making a request that uses an add-on, the usage counts towards the standard quotas as mentioned above but is also counted towards the add-on's specific quota.
Q: What other processes could be counted towards the "transformations" quota?
A: Other than uploads and derived resources generations, using the
explicit API to perform processes like extracting image metadata, colors, pHash, and others are also counted towards the "transformations" quota. There's a more specific guide available in our Transformation Counts documentation.