Cloudflare Pages limits: what the free plan includes

It is Friday, 4:50 p.m., and your team is fixing the last price on the site before a campaign. Every tweak triggers a new deployment, and suddenly the dashboard says there are no builds left. It happens less than it seems, but almost always because the limits were never read in advance.

Cloudflare Pages is generous on the free plan, and it pays to know exactly where the ceiling is.

What are the limits of the Cloudflare Pages free plan?

The free plan allows 500 builds per month, one build at a time, 20,000 files per site and 100 custom domains per project. According to the Cloudflare limits documentation, this is how the plans compare:

Limit	Free	Pro	Business
Builds per month	500	5.000	20.000
Concurrent builds	1	5	20
Files per site	20.000	100.000	100.000
Domains per project	100	250	500

Projects per account are 100 and are not routinely increased. If you are still evaluating whether all this suits you, first read what the Cloudflare free plan includes.

What happens if my site is very heavy?

No file can exceed 25 MiB, and a build is cut off after 20 minutes. The documentation puts it this way: the maximum size for a single site asset is 25 MiB, and builds time out after 20 minutes. For a corporate website this almost never gets in the way, except with videos, PDF catalogs or unoptimized images.

The practical fix: compress and convert your images (how to choose WebP, AVIF and write the alt text) and host long videos on a video service, not inside the site.

Common mistake: uploading a 40 MB PDF or video to the repository and finding out the deployment fails. Check the weight of each file before you commit, not after you see the error.

How many redirect and header rules fit?

You can have 2,000 static redirects plus 100 dynamic ones, and 100 header rules per file. Each individual header can be up to 2,000 characters, according to the same limits page. These numbers are roomy for almost any small business, but if you are coming from an old site with thousands of URLs, plan the redirects carefully: here is how to do it in the _redirects file and how to set up cache and security headers.

What are Pages preview deployments and who can see them?

They are temporary versions of your site that Cloudflare creates when you open a pull request or push a new branch, and they are public by default. The preview deployments documentation explains that each one has a unique URL shaped like <hash>.<project>.pages.dev and a branch alias. Pull requests from forks do not generate a preview.

Preview deployments and users are unlimited, according to Cloudflare. That said, every new branch creates a deployment, so do not open branches out of habit and check in your dashboard how your build quota is being used.

Can Google index a preview deployment?

Not by default: every preview sends the X-Robots-Tag: noindex header. You can check it by running curl -I on the URL and looking for that line. Even so, the URL is public to anyone who has it, so do not put prices or content there that you do not want to show yet.

If you need real privacy, go to Workers & Pages, open your project, go to Settings, General and turn on the access policy. Note that this policy protects only previews, not your pages.dev domain or your own domain.

How do I look after my 500 builds of the month?

Group small changes into a single push and review in a preview before merging. One build for every comma fix burns quota for no value. If you publish content daily, 500 builds are plenty, but if you connect automations that deploy on every event, do the math. And if you are coming from another platform, read how to migrate from WordPress to Pages without losing SEO.

In short

That Friday at 4:50 p.m. is solved by having the numbers at hand: 500 builds, 20,000 files, 25 MiB per file and public previews with noindex. Knowing them lets you publish calmly and decide when it is worth moving to a paid plan. If you want us to set it up for you, see our hosting and domains service.