Cloudflare Queues Pricing (2026) — Operations & Cost per Message
Queues bills per 64 KB operation, and delivering one message takes about three of them: a write when it's produced, a read when it's delivered to a consumer, and a delete when it's acknowledged. That makes the practical cost roughly $1.20 per million messages after the included allowance — simple, but retries and large messages multiply it.
Rates verified against Cloudflare's official docs · last checked April 2026
Cloudflare Queues pricing table
| Workers Free | Workers Paid ($5/mo) | |
|---|---|---|
| Standard operations | 10,000 / day | 1M / month included, then $0.40 per million |
| Message retention | 24 hours (fixed) | 4 days default, configurable up to 14 days |
// An operation = 64 KB written, read, or deleted. Messages over 64 KB bill as multiple operations (a 127 KB message = 2 ops per action). Operations are per message, not per batch: a batch of 10 delivered messages = 10 reads (plus 10 writes at produce, 10 deletes on ack).
What actually matters
The cost-per-message formula
((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Three ops per message is the common case: 1 write + 1 read + 1 delete. At 10M messages/month that's 30M ops → $5 base (covers first 1M ops) + $11.60 ≈ $11.60 in queue charges on top of Workers Paid.
Retries are not free
Each retry incurs another read operation. A batch of 10 that fails and retries three times adds 30 read ops. Poison messages that exhaust retries and land in a Dead Letter Queue incur a write per 64 KB chunk.
The $0.40 rate hides behind included volume
1M operations/month included means ~333K messages/month are effectively free — most side projects never see a queue line item. The billing only becomes visible at serious throughput.
Example: 5M messages / month, small payloads, no retries
What people miss
- ▸Message size includes ~100 bytes of internal metadata — payloads near the 64 KB boundary can tip into an extra operation.
- ▸Expired messages (retention reached before delivery) still incur write + delete operations.
- ▸The free tier's 10K ops/day = only ~3,300 messages/day across produce + consume + ack.
- ▸There's no Queues-only plan — it requires Workers Paid for real volume.
Model your own bill
Plug your monthly volumes into the free calculator and see the total across Workers, KV, R2, D1, and Queues. Then let FlareLog watch the real thing: real-time cost burn alerts fire the moment a loop or spike starts inflating your bill — hours before Cloudflare's 15–60 minute dashboards catch up.
FAQ
How much does Cloudflare Queues cost?
1 million operations per month are included on Workers Paid, then $0.40 per million operations. Since delivering a message typically costs 3 operations (write, read, delete), one million messages costs about $1.20 in overage. The Workers Free plan includes 10,000 operations per day.
What counts as a Queues operation?
Each 64 KB of data written, read, or deleted is one operation. Producing a message = a write, delivering it to a consumer = a read, acknowledging it = a delete. Retries add read operations; messages larger than 64 KB count as multiple operations per action; batches don't help — operations are counted per message, not per batch.
How do I reduce my Queues bill?
Keep messages under 64 KB so each action is one operation, minimize retries by fixing poison messages early (dead-letter them deliberately), batch consumer work without changing message counts (billing is per message), and delete messages promptly — expired messages still bill write + delete. At high volume, consider whether batching multiple logical events into one message fits your semantics.
Does Cloudflare charge for egress on Queues?
No. Like all Workers platform products, Queues has no data transfer or throughput charges — only the per-operation billing described above.