--- name: Registry-registry_quota title: Managing quota limits for storage and pull traffic in Container Registry description: You can limit the amount of storage and pull traffic that can be used in your IBM Cloud account by setting and managing custom quota limits in IBM Cloud® Container Registry. last-updated: 2025-10-10 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/Registry?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Managing quota limits for storage and pull traffic in Container Registry {: #registry_quota} You can limit the amount of storage and pull traffic that can be used in your IBM Cloud account by setting and managing custom quota limits in IBM Cloud® Container Registry. {: shortdesc} ## Setting quota limits for storing and pulling images {: #registry_quota_set} {: help} {: support} You can limit the amount of storage and pull traffic to your private images by setting your own quota limits. When you upgrade to the IBM Cloud Container Registry standard plan, you benefit from unlimited amount of storage and pull traffic to your private images. To avoid exceeding your preferred payment level, you can set individual quotas for the amount of storage and pull traffic. Quota limits are applied to all [namespaces](#x2031005){: term} that you set up in IBM Cloud Container Registry. If you're using the free service plan, you can also set custom quotas within your free amount of storage and pull traffic. To set a quota, complete the following steps. 1. Log in to IBM Cloud. ```txt ibmcloud login ``` {: pre} 2. Review your current quota limits for storage and pull traffic. ```txt ibmcloud cr quota ``` {: pre} Your output looks similar to the following example. ```txt Getting quotas and usage for the current month, for account ' Account'... QUOTA LIMIT USED Pull traffic 5.1 GB 0 B Storage 512 MB 511 MB OK ``` {: screen} 3. Change the quota limit for storage and pull traffic. To change the pull traffic usage, specify the **traffic** option, and replace `TRAFFIC_QUOTA` with the value in megabytes that you want to set for the pull traffic quota. If you want to change the amount of storage in your account, specify the **storage** option, and replace `STORAGE_QUOTA` with the value in megabytes that you want to set. If you are on the free plan, you cannot set your quota to an amount that exceeds the free tier. The free tier allowance for storage is 512 MB and traffic is 5120 MB. {: tip} ```txt ibmcloud cr quota-set --traffic TRAFFIC_QUOTA --storage STORAGE_QUOTA ``` {: pre} The following example sets your quota limit for storage to 600 megabytes, and the pull traffic to 7000 megabytes. ```txt ibmcloud cr quota-set --storage 600 --traffic 7000 ``` {: pre} ## Reviewing quota limits and usage {: #registry_quota_get} {: help} {: support} You can review your quota limits and check your current storage and pull traffic usage for your account. 1. Log in to IBM Cloud. ```txt ibmcloud login ``` {: pre} 2. Review your current quota limits for storage and pull traffic. ```txt ibmcloud cr quota ``` {: pre} Your output looks similar to the following example. ```txt Getting quotas and usage for the current month, for account ' Account'... QUOTA LIMIT USED Pull traffic 5.1 GB 0 B Storage 512 MB 511 MB OK ``` {: screen} ## Staying within quota limits {: #registry_quota_freeup} {: help} {: support} If you exceed the quota limits that are set for your IBM Cloud account, you can free up storage and change your service plan or quota limits so that you can continue pushing and pulling images to and from your namespace. From 1 February 2022, both [tagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#overview_elements_tag) and [untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#overview_elements_untagged) images are charged for. {: important} To free up image storage in your IBM Cloud account, complete the following steps. Depending on the proportions of the image, it might take a while for the image to be removed and for the storage to be available. {: note} 1. Find the names of the images that you want to remove. - To list only tagged images, run the [`ibmcloud cr image-list`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_image_list) command. Combine the content of the **Repository** column (`repository`) and **Tag** column (`tag`) separated by a colon (`:`) to create the image name in the format `repository:tag`. If the listing images command times out, see [Why is it timing out when I list images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeout&format=markdown) for assistance. ```txt ibmcloud cr image-list ``` {: pre} - To list both tagged and untagged images, you must list the images by [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#overview_elements_digest) in all your namespaces of your IBM Cloud account. To list the images by digest, run the [`ibmcloud cr image-digests`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_image_digests) command. Combine the content of the **Repository** column (`repository`) and the **Digest** column (`digest`) separated by an at (`@`) symbol to create the image name in the format `repository@digest`. ```txt ibmcloud cr image-digests ``` {: pre} 2. You can remove images individually, collectively, or by using retention policies. - To remove images individually from your namespace, use the [`ibmcloud cr image-rm`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_image_rm) command. Replace `IMAGE_NAME` with the name of the image that you want to remove. The name must be in the format `repository@digest` or `repository:tag`. If a tag is not specified in the image name, the image that is tagged `latest` is deleted by default. Deleted images are stored in the trash for 30 days. Images that are in the trash don't count toward your quota. You can remove both tagged and untagged images by using the format `repository@digest`. You can remove only tagged images by using the format `repository:tag`. {: note} ```txt ibmcloud cr image-rm IMAGE_NAME ``` {: pre} Where multiple tags exist for the same image digest within a repository, the [`ibmcloud cr image-rm`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_image_rm) command removes the underlying image and all its tags. If the same image exists in a different repository or namespace that copy of the image is not removed. If you want to remove a tag from an image and make sure the underlying image and any other tags remain in place, see [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_&format=markdown#registry_images_untag) command. {: tip} - To remove untagged images collectively from your namespace, use the [`ibmcloud cr image-prune-untagged`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#ic_cr_image_prune_untagged) command, see [Clean up your namespaces by deleting untagged images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention&format=markdown#retention_images_untagged). - To use retention policies, see [Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention&format=markdown). 3. Review your storage quota usage. ```txt ibmcloud cr quota ``` {: pre} 4. To reduce your pull traffic usage, you must wait until the next billing period. To continue pulling images from your namespaces, choose between the following options. - Wait until the next billing cycle starts. - If you have a free plan, [upgrade to the standard service plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#registry_plan_upgrade). - If you already have a standard plan, [set new quota limits for the pull traffic](#registry_quota_set).