At a glance

Cost
$0 on the Workers Free plan; static asset requests are free and unlimited
Builds
500 per month, one at a time, 20-minute timeout
Site size
20,000 files, 25 MiB per file
Domains
100 custom domains per project, TLS managed by Pages
Functions
100,000 requests a day, 10 ms CPU per invocation
Best for
Generated or hand-written sites, docs, blogs, landing pages
Watch out
Drag-and-drop uploads cap at 1,000 files; a missing 404.html turns the site into a single-page app

Pages sits in front of Cloudflare's CDN: you upload a folder of finished files, and every request is answered from the nearest data centre with no server of yours involved. There is no database, no runtime, nothing to patch. That is the whole appeal. The site you are reading is built exactly this way — a Python script writes dist/, the folder is uploaded, and the bill has never left zero.

The free plan, number by number

These figures come from Cloudflare's Pages limits page (last updated 5 September 2026) and its Workers pricing page (13 November 2026). They apply to the Workers Free plan, which is what a new account is on.

LimitFree planWhere it bites
Builds per month500Git-integrated projects only; direct uploads are not builds
Concurrent builds1A slow build blocks every other project on the account
Build timeout20 minA big image pipeline or a site-wide link check
Files per site20,000Photo-heavy sites; generated tag or archive pages
Size per file25 MiBVideo, audio, big PDFs — move those to R2
Custom domains100 / projectMulti-market or multi-brand sites
Projects100 / accountNot routinely raised; use Workers for scale
Function requests100,000 / dayAnything dynamic: forms, search, redirects with logic
CPU per invocation10 msHeavy parsing or image work inside a Function
_headers rules100Large sites with per-section security policies
_redirects rules2,1002,000 static plus 100 dynamic, combined
Preview deploymentsUnlimitedServing stale or private previews you forgot about

Two facts matter more than the table. First, requests for static assets are free and unlimited — the expensive part of hosting a normal site, bandwidth, is not metered here at all. Second, a Function is billed as a Worker, so the 100,000 requests a day is a Workers Free limit, and only applies if you add dynamic code. A purely static site never touches it.

One limit that is not in the table: Cloudflare caps how many new Pages projects you can create in your first 48 hours on the service. If project creation is blocked, it lifts by itself once that window passes. It is an anti-abuse measure, not a plan restriction.

Two ways to get files in, and why it matters

Pages offers a Git integration and a Direct Upload. Pick once: a Direct Upload project cannot be switched to Git later. You would have to create a new project, which means a new pages.dev hostname and re-attaching the domain.

Git integration builds on every push: 500 builds a month on the free plan, one at a time, each with 20 minutes to finish. Direct Upload skips building entirely — you upload the output folder — and the same project can then be updated by either the dashboard or the CLI.

Upload methodFilesPer fileNotes
Wrangler CLI20,00025 MiBA folder of assets; zip files are not supported
Dashboard drag and drop1,00025 MiBZip or folder — the 1,000-file cap is the trap

That 1,000-file cap is the difference that catches people. A generated site with a page per tag, an archive and images can cross 1,000 files long before it crosses 20,000. If a drag-and-drop upload seems to finish but pages are missing, count the files first.

With Wrangler, the deploy is two commands:

npx wrangler pages project create
npx wrangler pages deploy dist --project-name=my-site

If you skip project create, pages deploy creates the project for you and asks for a production branch name. Either way the production deployment lands on <project>.pages.dev. Add --branch=<name> to push a preview instead.

Custom domains: apex and subdomain behave differently

A subdomain is the easy case: add the domain in the Pages project, then point a CNAME at <project>.pages.dev at your DNS provider. If the domain is already a Cloudflare zone, the record is created for you.

An apex domain (example.com) has a harder requirement: the zone must be on the same Cloudflare account as the Pages project, with the domain's nameservers pointed at Cloudflare, so Cloudflare can create the CNAME at the apex itself. There is no way around this with a plain CNAME at another DNS provider, because a CNAME at an apex conflicts with the zone's other records.

Order matters. Add the custom domain in the Pages dashboard first, then let the DNS record be created. Manually adding a CNAME that points at Pages without associating the domain in the dashboard produces a 522 error — the request reaches Cloudflare, but nothing is bound to that hostname to answer it.

