How much does Cloudflare Queues cost in 2026? Pricing and examples

In brief

• Cloudflare Queues is billed per number of operations (write, read, delete), not per data volume or egress.
• 1 operation = each 64 KB slice of a message. Delivering a message = 3 operations (1 write, 1 read, 1 delete).
• Workers Free: 10,000 operations/day included. Enough for a test volume or a lightly used internal queue.
• Workers Paid: 1 million operations/month included, then $0.40/million. Message retention: 4 days by default, up to 14.
• No egress or bandwidth fees: for messages under 64 KB, a million messages delivered per day costs about 36 $/month.

The problem, concretely

You have an application that processes background tasks: sending emails, PDF generation, file processing, ERP synchronization. If everything goes through direct HTTP requests, the slightest failure or activity spike makes your users wait. A queue puts these tasks in line and processes them at your capacity's pace. That's the role of Cloudflare Queues: a managed message queue at the edge, directly connected to your Workers.

The question that keeps coming up: "How much does it cost?". Short answer: almost nothing to start, and a cost proportional to the number of messages, without ever paying for data exit. Pricing details below.

The pricing model

Queues bills the total number of operations against your queues in the month. An operation is counted for each 64 KB slice written, read or deleted. Concretely, delivering a message costs 3 operations: 1 write (the application pushes it into the queue), 1 read (the Worker picks it up), 1 delete (it's removed after processing).

• Messages over 64 KB: counted as several messages. A 65 KB message and a 127 KB message each generate 2 operations (write, read, delete).
• Retries: each new attempt adds a read operation. A batch reprocessed = 10 extra read operations.
• Dead Letter Queue: a message that fails after the maximum number of attempts and falls into the DLQ generates read operations then a write.
• Expired message: a message that reaches the retention period without being read only costs one write and one delete.

The two plans

Workers Free

• 10,000 operations/day included (about 3,300 messages delivered/day).
• Message retention: 24 hours, not configurable.

That's enough to test, for a lightly used SMB internal queue, or for occasional burst load. Beyond that, you need the paid plan.

Workers Paid (5 $/month)

• 1 million operations/month included, then $0.40/million operations.
• Retention: 4 days by default, configurable up to 14 days.
• The 5 $/month package already covers the Worker itself, R2, D1 and the other Cloudflare services at the same rate.

The formula to estimate your monthly bill, if your messages are under 64 KB:

(Number of messages × 3 − 1,000,000) ÷ 1,000,000 × $0.40

Worked examples

• Moderate usage: 1 million messages delivered/day, messages under 64 KB, 30 days = 90 million operations, 1 million included, bill about 36 $/month.
• Larger messages: 100 million messages of about 127 KB (2 slices of 64 KB) = 600 million operations, about 240 $/month. Above 64 KB, the cost doubles, hence the value of keeping messages light.
• Small internal queue: a few thousand messages/day, fully covered by the free plan or the 1 million included operations of the paid plan, so 0 $ on top of the package.

Note: no egress or bandwidth fees. It's the same principle as R2: getting data out of Cloudflare costs nothing, unlike traditional providers.

What makes the bill spiral (and how to avoid it)

• Retries: each new attempt adds read operations. Configure a reasonable number of attempts and fix the cause of failures rather than multiplying retries.
• Messages that are too large: above 64 KB, each message counts for 2 operations or more. Keep messages light (identifiers, compact JSON) and store large payloads in R2, referencing their key.
• Messages that expire: without an active consumer, messages expire and still cost write + delete. A consumer Worker running continuously avoids the waste.

Why it matters for an SMB

For an SMB automating its processes (document generation, sending, synchronizations), the real volume is generally a few thousand to a few hundred thousand messages a day. On that profile, Queues costs 0 to a few euros a month on top of the 5 $/month Workers package. It's a managed queue, with no server to administer, integrating natively with Workers and D1.

If your automation needs a reliable queue, it's a building block I integrate into your Cloudflare projects, at a fixed price and with no subscription behind it. The detail of my services is on the Cloudflare Workers developer page.