Cloudflare Queues
Message queue on Cloudflare Workers, billed per 64 KB operation with no egress or throughput charges.
- queue
- Yes
- Not documented
- Not documented
Who it suits.
Workers applications that want a queue with no egress or throughput charges and a retention window measured in days rather than hours.
Consider something else if…
Billing is per 64 KB operation rather than per message, so a large payload or a chatty retry loop costs several times what the message count suggests.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Cloudflare Queues does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“Workers Free | 10,000 operations/day included [...] Message retention | 24 hours (non-configurable)”
Read 2026-09-06 · official docs
Queues
Included per month
1,000,000 operations a month on Workers Paid, then $0.40 per million. An operation is each 64 KB written, read or deleted, so a typical message costs three — Cloudflare's own formula is ((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Workers Free allows 10,000 operations a day.
Sources (1) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“1,000,000 operations/month included + $0.40/million operations [...] An operation is counted for each 64 KB of data that is written, read, or deleted. [...] In most cases, it takes 3 operations to deliver a message [...] 10,000 operations/day included”
Read 2026-09-06 · official docs
Maximum message size
128 KB per message, with roughly 100 bytes of that taken by internal metadata. Messages above 64 KB are billed as multiple operations.
Sources (1) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“Message size | 128 KB [...] Messages can include up to ~100 bytes of internal metadata that counts towards total message limits.”
Read 2026-09-06 · official docs
Message retention
4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours.
Sources (1) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“Message retention | 24 hours (non-configurable) | 4 days default, configurable up to 14 days”
Read 2026-09-06 · official docs
Maximum delay
24 hours, set with delaySeconds when sending or retrying.
Sources (1) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“delaySeconds (when sending or retrying) | 24 hours”
Read 2026-09-06 · official docs
Concurrency
250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a second and a 25 GB backlog.
Sources (1) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“Concurrent consumer invocations | 250 push-based only [...] Per-queue message throughput | 5,000 messages per second [...] Per-queue backlog size | 25GB”
Read 2026-09-06 · official docs
Dead letter queue
Supported
Sources (1) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“Messages that reach the maximum retries and that are written to a Dead Letter Queue incur a write operation for each 64 KB chunk.”
Read 2026-09-06 · official docs