Skip to content
Help · MoreCloudflare Email Routing and Sending limits
Start here

Cloudflare Email Routing and Sending limits

The limits that matter on Cloudflare email: 200 routing rules per domain, 200 destination addresses, 25 MiB messages, 50 recipients per email and send quotas.

On this page · 5 sections

Email Routing: receiving

These apply to mail coming in to your domain. [1]

Routing rules per domain
Value: 200
What it means: One rule maps one address pattern to one destination or one Worker.
Destination addresses per account
Value: 200
What it means: Verified destinations are shared by every domain in the account.
Inbound message size
Value: 25 MiB
What it means: Larger messages are rejected.
Domains per zone
Value: 30
What it means: The root domain and subdomains set up for Email Routing or Email Sending, together.
Inbound emails
Value: Unlimited
What it means: On both the Workers Free and Workers Paid plans. [2]

A rule sends a pattern to one place. To forward the same address to several inboxes, Cloudflare's answer is a Worker that forwards it once per destination, and each destination has to be verified first. [1] Mail to addresses with no rule of their own goes to the catch-all: see Catch-all email on Cloudflare.

Email Sending: sending

These apply to mail sent through Cloudflare Email Service, from the REST API, the Workers binding or SMTP. [1]

Recipients per email
Value: 50
What it means: To, Cc and Bcc together.
Message size
Value: 25 MiB
What it means: Attachments included.
Subject line
Value: 998 characters
What it means: The email standard's own limit.
Headers
Value: 16 KB
What it means: All custom headers together.
Daily sending limit
Value: Set per account
What it means: New accounts start low, and the limit rises with sending history and deliverability.

Sending to any recipient needs the Workers Paid plan, which includes 3,000 emails a month and then costs $0.35 per 1,000. Sending to destination addresses you have verified in your own account is free on every plan and doesn't count toward the quota. Emails that bounce count; emails refused before sending, such as ones blocked by the suppression list, don't. [2] Before a domain is set up for sending, you can only send to verified destination addresses; after, to anyone. [1]

Email Workers

  • A Worker that handles incoming mail counts against the normal Workers CPU and memory limits. On the Workers Free plan a heavy handler can fail with EXCEEDED_CPU, and the failure shows in the Workers logs. [1]
  • If an incoming message has more than 100 References entries, message.reply() throws, which stops reply loops. [1]
  • Mail sent by a Worker through the send_email binding shows in the Email Routing summary as dropped even when it was delivered. Check the Email Sending metrics and logs instead. [1]

Need more? Cloudflare takes requests through its Limit Increase Request Form. [1]

How Ayoh stays inside them

Ayoh points the domain's catch-all at its own Worker, so every address you create uses that one rule rather than one rule and one destination each, and the 200 limits stop mattering. Mail is kept in your own Cloudflare account instead of being forwarded. Replies go out through Email Sending from your address, so they count toward the Workers Paid quota above; for one person writing a few dozen messages a day that is well inside the 3,000 included. What each part costs is on Does Cloudflare host email?, and setup is in Getting started.

Sources

Read November 14, 2026.