Netlify vs Cloudflare Pages
A comparison of Netlify and Cloudflare Pages built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
- Pick Netlify if
- Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.
- Pick Cloudflare Pages if
- 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.
8 sourced criteria separate them:
- Entry paid plan
- Netlify: $9/month for 1,000 credits/month
- Cloudflare Pages: $5 / month account minimum
- Pricing model
- Netlify: Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle.
- Cloudflare Pages: Metered usage with a $5 monthly account minimum
- Sites or apps included
- Netlify: 500 projects on the Personal plan (same limit on Free and Pro)
- Cloudflare Pages: 100 projects per account (platform-wide, all plans)
- Monthly visits cap
- Netlify: No fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth
- Cloudflare Pages: No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota
- File or inode limit
- Netlify: No limit on files per deploy, but a hard limit of 54,000 files per directory (platform-wide)
- Cloudflare Pages: 100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB
- Concurrent builds
- Netlify: Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build
- Cloudflare Pages: 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro
- CPU time limit
- Netlify: 50 ms of CPU execution time per request for Edge Functions, explicitly excluding time spent waiting on resources or responses. Listed under operation limits with no plan differentiation (applies on the cheapest paid plan).
- Cloudflare Pages: 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.
- Scheduled jobs
- Netlify: Supported
- Cloudflare Pages: Not supported
At a glance.
| Criterion | Netlify | Cloudflare Pages |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Entry paid plan | $9/month for 1,000 credits/month | $5 / month account minimum |
| Pricing model | Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle. | Metered usage with a $5 monthly account minimum |
| Limits | ||
| Sites or apps included | 500 projects on the Personal plan (same limit on Free and Pro) | 100 projects per account (platform-wide, all plans) |
| Monthly visits cap | No fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth | No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota |
| File or inode limit | No limit on files per deploy, but a hard limit of 54,000 files per directory (platform-wide) | 100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB |
| Concurrent builds | Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build | 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro |
| Execution | ||
| CPU time limit | 50 ms of CPU execution time per request for Edge Functions, explicitly excluding time spent waiting on resources or responses. Listed under operation limits with no plan differentiation (applies on the cheapest paid plan). | 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. |
| Deployment | ||
| Git deployment | Supported | Supported |
| Scheduled jobs | Supported | Not supported |
| Infrastructure | ||
| Edge network | Supported | Supported |
Where they differ.
Entry paid plan
- Netlify
- $9/month for 1,000 credits/month
- Cloudflare Pages
- $5 / month account minimum
Sources (2) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“$9/month for 1,000 credits/month, with an auto recharge option (500 credits for $5) if you go over your monthly credits.”
Read 2026-09-05 · official docs
- 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
- Netlify
- Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle.
- Cloudflare Pages
- Metered usage with a $5 monthly account minimum
Sources (2) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“By using credits to measure and bill for usage, Netlify users have fewer metrics to track and more flexibility on how to optimize their spending.”
Read 2026-09-05 · official docs
- 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
Sites or apps included
500 projects on the Personal plan (same limit on Free and Pro)
100 projects per account (platform-wide, all plans)
Sources (2) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“Project count limit — Personal: 500 projects”
Read 2026-09-05 · official docs
- Limits ↗
“Cloudflare Pages has a limit of 100 projects per account.”
Read 2026-09-05 · official docs
Monthly visits cap
- Netlify
- No fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth
- Cloudflare Pages
- No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota
Sources (2) →Sources ↓
- How credits work ↗
“| Web requests | 2 credits per 10,000 requests | Web traffic requests to your site or app, includes page views, API calls, redirects, requests to serverless functions, asset requests | ... | Bandwidth | 20 credits per GB | Data sent out to the internet, such as assets hosted on Netlify or files downloaded from your site/app. |”
Read 2026-09-05 · official docs
- 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
No limit on files per deploy, but a hard limit of 54,000 files per directory (platform-wide)
100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB
Sources (2) →Sources ↓
- Deploy overview ↗
“While Netlify doesn't have a limit on the number of files per deploy, we do have a limit of 54,000 files per directory. If any directory within your publish directory has more than 54,000 files, your deploys will fail.”
Read 2026-09-05 · official docs
- 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
Concurrent builds
Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build
5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro
Sources (2) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“1 concurrent build included in plan with option to purchase more. Limited to 3 concurrent builds, meaning up to 3 builds can run at the same time. Ideal for using multiple agents and running projects that depend on each other. Add 1 additional concurrent build as an add-on at $40/month”
Read 2026-09-05 · official docs
- 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
CPU time limit
- Netlify
- 50 ms of CPU execution time per request for Edge Functions, explicitly excluding time spent waiting on resources or responses. Listed under operation limits with no plan differentiation (applies on the cheapest paid plan).
- Cloudflare Pages
- 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 (2) →Sources ↓
- Edge Functions limits ↗
“CPU execution time per request: 50 ms — This tracks all time spent running your scripts. Execution time does not include time spent waiting for resources or responses.”
Read 2026-09-05 · official docs
- 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
Scheduled jobs
- Netlify
- Supported
- Cloudflare Pages
- Not supported
Sources (2) →Sources ↓
- Scheduled Functions | Netlify Docs ↗
“Scheduled Functions is a feature of Netlify Functions that enables you to run functions on a regular and consistent schedule, much like a cron job.”
Read 2026-09-05 · official docs
- Migrate from Pages to Workers · Cloudflare Workers docs ↗
“Cron Triggers | ✅ | ❌ (compatibility matrix column headings: Workers | Pages)”
Read 2026-09-05 · official docs
Which should you choose?
Choose Netlify if…
Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.
Editorial · Palash Bagchi · approved
Choose Cloudflare Pages if…
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.
Editorial · Palash Bagchi · approved
Consider something else if…
- Netlify: You need to run containers or long-lived processes — Netlify does not document either.
- Cloudflare Pages: Your repository is hosted somewhere other than GitHub or GitLab, or the free plan's 500 builds a month is not enough headroom.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.