the writing tool & vendor comparisons 12 min

Cloudflare Pages Pricing and Free Tier Limits in 2026

Pages serves static files free with no cap. The bill starts when Functions run, because those are Workers requests. Here's what each plan and limit covers.

Line-art browser window with a cloud above it and a stack of file cards beside it

Cloudflare Pages charges nothing for serving static files, on Free or paid plans: Cloudflare's Functions pricing doc says requests to static assets are free and unlimited. The money question begins when Functions run, because those are billed as Workers requests, with 100,000 a day on the Workers Free plan and a $5 a month Workers Paid plan above that. Builds, files, projects and domains each have their own caps. Below: what each plan includes, which product bills which usage, the current limits, three illustrative workloads priced from published rates, and a straight view on Netlify and Vercel.

What Pages includes on Free, and what paying changes

Pages is available on all Cloudflare plans, according to the Pages overview. You can deploy from a Git provider, push prebuilt assets with Direct Upload, or scaffold a project from the command line. There is no separate checkout for the hosting itself.

What changes between plans is the ceiling on a small set of things. Per the Pages limits page, Free gives you:

  • 1 build at a time, and 500 builds a month
  • 100 custom domains per project
  • 20,000 files per site
  • 25 MiB for a single asset

Pro lifts that to 5 concurrent builds, 5,000 builds a month and 250 domains per project. Business goes to 20 concurrent builds, 20,000 a month and 500 domains. Enterprise also sits at 500 domains, and Cloudflare tells you to contact your account team if you need more.

Files are the newer change. A changelog entry dated 23 January 2026 raised paid plans to 100,000 files per site, up from 20,000. Free stays at 20,000. It isn't automatic: you set the environment variable PAGES_WRANGLER_MAJOR_VERSION=4 in your project settings to switch it on.

Two subscriptions, not one

This is the point that trips people up. The build, domain and file caps follow your Cloudflare plan (Free, Pro, Business, Enterprise). Functions usage follows your Workers plan, which is a different line on the bill. One has nothing to do with the other, so upgrading one doesn't change the other.

On price, I'll be careful. The official Pages docs I'm citing list the limits per plan but don't print a Pro price. One third-party comparison quotes $20 a month for Pages Pro, but that figure isn't in Cloudflare's own docs here, so check the Cloudflare plans page before you budget around it. The $5 figure you'll see elsewhere belongs to Workers Paid, which is where Functions are billed.

One naming oddity: the Pages overview describes the Free cap as 500 deploys a month, while the limits page says 500 builds. Treat the limits page as the authority. Same number, different noun.

Static delivery versus Functions: which product bills what

This is the section that saves you from a surprise invoice. Pages is a front door onto two different meters.

A cloud holding a browser window, with a stack of coins and an open empty gift box in front of it

Static assets. If a request is answered with a file from your deployment, it doesn't invoke Functions, and the docs say it's free and unlimited on both free and paid plans. A fully static Astro build is just files, so a viral day costs nothing extra on this meter.

Functions. The moment a request hits a Function, whether middleware, an API route or server rendering, it's a Workers request. The Pages Functions pricing doc says exactly that: requests to your Functions are billed as Cloudflare Workers requests. Cloudflare's own GA announcement put it as Functions being special Workers, with unlimited free static requests and billing primarily on dynamic ones.

The Workers numbers, from the Workers pricing page:

  • Free: 100,000 requests per day, no charge for duration, 10 milliseconds of CPU time per invocation.
  • Standard (Workers Paid): $5 USD a month minimum per account, 10 million requests included then $0.30 per additional million, plus 30 million CPU milliseconds included then $0.02 per additional million.

On Free, Pages Functions and plain Workers share that one daily pool. The Pages doc's own example is blunt: 50,000 Functions requests plus 50,000 Workers requests uses the full 100,000, and the allowance resets at midnight UTC.

The Workers Paid plan also states there are no extra charges for data transfer or throughput. Bandwidth isn't a line item. Subrequests your code makes aren't billed either, though the Pages limits page does say requests from a Function to KV or Durable Object bindings count towards your Workers quota. Read both pages together if your Functions lean on bindings.

The Workers Caching catch

If you turn on Workers Caching, the Workers pricing footnote says cache-served requests, static assets included, are billed at the same per-request rate as Worker-invoking requests. Leave it off for a plain static site and the free-and-unlimited rule holds. Switch it on and you've changed the bill.

Plan-and-usage table

This table is a summary of the cited docs, not a quote. Rates change, so confirm on the linked pages.

