Each time you push new code to your Git repository, Pages will build and deploy your site. You can deploy up to 500 times per month on the Free plan. Refer to the Pro and Business plans in if you need to deploy more frequently.
Builds will timeout after 20 minutes.
Pages projects can have up to 10,000 active deployments. These are the most recent 10,000 deployments, excluding aliased deployments and production. Inactive deployments will return a
522 error and will need to be redeployed. All deployments are visible in the Cloudflare dashboard, but only the most recent 10,000 will be able to serve traffic.
A Cloudflare Pages project can be attached to a certain number of domains per plan.
Pages uploads each file on your site to Cloudflare’s globally distributed network to deliver a low latency experience to every user that visits your site. Cloudflare Pages sites can contain up to 20,000 files.
The maximum file size for a single Cloudflare Pages site asset is 25 MiB.
_headers file can have a maximum of 100 header rules.
_redirects file can have a maximum of 2,000 static redirects and 100 dynamic redirects, for a combined total of 2,100 redirects. It is recommended to use when you have a need for more than the
_redirects file supports.
Your Pages site can be managed by an unlimited number of users via the Cloudflare dashboard. Note that this does not correlate with your Git project – you can manage both public and private repositories, open issues, and accept pull requests via without impacting your Pages site.
Cloudflare Pages supports deploying 100 sites to your account. If you need to raise this limit, contact your Cloudflare account team.
In order to protect against abuse of the service, Cloudflare may temporarily disable your ability to create new Pages projects, if you are deploying a large number of applications in a short amount of time. Email if you need this restriction removed.