Skip to content

Commit b768db9

Browse files
Update download-rate-limit.md (#2)
* Update download-rate-limit.md Added information about how storage is calculated. * Update content/manuals/docker-hub/download-rate-limit.md * Update content/manuals/docker-hub/download-rate-limit.md --------- Co-authored-by: Sarah Sanders <[email protected]>
1 parent 47ac5a4 commit b768db9

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

content/manuals/docker-hub/download-rate-limit.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,7 @@ The following storage and repository limits apply based on your subscription, su
128128
| Team | Unlimited | Unlimited | Unlimited | Up to 50 GB |
129129
| Business | Unlimited | Unlimited | Unlimited | Up to 500 GB |
130130

131+
### How storage is calculated
131132

132133
Private repository storage is calculated on a monthly basis based on the average
133134
storage used throughout the month per namespace. Docker measures your storage
@@ -140,6 +141,10 @@ charged at an on-demand rate. You can [scale your
140141
limit](../subscription/scale.md) or [upgrade](../subscription/change.md) to get
141142
a higher limit.
142143

144+
Docker Hub calculates storage based on each unique image layer (or “digest”) stored within a repository. Only unique layers contribute to your storage usage, which means if multiple images in a single repository share the same layer, you’re only billed once for that layer. However, if the same layer is used across different repositories, it will count separately in each one.
145+
146+
For example, if 10 different repositories use the same digest, you would be billed for the storage of that digest 10 times (once per repository). However, if you have 10 versions of an image within a single repository that uses the same digest, you would only pay for that digest once.
147+
143148
## Pull limit and rate limit
144149

145150
A pull is defined as the following:

0 commit comments

Comments
 (0)