Cloudflare Workers vs Cloudflare Pages
SEPT 2026 auditA comparison of Cloudflare Workers and Cloudflare Pages built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Cloudflare Workers if…
Code that should run in every Cloudflare data centre rather than one chosen region, where 10 ms of free CPU per request is enough to start and a $5 account minimum then covers Workers, KV, Hyperdrive and Durable Objects together.
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…
- Cloudflare Workers: The work is CPU-bound or long-running: the free plan allows 10 ms of CPU per HTTP request and stops at 100,000 requests a day, and the paid plan defaults to 30 seconds rather than the 5-minute ceiling.
- 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.
5 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Cloudflare Workers 0
Cloudflare Pages 0
At a glance.
| Criterion | Cloudflare Workers | Cloudflare Pages |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Entry paid plan | $5/month minimum charge for an account on the Workers Paid plan, which covers Workers, Pages Functions, Workers KV, Hyperdrive and Durable Objects usage. | $5 / month account minimum |
| Execution | ||
| CPU time limit | 10 ms of CPU per HTTP request on the free plan; up to 5 minutes on paid, defaulting to 30 seconds. Time spent waiting on network requests does not count. | 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. |
| Infrastructure | ||
| Regions | No region selection. A Worker runs in the data centre closest to the request; Smart Placement can instead pin it near a named cloud region, host or hostname. | No region selection. Pages Functions run in the data centre closest to the request; Smart Placement can instead pin a Worker near a named cloud region, host or hostname. |
| Uptime SLA | 99.99% monthly, in a dedicated Workers SLA that says it applies to use of Workers only and names no plan tier. Cloudflare's separate application-services plan table shows an uptime SLA on Business and Enterprise only. | Cloudflare's Workers SLA promises 99.99% and says it applies to use of Workers only. Pages Functions run on the Workers runtime, but no SLA names Pages, so the commitment is not stated for this product. |
| Support | ||
| Support on entry paid plan | Community forum and Discord on every plan, with Discord named as the Developer Platform channel. Opening a support case needs Pro or above — Free is limited to billing, account and registrar issues. Live chat starts at Business, emergency phone at Enterprise. | Community forum and Discord on every plan, with Discord named as the Developer Platform channel. Opening a support case needs Pro or above — Free is limited to billing, account and registrar issues. Live chat starts at Business, emergency phone at Enterprise. |
| Response time commitment | None on the Workers Paid plan: Cloudflare says pay-as-you-go and Free customers get no SLA and are answered in the order received. Priority response times are sold as the Premium and Enterprise SLAs — 1 hour and 2 hours for an urgent P1. | None on the $5/month Workers Paid plan Pages bills against: Cloudflare says pay-as-you-go and Free customers get no SLA and are answered in the order received. Priority response times are sold as the Premium and Enterprise SLAs — 1 hour and 2 hours for an urgent P1. |
Where they differ.
Entry paid plan
- Cloudflare Workers
- $5/month minimum charge for an account on the Workers Paid plan, which covers Workers, Pages Functions, Workers KV, Hyperdrive and Durable Objects usage.
- Cloudflare Pages
- $5 / month account minimum
Sources (1) →Sources ↓
- Pricing — Cloudflare Workers docs ↗
“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-14 · official docs
CPU time limit
10 ms of CPU per HTTP request on the free plan; up to 5 minutes on paid, defaulting to 30 seconds. Time spent waiting on network requests does not count.
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 ↓
- Limits — Cloudflare Workers docs ↗
“cpu time measures how long the cpu spends executing your worker code. waiting on network requests (such as fetch() calls, kv reads, or database queries) does not count toward cpu time. limit workers free workers paid cpu time per http request 10 ms 5 min (default: 30 seconds)”
Read 2026-09-14 · 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
Regions
- Cloudflare Workers
- No region selection. A Worker runs in the data centre closest to the request; Smart Placement can instead pin it near a named cloud region, host or hostname.
- Cloudflare Pages
- No region selection. Pages Functions run in the data centre closest to the request; Smart Placement can instead pin a Worker near a named cloud region, host or hostname.
Sources (1) →Sources ↓
- Smart Placement · Cloudflare Workers docs ↗
“By default, Workers and Pages Functions run in a data center closest to where the request was received. If your Worker makes requests to back-end infrastructure such as databases or APIs, it may be more performant to run that Worker closer to your back-end than the end user.”
Read 2026-09-14 · official docs
Uptime SLA
- Cloudflare Workers
- 99.99% monthly, in a dedicated Workers SLA that says it applies to use of Workers only and names no plan tier. Cloudflare's separate application-services plan table shows an uptime SLA on Business and Enterprise only.
- Cloudflare Pages
- Cloudflare's Workers SLA promises 99.99% and says it applies to use of Workers only. Pages Functions run on the Workers runtime, but no SLA names Pages, so the commitment is not stated for this product.
Sources (1) →Sources ↓
- Workers Service Level Agreement — Cloudflare ↗
“applies to use of workers only [...] cloudflare will use commercially reasonable efforts to provide a monthly uptime percentage of 99.99% for customer's use of workers”
Read 2026-09-14 · official site
Response time commitment
- Cloudflare Workers
- None on the Workers Paid plan: Cloudflare says pay-as-you-go and Free customers get no SLA and are answered in the order received. Priority response times are sold as the Premium and Enterprise SLAs — 1 hour and 2 hours for an urgent P1.
- Cloudflare Pages
- None on the $5/month Workers Paid plan Pages bills against: Cloudflare says pay-as-you-go and Free customers get no SLA and are answered in the order received. Priority response times are sold as the Premium and Enterprise SLAs — 1 hour and 2 hours for an urgent P1.
Sources (1) →Sources ↓
- Contacting Cloudflare Support · Cloudflare Support docs ↗
“Premium SLA P1 Urgent- initial response in 1 hour P2 High - initial response in 2 hours P3 Normal - initial response in 24 hours P4 Low - initial response in 24 hours Enterprise SLA P1 Urgent - initial response in 2 hours P2 High - initial response in 4 hours P3 Normal - initial response in 48 hours P4 Low - initial response in 48 hours SLOs for other plans Pay-as-you-go and Free customers - No SLAs are offered, but customers are responded to in the order in which their request is received.”
Read 2026-09-14 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
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.
Questions this comparison answers.
Entry paid plan: Cloudflare Workers or Cloudflare Pages?
Cloudflare Workers: $5/month minimum charge for an account on the Workers Paid plan, which covers Workers, Pages Functions, Workers KV, Hyperdrive and Durable Objects usage.
Cloudflare Pages: $5 / month account minimum
Should I choose Cloudflare Workers or Cloudflare Pages?
Pick Cloudflare Workers if Code that should run in every Cloudflare data centre rather than one chosen region, where 10 ms of free CPU per request is enough to start and a $5 account minimum then covers Workers, KV, Hyperdrive and Durable Objects together.
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.