Optimize costs
Cloudflare lists ways to find and reduce usage-based charges by product.
- Products
- Account-wide usage-based productsWorkersDurable ObjectsR2
- Source
- Official docsCloudflare Docs
Key points
- The page starts from the billable usage dashboard to find which products drive costs. General strategies are budget alerts, a weekly dashboard review, and understanding how charges accrue across a request.
- For Workers and Durable Objects, it lists Workers Logs instead of Logpush for log retention, and the WebSocket Hibernation API for idle connections, since duration billing pauses while the object hibernates. For R2, it lists lifecycle rules to Infrequent Access, batching, presigned URLs instead of proxying through Workers, and Cache-Control headers so cached objects skip R2 reads.
- Budget alerts use one account-wide dollar threshold; per-product usage notifications for bytes, requests, or minutes are configured separately in Notifications.
Original sources
Undated
Original post
Open original source
More to read
Official docsAccount-wide usage-based products
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.
Workers
A voting page polling every three seconds: the author revises a $1,000 report.
@keking99 first reports about $1,000 for a voting page polling /api/result every three seconds. A later post reports $816.52 in accumulated usage as of October 4 and cites another screenshot total of $817.14.
Author experienceWorkers +4
Cloudflare billing pitfalls thread
The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.