Download rate limit

What’s the download rate limit on Docker Hub

Docker Hub limits the number of Docker image downloads (“pulls”) based on the account type of the user pulling the image. Pull rates limits are based on individual IP address. For anonymous users, the rate limit is set to 100 pulls per 6 hours per IP address. For authenticated users, it’s 200 pulls per 6 hour period. Users with a paid Docker subscription get up to 5000 pulls per day. If you require a higher number of pulls, you can also purchase an Enhanced Service Account add-on.

Some images are unlimited through our Open Source and Publisher programs.

See Docker Pricing and Resource Consumption Updates FAQ for details.

Definition of limits

A user’s limit is equal to the highest entitlement of their personal account or any organization they belong to. To take advantage of this, you must log in to Docker Hub as an authenticated user. For more information, see How do I authenticate pull requests. Unauthenticated (anonymous) users will have the limits enforced via IP.

  • A pull request is defined as up to two GET requests on registry manifest URLs (/v2/*/manifests/*).
  • A normal image pull makes a single manifest request.
  • A pull request for a multi-arch image makes two manifest requests.
  • HEAD requests aren’t counted.

How do I know my pull requests are being limited

When you issue a pull request and you are over the limit for your account type, Docker Hub will return a 429 response code with the following body when the manifest is requested:

You have reached your pull rate limit. You may increase the limit by authenticating and upgrading:

You will see this error message in the Docker CLI or in the Docker Engine logs.

How can I check my current rate

Valid manifest API requests to Hub will usually include the following rate limit headers in the response:


These headers will be returned on both GET and HEAD requests. Note that using GET emulates a real pull and will count towards the limit; using HEAD won’t, so we will use it in this example. To check your limits, you will need curl, grep, and jq installed.

To get a token anonymously (if you are pulling anonymously):

$ TOKEN=$(curl "" | jq -r .token)

To get a token with a user account (if you are authenticating your pulls) - don’t forget to insert your username and password in the following command:

$ TOKEN=$(curl --user 'username:password' "" | jq -r .token)

Then to get the headers showing your limits, run the following:

$ curl --head -H "Authorization: Bearer $TOKEN"

Which should return headers including these:

ratelimit-limit: 100;w=21600
ratelimit-remaining: 76;w=21600

This means my limit is 100 pulls per 21600 seconds (6 hours), and I have 76 pulls remaining.

Remember that these headers are best-effort and there will be small variations.

I don’t see any RateLimit headers

This could be because the image or your IP is unlimited in partnership with a publisher, provider, or an open-source organization. Pulling that image won’t count toward pull limits if you don’t see these headers. However, users with a paid Docker subscription pulling more than 5000 times daily require a Service Account subscription.

I’m being limited to a lower rate even though I have a paid Docker subscription

To take advantage of the higher limits included in a paid Docker subscription, you must authenticate pulls with your user account.

A Pro, Team, or a Business tier doesn’t increase limits on your images for other users. See our Open Source, Publisher, or Large Organization offerings.

How do I authenticate pull requests

The following section contains information on how to log into on Docker Hub to authenticate pull requests.

Docker Desktop

If you are using Docker Desktop, you can log into Docker Hub from the Docker Desktop menu.

Click Sign in / Create Docker ID from the Docker Desktop menu and follow the on-screen instructions to complete the sign-in process.

Docker Engine

If you are using a standalone version of Docker Engine, run the docker login command from a terminal to authenticate with Docker Hub. For information on how to use the command, see docker login.

Docker Swarm

If you are running Docker Swarm, you must use the -- with-registry-auth flag to authenticate with Docker Hub. For more information, see docker service create. If you are using a Docker Compose file to deploy an application stack, see docker stack deploy.

GitHub Actions

If you are using GitHub Actions to build and push Docker images to Docker Hub, see login action. If you are using another Action, you must add your username and access token in a similar way for authentication.


If you are running Kubernetes, follow the instructions in Pull an Image from a Private Registry for information on authentication.

Third-party platforms

If you are using any third-party platforms, follow your provider’s instructions on using registry authentication.

Other limits

Docker Hub also has an overall rate limit to protect the application and infrastructure. This limit applies to all requests to Hub properties including web pages, APIs, image pulls, etc. The limit is applied per-IP, and while the limit changes over time depending on load and other factors, it’s in the order of thousands of requests per minute. The overall rate limit applies to all users equally regardless of account level.

You can differentiate between these limits by looking at the error code. The “overall limit” will return a simple 429 Too Many Requests response. The pull limit returns a longer error message that includes a link to this page.