TLS is handled by Pages, and it is worth knowing what you cannot control: the minimum TLS version and cipher suites are managed by Pages for the custom hostname, and the zone's own settings for those do not apply. A CAA record on the domain also matters — if it does not allow the certificate authorities Cloudflare uses, issuance fails and the domain stays inactive.

Proxied domain, two caches. When the custom domain is a Cloudflare zone, requests pass through the zone before they reach Pages. Your WAF, redirect rules and Cache Rules apply first, and a Cache Rule can serve a stale response after a new deployment. Pages' own cache is separate; if a deploy seems not to have taken effect, check the zone's cache before rebuilding.

Caching defaults you should not fight

Cloudflare's own guidance is to leave caching alone on Pages, and it is right for a normal site. The defaults:

  • Assets stay cached at the edge until the next deployment; the per-data-centre TTL is one week, and assets can be evicted sooner.
  • Every 200 response carries an ETag. The browser sends it back as If-None-Match, and Pages answers 304 Not Modified when it matches.
  • HTML and other cacheable assets are served with Cache-Control: public, max-age=0, must-revalidate — revalidated on every visit, which is exactly what you want for pages that change on deploy.
  • Gzip or Brotli is applied whenever possible.

The one place custom caching pays is fingerprinted assets: a CSS or JS file with a content hash in its name can be cached for a year, because a change produces a new filename.

/assets/*
  Cache-Control: public, max-age=31536000, immutable

That is a _headers file — a plain text file in the output directory, not served itself, with rules applied in file order. Up to 100 rules, and 2,000 characters per line. Two behaviours to know before you write one:

  • Repeated headers are joined, not replaced. Set Cache-Control twice for the same path and you get both directives in one header, which per RFC 9111 can make the response stale in ways you did not intend.
  • To override, detach first. Put a line with ! Cache-Control in the narrower block, then set the value again. The detach only removes what earlier rules added, so the narrower rule has to come after the broader one.

Also: _headers does not apply to responses generated by Pages Functions. If you add server-side code, set its headers in the Function.

Four things that break a small site

  1. No 404.html, no 404. Without a top-level 404.html, Pages assumes a single-page app and serves the root document for any unknown path — with a 200. Every mistyped URL then looks like a real page to a crawler. Ship a 404 file even on a five-page site.
  2. A subdirectory that shadows a page. Pages redirects /about/index.html to /about/ and /contact.html to /contact. If you generate both, expect redirects rather than duplicates; if you link to .html URLs, expect one extra hop.
  3. Direct Upload and production branches. A Direct Upload project has no production branch setting in the dashboard. Changing it means calling the Pages API with PATCH on the project.
  4. The 20-minute build, silently. A build that runs long fails without deploying, and on the free plan it also blocks the account's only build slot until it times out.

What it costs when you outgrow it

Two different upgrades, and it helps to know which one you would need:

You needProductPrice
More builds, files or concurrent buildsPages on a paid planPro: 5,000 builds/month, 5 concurrent; Business: 20,000 builds, 20 concurrent. Paid plans also allow 100,000 files per site with an environment variable set.
More dynamic requestsWorkers Paid$5/month minimum: 10 million requests and 30 million CPU-ms included, then $0.30 per million requests and $0.02 per million CPU-ms.
Files over 25 MiBR2Serve them from a public R2 bucket, ideally on a subdomain

For a text site the realistic ceiling is not bandwidth or requests — it is the 20,000-file and 25 MiB limits, and neither is close for anything made of pages. When this site eventually adds thousands of generated pages, the file count is what will need watching, not the traffic.

The setup, in order

  1. 01 · build Generate a clean output folder

    One folder, no sources, no drafts. Add 404.html, robots.txt, sitemap.xml and _headers to it.

  2. 02 · deploy Wrangler or drag and drop

    Under 1,000 files, either works. Above that, use Wrangler — the dashboard will quietly refuse the rest.

  3. 03 · domain Add in the dashboard, then DNS

    Subdomain: CNAME to project.pages.dev. Apex: the zone must be on the same account with Cloudflare nameservers.

  4. 04 · verify Check the headers, not just the page

    curl -I https://your-domain/ should show your security headers and an ETag; a second request with If-None-Match should return 304.

  5. 05 · repeat Redeploy, purge nothing

    A new deployment replaces the edge cache for the files it contains. Only a zone-level Cache Rule makes purging necessary.

Sources and checks

Checked 17 November 2026. Free-tier limits change; re-read the limits page before you plan around a number.