Quick Answer: How much does cloudflare workers cost for a small project or business?
For most small projects, Cloudflare Workers costs either nothing or a flat base fee of about $5 per month on the paid plan. The free tier covers low-traffic sites, while the paid plan adds higher request allowances, more CPU time, and access to paid features. Storage products like KV, R2, D1, and Durable Objects are billed on separate meters, so your real bill depends on which bindings you use. Before committing, compare your expected daily requests, CPU time per request, storage needs, egress volume, and whether you need paid-only features. (Cloudflare)
Cloudflare Workers flipped the traditional hosting model on its head. Instead of renting a server and hoping traffic shows up, you deploy small functions that run only when someone makes a request. That sounds cheap, and for many small projects it genuinely is. But “cheap” is not the same as “free,” and the pricing structure has a few quirks that catch people off guard. This guide breaks down what a small project or business actually pays, where the hidden costs live, and how to estimate your bill before you commit.
Why Workers Pricing Feels Different From Normal Hosting
Most hosting bills are predictable because you rent a fixed box. Workers bills are usage-based, which means the cost scales with what your code does. The good news: Cloudflare does not charge for time spent waiting on a database or an API. It charges for CPU time, the actual compute your function burns. A worker that waits two seconds for a slow API call but computes for 5 milliseconds is billed for 5 milliseconds.
That distinction matters enormously for small projects. A typical contact form handler, redirect service, or lightweight API endpoint might use a few milliseconds of CPU per request. At that rate, even modest traffic stays well inside the free tier. The pricing model rewards efficient code and punishes heavy computation, which is a very different incentive than a flat monthly server bill.
The Free Plan: What You Get and Where It Stops
The free tier is the starting point for almost every small project, and it is generous enough that many sites never leave it. It includes a daily request cap (commonly cited as 100,000 requests per day) and a limited amount of CPU time per request. For a brochure site, a small API, or an internal tool with a few hundred daily users, that ceiling is rarely touched.
Two details trip people up. First, free-tier limits are applied per account, not per Worker, so running five small functions does not multiply your allowance. Second, the free plan lacks some paid-only capabilities, including certain Durable Objects features and higher CPU ceilings. If your project needs those, the free tier is not a negotiation, it is a wall.
Practical tip: before upgrading, check your actual request volume in the Cloudflare dashboard for a week or two. Plenty of teams pay for the paid plan out of anxiety rather than need.
The Paid Plan: The $5 Question
The Workers Paid plan has historically started at a base monthly fee (commonly cited as $5 per month) that includes a monthly request allowance (commonly cited as 10 million requests), with per-million overage charges beyond that. For a small business, that base fee is usually the entire bill. Request overages only become a real line item once you are pushing serious traffic.
Here is the honest caveat: Workers pricing has changed several times since the paid model launched, so any figure you read, including the ones here, should be checked against Cloudflare’s current official pricing page before you budget. Treat the numbers as a shape, not a promise. The structure, a small base fee plus usage meters, has been stable; the exact rates have not.
| Plan | Base Cost | Included Requests | Best For |
|---|---|---|---|
| Free | $0 | Daily cap (commonly 100,000/day) | Hobby projects, low-traffic sites |
| Paid | ~$5/month | Monthly allowance (commonly 10M) | Small businesses, production apps |
| Storage add-ons | Varies by product | Separate meters | Projects using KV, R2, D1, Durable Objects |
Where Small Projects Actually Spend Money
The base fee is rarely the story. The real cost driver is which storage and compute products you attach. Cloudflare bills KV, R2, D1, and Durable Objects on their own meters, so a “small project” that leans on three of them is really three small bills stacked together.
A few patterns show up again and again:
- Static sites with a little logic (redirects, headers, A/B tests) usually cost $0. They barely touch CPU and need no storage.
- APIs with a database add D1 or KV costs on top of the base fee. Still small, but not zero.
- File-heavy apps using R2 benefit from the fact that R2 has historically charged no egress fees, a notable differentiator versus S3-style storage. That single feature can save a small business more than every other line item combined.
- Real-time features using Durable Objects are the priciest common pattern, because they keep state alive and bill accordingly.
If you are also weighing other software subscriptions for your business, it helps to benchmark them the same way. Tools like accounting platforms or password managers have their own pricing quirks, and comparing them side by side (for example, checking how much 1Password costs) keeps your total stack visible rather than hidden across a dozen invoices.
CPU Time vs. Wall-Clock Time: The Mistake That Inflates Bills
The single most common estimating error is confusing wall-clock time with CPU time. A developer sees that a request “takes 800ms” and multiplies that by traffic, then panics at the projected bill. In reality, only the compute portion is billed. If 780ms of that was waiting on a fetch, the billable time is a fraction of what they feared.
The opposite mistake is just as common: writing a worker that does heavy JSON parsing, image manipulation, or cryptographic work on every request. That burns real CPU, and CPU is what you pay for. Small projects rarely hit this, but when they do, the fix is usually architectural, moving work to a scheduled job or caching the result, rather than upgrading the plan.
Measure first, optimize second. Cloudflare’s analytics show CPU time per request, and that number tells you more about your future bill than any traffic graph.
Estimating Your Bill: A Practical Walkthrough
Here is a simple process that works for most small businesses:
- Count your daily requests. Pull a week of analytics from your current host or estimate from user numbers. Multiply average daily users by requests per session.
- Estimate CPU per request. Start with a conservative 10ms if you are unsure. Most simple endpoints land well below that.
- List your storage bindings. Note whether you need KV (config and cache), D1 (relational data), R2 (files), or Durable Objects (stateful real-time).
- Check the free-tier ceiling against step 1. If you are under the daily cap and need no paid features, your bill is $0.
- If you exceed it, budget the base fee plus storage. For most small projects, that lands in the single-digit-to-low-double-digit dollar range per month.
A useful sanity check: compare this to what you would pay for a comparable VPS plus managed database. Workers often wins on cost at low traffic and loses at sustained high CPU workloads, where a fixed server becomes cheaper per unit of compute.
When Workers Is the Wrong Choice for a Small Business
Workers is not automatically the cheapest option, and pretending otherwise does a disservice to small teams. It is a poor fit when your workload is CPU-heavy and constant, such as video transcoding, long-running batch jobs, or heavy data processing. Fixed-cost servers handle those better because you are not paying per compute millisecond.
It is also awkward if your team has no JavaScript or TypeScript experience and no appetite to learn an edge runtime. The platform is developer-first; the savings evaporate if you need a consultant to maintain it. And if your project depends on a traditional stack with long-lived processes, Workers will fight you at every turn.
The cheapest platform is the one your team can actually run. That is not a cop-out, it is the most practical cost consideration of all.
Comparing Workers to the Rest of Your Software Stack
Small businesses rarely buy one tool in isolation. A typical stack includes hosting, a website builder, accounting software, and a handful of subscriptions. Putting Workers in that context makes the decision clearer. If you are choosing a site platform alongside your edge functions, it is worth reviewing the best website builders for small business so you are not paying for overlapping capabilities. Likewise, pairing your infrastructure choices with solid small business accounting software keeps the bookkeeping side from becoming its own cost center.
The pattern is consistent: edge compute is usually one of the smaller line items. The bigger savings often come from consolidating tools and cutting subscriptions you forgot you had.
Common Mistakes That Cost Small Teams Money
A few avoidable errors show up repeatedly:
- Upgrading to paid before measuring. Many teams pay the base fee for months while sitting comfortably inside free-tier limits.
- Ignoring storage meters. Building on KV, D1, and R2 without checking each product’s separate pricing page leads to surprise line items.
- Over-engineering for scale. A small business does not need Durable Objects for a contact form. Simpler bindings cost less and break less.
- Forgetting egress. If you store files, confirm the egress terms. R2’s no-egress positioning is a genuine advantage, but only if you actually use R2.
- Never revisiting the estimate. Traffic patterns change. A quarterly check of your dashboard takes ten minutes and can catch a runaway cost early.
Conclusion
For a small project or business, Cloudflare Workers is usually a $0 to roughly $5-per-month decision, with storage products adding a modest amount on top. The platform rewards efficient code and light storage use, and it punishes heavy, constant computation. The smartest approach is unglamorous: measure your real request volume and CPU time, list every binding you plan to use, and check the official pricing page before you budget. Do that, and Workers becomes one of the more predictable line items in your stack rather than a mystery charge you discover at the end of the quarter. The edge is cheap, but only for the workloads it was built for.
FAQ
Is the Cloudflare Workers free tier enough for a small business website?
For most low-traffic business sites, yes. A brochure site, a contact form handler, or a small API with a few hundred daily visitors typically stays well inside the free tier’s daily request cap. The free plan only becomes limiting if you need paid-only features or exceed the daily request ceiling.
Do I pay for time my worker spends waiting on an API or database?
No. Workers bills CPU time, not wall-clock time. If your function waits two seconds for an external API but only computes for a few milliseconds, you are billed for the compute portion. This is why I/O-heavy workloads are often far cheaper than developers expect.
Are storage products like KV, R2, and D1 included in the base plan?
No. Each storage product is billed on its own separate meter, so your total cost depends on which bindings your project uses. A project using only Workers logic may pay just the base fee, while one leaning on multiple storage products will see additional charges on top.
Why is R2 often cheaper than S3-style storage for file-heavy projects?
R2 has historically charged no egress fees, meaning you are not billed for data transferred out to users. For projects that serve lots of files, images, or downloads, that single difference can outweigh every other line item in the bill.
Does the free tier apply per Worker or per account?
Free-tier limits apply per account, not per individual Worker. Running several small functions does not multiply your allowance, which is worth remembering if you plan to split one project across multiple Workers.
How often does Cloudflare change Workers pricing?
Pricing has been revised several times since the usage-based model launched, and storage products have been added over time. Because rates shift, any figure you read should be verified against Cloudflare’s current official pricing page before you finalize a budget.