UsageBelongs toFreePaidSource
Static asset requestsPagesFree, unlimitedFree, unlimitedPages Functions pricing
Builds per monthPages (Cloudflare plan)500Pro 5,000, Business 20,000Pages limits
Concurrent buildsPages (Cloudflare plan)1Pro 5, Business 20Pages limits
Files per sitePages20,000100,000Changelog, 2026-01-23
Functions requestsWorkers100,000 per day, 10 ms CPU10M a month included, then $0.30 per millionWorkers pricing
Functions CPU timeWorkersIncluded in daily limits30M ms included, then $0.02 per million msWorkers pricing
R2 storage, if usedR2Own meterOwn meterCheck Cloudflare's R2 pricing

On R2: it's a separate product with its own storage and operation charges. The Pages overview describes it as object storage without the costly egress fees of typical cloud storage. One third-party write-up quotes $0.015 per GB-month, $0 egress, and $4.50 and $0.36 per million Class A and Class B operations, but I haven't matched those to Cloudflare's R2 docs, so I'm not building any example on them.

Build, file, project and deployment limits

Most of these are on the Pages limits page. Convika, a third-party comparison, quotes that page as last updated 5 September 2026 and the Functions pricing page as last updated 8 September 2026, which gives you a rough sense of how fresh the figures are. Still, check the pages themselves.

Builds

Builds time out after 20 minutes. Concurrency is counted per account, not per project, so five projects on Free still share a single build slot. That matters if you run several sites from one account.

Files and sizes

A site can hold 20,000 files on Free and 100,000 on paid plans, with the environment variable above. A single asset can't exceed 25 MiB. A big image library or a video file is the usual way to trip the size cap, and a huge generated archive of tiny pages is the usual way to trip the file count.

Headers and redirects

  • _headers: maximum 100 rules, and an individual header can be at most 2,000 characters. Cloudflare suggests Pages Functions for larger headers.
  • _redirects: 2,000 static plus 100 dynamic, 2,100 combined. Past that, the docs point you to Bulk Redirects.

Projects, users and previews

There's a cap of 100 projects per account, and the docs say it isn't routinely increased. Cloudflare also limits how many new projects you can create in your first 48 hours of using the service, which lifts on its own once the window passes. Preview deployments are unlimited in number, and so are the users who can manage a site.

For more than 100 sites, Cloudflare points to Workers for Platforms, or to Workers Static Assets, where paid plans support up to 500 Workers per account, each serving up to 100,000 static files.

A pre-deploy check for an Astro site

  1. Count the files in your build output folder and compare against 20,000 (or 100,000 on a paid plan with the version variable set).
  2. Find your largest asset and confirm it's under 25 MiB.
  3. Count redirect rules, including any generated by a plugin, against the 2,100 combined cap.
  4. Time a clean build locally, then allow for a slower CI machine against the 20-minute timeout.
  5. Decide whether any route needs server code. If none does, you're on the free static meter.

Three example workloads

These are illustrative. The assumptions are mine, labelled as such. The rates come from the cited Cloudflare docs, and I haven't measured any of these on a real site.

Workload A: static brochure site

Assumptions: an Astro site of a few dozen pages, no Functions, rebuilt a handful of times a month.

Static requests are free and unlimited, builds sit far below 500, and file count is nowhere near 20,000. Cost on the Pages side is nothing, whatever the traffic. This is the case Pages was made for, and it's hard to beat on price.

Workload B: content site with frequent builds

Assumptions: a publishing site that rebuilds on every merged edit, with 20 merges a day over a 30-day month, and no server code.

That's 600 builds, which is over the Free cap of 500. Bandwidth isn't the issue here. Builds are. On Free you'd also be running them one at a time, with a 20-minute timeout on each. The Pro cap is 5,000 builds a month with 5 concurrent, which covers the scenario with plenty of room, but then you're paying for the Cloudflare plan whose price you need to confirm on the plans page.

Before paying, try batching. Merge edits in groups and a 600-build month drops under 500 without changing anything else. Also watch the file count: a content site that has grown past 20,000 generated pages needs a paid plan plus the version variable, whatever its build cadence.

Workload C: dynamic site with Functions

Three cases, all priced from the Workers pricing examples.

C1, small and dynamic, on Free. Keep Functions traffic under 100,000 requests a day and CPU under 10 ms per invocation, and the Workers side costs nothing. Go over the daily pool and you've outgrown Free, because the allowance is the allowance.

