CLOUDFLARE BILL ESTIMATOR · RUNS IN YOUR BROWSER

What will your Cloudflare bill be, and what cuts it most?

Enter your usage from the Cloudflare dashboard and get an estimated monthly bill by line and a ranked list of levers (edge caching, CPU trimming, KV caching, redundant KV writes, R2 lifecycle, R2 batching, CDN in front of R2) with a dollar saving for each.

Nothing is uploaded. Calculated in this browser from numbers you enter and approximate list prices you can edit. It cannot see your plan or your invoice.

1. Your monthly usage

Prices, allowances and assumptions (editable)

LinePrice per unit (USD)Included per month

Change a price here and press Estimate. Defaults are approximate list prices; check Cloudflare pricing and your plan.

Prefer a CLI, or want a budget gate in CI?

node cli.mjs template > usage.csv
node cli.mjs estimate usage.csv
node cli.mjs estimate usage.csv --budget 100      # exit 1 over budget
node cli.mjs estimate usage.csv --set r2_storage_gb=200 --json
node cli.mjs estimate usage.csv --prices prices.json --assume assumptions.json

Get cli.mjs and engine.mjs — Node 18+, nothing to install, no network call. More: how to reduce your Cloudflare bill.

Common questions

Does this read my Cloudflare account or invoice?

No. It reads only the usage numbers you type or paste (copy them from the Billing and the Workers and R2 analytics pages of the Cloudflare dashboard) and multiplies them by list prices you can edit. It cannot see your plan, add-ons, contract or real invoice. Treat every figure as a way to compare options, never as what you will be charged.

Where do the prices come from?

They are approximate public usage-based list prices from Cloudflare's Workers, KV and R2 pricing pages as best known in 2025, shown with an as-of date, and every one is editable, including the included allowances and the monthly minimum. Cloudflare changes prices and packaging, so check developers.cloudflare.com/workers/platform/pricing before relying on a number.

How is the saving for each lever calculated?

Each lever re-runs the estimate with one change applied under an assumption shown beside it (for example, edge caching that serves 40% of requests without running the Worker) and reports the difference. The assumptions are editable. Levers overlap, so the savings are not additive.

Is my usage data uploaded anywhere?

No. The browser page calculates in your own browser and never sends anything. The CLI reads a local file or stdin and makes no network call.