Cloudflare Pages
Static and full-stack site hosting on Cloudflare's network, billed together with Workers compute.
- frontend serverless
- Yes
- $5 / month account minimum
- 348 cities across 100+ countries
Who it suits.
Projects where the entire fixed cost should be a $5 monthly account minimum rather than a per-seat fee, and teams already running on the wider Workers platform. Billing is metered, so cost tracks traffic rather than headcount.
Consider something else if…
Your repository is hosted somewhere other than GitHub or GitLab, or the free plan's 500 builds a month is not enough headroom.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Cloudflare Pages does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Cloudflare Workers and Pages pricing ↗
“By default, users have access to the Workers Free plan.”
Read 2026-09-05 · official docs
Entry paid plan
$5 / month account minimum
Sources (1) →Sources ↓
- Cloudflare Workers and Pages pricing ↗
“The Workers Paid plan includes Workers, Pages Functions, Workers KV, Hyperdrive, and Durable Objects usage for a minimum charge of $5 USD per month for an account.”
Read 2026-09-05 · official docs
Pricing model
Metered usage with a $5 monthly account minimum
Sources (1) →Sources ↓
- Cloudflare Workers and Pages pricing ↗
“The Workers Paid plan includes Workers, Pages Functions, Workers KV, Hyperdrive, and Durable Objects usage for a minimum charge of $5 USD per month for an account.”
Read 2026-09-05 · official docs
Limits
Sites or apps included
100 projects per account (platform-wide, all plans)
Sources (1) →Sources ↓
- Limits ↗
“Cloudflare Pages has a limit of 100 projects per account.”
Read 2026-09-05 · official docs
Monthly visits cap
No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota
Sources (1) →Sources ↓
- Pricing · Cloudflare Pages docs ↗
“On both free and paid plans, requests to static assets are free and unlimited. [...] Requests to your Pages functions count towards your quota for Workers Paid plans, including requests from your Function to KV or Durable Object bindings.”
Read 2026-09-05 · official docs
File or inode limit
100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB
Sources (1) →Sources ↓
- Limits ↗
“Cloudflare Pages sites can contain up to 20,000 files on the Free plan. Paid plans (such as Pro, Business, and Enterprise plans) can have up to 100,000 files per site. [...] The maximum file size for a single Cloudflare Pages site asset is 25 MiB.”
Read 2026-09-05 · official docs
Build minutes
500 builds per month on the Free plan
Sources (1) →Sources ↓
- Cloudflare Pages limits ↗
“Builds per month on the Free plan: 500”
Read 2026-09-05 · official docs
Concurrent builds
5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro
Sources (1) →Sources ↓
- Limits ↗
“Builds table — Free: 1 build at a time, 500 builds per month; Pro: 5 concurrent builds, 5,000 builds per month; Business: 20 concurrent builds, 20,000 builds per month”
Read 2026-09-05 · official docs
Execution
CPU time limit
Up to 30 seconds of CPU time under the Standard usage model, which the Pages docs state Pages supports. CPU time is tracked separately from duration in the Pages Functions metrics dashboard; the same page notes that network-bound work inflates duration but not CPU time. Not plan-differentiated on the page.
Sources (1) →Sources ↓
- Metrics · Cloudflare Pages docs ↗
“Understanding duration on your Function is useful when you are intending to do a significant amount of computation on the Function itself. This is because you may have to use the Standard or Unbound usage model which allows up to 30 seconds of CPU time. Workers on the Bundled Usage Model may have high durations, even with a 50 ms CPU time limit, if they are running many network-bound operations like fetch requests and waiting on responses.”
Read 2026-09-05 · official docs
Managed connection pooling
Supported
Sources (1) →Sources ↓
- Bindings · Cloudflare Pages docs ↗
“Hyperdrive is a service for connecting to your existing databases from Cloudflare Workers and Pages Functions. … PostgreSQL drivers like Postgres.js depend on Node.js APIs. Pages Functions with Hyperdrive bindings must be deployed with Node.js compatibility.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Cloudflare Pages Git integration ↗
“Cloudflare supports connecting Cloudflare Pages to your GitHub and GitLab repositories. Cloudflare will automatically deploy your code every time you push a change to a branch.”
Read 2026-09-05 · official docs
Scheduled jobs
Not supported
Sources (1) →Sources ↓
- Migrate from Pages to Workers · Cloudflare Workers docs ↗
“Cron Triggers | ✅ | ❌ (compatibility matrix column headings: Workers | Pages)”
Read 2026-09-05 · official docs
Infrastructure
Edge network
Supported
Sources (1) →Sources ↓
- The Cloudflare global network ↗
“348 cities”
Read 2026-09-05 · official site
Regions
348 cities across 100+ countries
Sources (1) →Sources ↓
- The Cloudflare global network ↗
“348 cities ... 100+ countries”
Read 2026-09-05 · official site