C2, mostly static with a dynamic edge. Take 15 million requests a month where 80% (12 million) are static assets and the rest invoke a Function averaging 7 ms CPU. Cloudflare's own Example 2 puts this at $5.00 a month, the subscription alone. The dynamic requests sit inside the 10 million included, and the CPU milliseconds, request count times 7 by my arithmetic, sit inside the 30 million included.

C3, fully dynamic at volume. Take 100 million requests a month, every one invoking a Function at 7 ms CPU. Cloudflare's Example 4 totals $45.40: $27.00 for requests plus $13.40 for CPU time on top of the minimum subscription charge. For comparison, Example 1, 15 million requests, all dynamic, 7 ms, comes to $8.00.

Notice what drives the number. It's the share of requests that invoke code. Moving a route from a Function to a pre-rendered file is the cheapest optimisation on the platform.

R2, if you add it: uploads, media or generated files stored in R2 are billed on R2's own meter, not as part of any figure above. Price it separately from Cloudflare's R2 page.

When Pages is a better or worse fit than Netlify and Vercel

Where Pages wins

Static and mostly static sites. Free unlimited static requests with no bandwidth meter is a real advantage, and unlimited users on a site means no per-seat bill climbing as your team grows. The entry paid plan, per a third-party 2026 comparison updated 21 October 2026, is $5 a month (Workers Paid) against $20 a month for Netlify Pro and $20 per user per month for Vercel Pro. That source also quotes Vercel functions at $0.60 per million invocations against Cloudflare's $0.30 after 10 million included. I'd treat those as directional, since I can't see Vercel's own pricing page from here.

Where Pages loses

  • Agencies with many client sites. 100 projects per account, not routinely raised, is a hard ceiling. Workers Static Assets is the workaround Cloudflare names.
  • Frequent builds on Free. 500 builds a month and one at a time can hurt a busy content team.
  • Heavy server rendering. A framework doing server work on every route is a Workers cost model, whatever the dashboard says. One secondary source says Cloudflare's own direction in 2026 pushes new full-stack projects towards Workers with static assets rather than Pages Functions. I'd read the current Cloudflare docs before starting a server-heavy build on Pages.
  • Next.js-centric teams. Vercel's first-party support is the reason people pay it, and Pages doesn't try to match that.

The Netlify numbers are messier

Sources disagree here because Netlify changed its pricing. Render's roundup lists Netlify Free as $0 with 300 credits a month and a hard limit, Personal at $9 a month with 1,000 credits, and Pro from $20 a month with 3,000 credits. Older comparisons still talk in build minutes. Our Netlify free tier limits post covers that side, and the head-to-head posts are Cloudflare Pages vs Netlify and Cloudflare Pages vs Vercel. There's also a Cloudflare Pages overview on this site.

One caveat on sources: a Vibe Coder Blog post quotes $0.15 per million after 10 million requests. That conflicts with Cloudflare's published $0.30 per additional million, so I've used the official rate throughout.

If you've decided to move a live site, the site migration page is where to start. Do the file-count and redirect checks above first, since those are the limits that bite during a move.

FAQ

Is Pages bandwidth actually unlimited?

For static asset requests, Cloudflare's docs say requests are free and unlimited on both free and paid plans. Workers Paid also says there are no extra charges for data transfer or throughput. The exception to watch is Workers Caching: with it enabled, cache-served requests are billed at the per-request rate.

What should I do if I keep hitting 500 builds a month?

First, cut the number of builds. Batch merges, and stop building on every tiny commit. If that isn't practical, the next step up is a paid Cloudflare plan: Pro allows 5,000 builds a month and 5 at once. Check the current price on the plans page, since the $20 figure from one third-party source isn't in the docs cited here.

Do Functions requests to KV or Durable Objects cost extra?

The Pages limits and Functions pricing pages both say requests from your Function to KV or Durable Object bindings count towards your Workers quota. The Workers pricing page separately says subrequests from a Worker aren't billed. The two read differently, so confirm with the current docs before modelling a binding-heavy site. KV and R2 may also have their own allowances and charges.

Does the 100,000 daily request allowance cover my whole account?

Yes, it's a shared Workers Free allowance. Pages Functions requests and ordinary Workers requests draw from the same 100,000 a day, resetting at midnight UTC. Putting a frontend on Pages doesn't give your server endpoints a separate free allowance.

The sharpest fact in all of this: static files cost nothing to serve, but anything that runs code is a Workers request on its own meter. Price your build count, your file count and your Functions share separately, and check each cap against the current docs before you commit.

this post in the tree

Need this done, not just read?

Discuss your website Book 30 minutes