BlogCloudflare Email Routing
Cloudflare Email Routing vs email hosting: limits, sending and when to switch
Cloudflare Email Routing receives mail for addresses on your domain and passes each message to an inbox you already have, or to a Worker. It's free and quick to turn on. It stores no mail, though, and replying from the address takes a separate Cloudflare product. The limits and prices below come from Cloudflare's own documentation, checked on October 15, 2026.
Short answer
Keep Cloudflare Email Routing if you only receive mail at your domain and read it in another inbox. It is free, allows 200 routing rules per domain and 200 destination addresses per account, but it stores no mail. Move to a hosted mailbox when you reply from the address, need its sent history, or share it with someone else.
Cloudflare Email Routing limits
Cloudflare Email Routing allows 200 routing rules per domain and 200 destination addresses per account, and rejects inbound messages over 25 MiB. Each rule has one destination, and the domain must use Cloudflare DNS.Sources[3]Cloudflare Email Service limits[2]Cloudflare Email Routing setup
- Routing rules: 200 per domain. Each rule maps one address pattern to one destination.
- Destination addresses: 200 per account, shared across every domain in it. You verify each one by email first.
- Message size: 25 MiB for inbound mail. Cloudflare rejects larger messages.
- One address to several people: a rule has one destination, so fanning out needs a Worker that forwards to each verified address.
- DNS: the domain must use Cloudflare DNS. Cloudflare adds its own MX, SPF and DKIM records and locks them.
- Price: inbound routing is unlimited on the Workers Free and Paid plans.
For one person with a contact@ and a hello@ address, none of these limits matter. They matter when a team wants support@ to reach three people, or when a domain needs dozens of addresses spread across many inboxes.[3]
Can Cloudflare send email from my domain?
Cloudflare Email Routing alone cannot. Cloudflare sells sending as a separate product, Email Sending, which is in beta for transactional email. It works through a Workers binding, a REST API or authenticated SMTP.[6]
Sending to your own verified destination addresses is free on every plan. Sending to anyone else needs the Workers Paid plan, which includes 3,000 emails a month and then charges $0.35 per 1,000. A message can carry 50 recipients and 5 MiB.Sources[5]Cloudflare Email Service pricing[3]Cloudflare Email Service limits
That covers order confirmations and password resets from code. It doesn't give you a mailbox. There's no inbox, no Sent folder and no IMAP account to add to Apple Mail or Outlook. Plugging its SMTP into Gmail's Send as only works for a while, because Gmail stops supporting Send as for third-party addresses in January 2027.Sources[6]Cloudflare Email Service overview[7]Google Gmail Send as help page
When Cloudflare Email Routing is enough
Cloudflare Email Routing is enough when nobody replies from the address, or when one person answers a few messages a month from a personal inbox. It also fits a Worker that receives mail and acts on it.[1]
- A solo founder routes
contact@yourdomain.cominto a personal inbox and answers a few messages a month. - A side project needs an address for a sign-up form or a domain registrar, and nobody replies from it.
- A Worker should receive mail and act on it, such as parsing invoices or replies into an app.
- An old address must stay reachable for a few months after a rebrand.
If all of these describe you, keep the free route. There's no point paying for a mailbox nobody replies from.
Signs you need hosted email instead
You usually find out you need hosted email the first time you reply. A forwarded message lands in your personal inbox, so your answer goes out from that address, and the thread lives in your personal Sent folder. Our guide to email forwarding vs real hosting explains the rest, including why forwarded mail can land in spam.[8]
- Customers write to the address and expect replies from it.
- A second person needs to read or answer the same mail.
- You want the address in Apple Mail, Outlook or a phone app, with its own Sent folder.
- The address should survive if the person whose inbox receives it leaves.
What a Shipmail mailbox adds
A Shipmail mailbox receives, sends and keeps its own Sent folder, and works in webmail or any app over IMAP and SMTP. Shipmail Solo is $4 a month for 2 mailboxes and 4 aliases. Aliases show up in the From menu, so you can reply as hello@ from the mailbox that receives it.Sources[9]Shipmail pricing[10]Shipmail email client connection settings[11]Shipmail mailbox docs: adding aliases
A catch-all takes mail for any unknown address on the domain, like Cloudflare's catch-all rule. Shipmail can also forward a mailbox's mail to up to three confirmed addresses. The original stays in the mailbox, so your personal inbox no longer holds the only copy.Sources[12]Shipmail catch-all docs[13]Shipmail docs: forwarding incoming mail
The same plan also covers what Email Sending does for an app, with a transactional API, SDKs and webhooks. It sends from a separate subdomain, and customer replies reach a mailbox. Cloudflare does win on one point. Inbound routing to a Worker is free, with no mailbox to pay for.Sources[14]Shipmail transactional email documentation[5]Cloudflare Email Service pricing
How to move from Cloudflare Email Routing to Shipmail
To move from Cloudflare Email Routing to Shipmail, list your routing rules, add the domain to Shipmail and replace Cloudflare's MX records. Keep routing on until every address is tested, then disable it.Sources[4]Cloudflare: disable Email Routing[15]Shipmail domain setup documentation
- Step 1
List your routing rules
Write down each custom address and its destination. Mark which ones need a mailbox, which can be aliases, and whether the catch-all rule is on.
- Step 2
Unlock the routing records
In Cloudflare, go to Compute, Email Service, Email Routing, pick the domain and open Settings. Choose to unlock the routing records so you can edit them. Keep routing on for now.
- Step 3
Add the domain to Shipmail
Shipmail detects Cloudflare DNS. Use Configure automatically if it is offered, or copy the MX, SPF, DKIM and DMARC records into Cloudflare DNS, replacing Cloudflare's MX records.
- Step 4
Wait for verification, then create addresses
Shipmail rechecks the records every 30 seconds. Once the domain verifies, create the mailboxes and aliases. Shipmail holds mail for new addresses for 48 hours, so nothing bounces while you work.
- Step 5
Test, then disable routing
Send a message in and out of each address. Then return to Email Routing Settings and select Disable Email Routing, which removes Cloudflare's remaining routing records.
Sources15 sourcesVerified 2026-11-09
- [1]Cloudflare Email Routing overview
Email Routing routes incoming email for custom addresses to Workers or verified destination addresses and is available on Free and Paid plans. Outbound sending is a separate Email Sending product, in beta for transactional email on the Workers Paid plan.
developers.cloudflare.com · 2026-10-15
- [2]Cloudflare Email Routing setup
Compute, Email Service, Email Routing, Onboard Domain: Cloudflare adds MX, SPF and DKIM records to the root domain. Destination addresses are verified by email. The domain must use Cloudflare DNS.
developers.cloudflare.com · 2026-10-15
- [3]Cloudflare Email Service limits
Email Routing: 200 routing rules per domain, each mapping one pattern to one destination; 200 destination addresses per account, shared across domains; 25 MiB inbound message size. Sending one pattern to several destinations needs a Worker. Email Sending: 50 recipients per email, 5 MiB per message (25 MiB to verified destinations).
developers.cloudflare.com · 2026-10-15
- [4]Cloudflare: disable Email Routing
Compute, Email Service, Email Routing, select the domain, Settings, Disable Email Routing. Disabling stops inbound processing and removes the MX, SPF and DKIM routing records. When moving to another provider, unlock the routing records first, add and verify the new provider's records, then disable.
developers.cloudflare.com · 2026-11-01
- [5]Cloudflare Email Service pricing
Email Routing inbound is unlimited on Workers Free and Paid. Sending to verified destination addresses is free on all plans. Sending to any recipient needs Workers Paid: 3,000 emails a month included, then $0.35 per 1,000.
developers.cloudflare.com · 2026-11-01
- [6]Cloudflare Email Service overview
Email Routing (Free and Paid plans) routes incoming mail to addresses or Workers. Email Sending is in beta for outbound transactional email on Workers Paid, through a Workers binding, the REST API or authenticated SMTP. No hosted mailboxes are described.
developers.cloudflare.com · 2026-11-01
- [7]Google Gmail Send as help page
Google's notice that Gmail stops supporting Send as for third-party email addresses starting January 2027, and its stated exceptions for Google Workspace aliases and other Gmail addresses you own.
support.google.com · 2026-11-01
- [8]Gmail: best practices for forwarding email to Gmail
Forwarded messages often fail SPF; DKIM is especially important for forwarded mail; Gmail does not automatically trust forwarded messages that passed authentication earlier; forwarded spam marked by recipients makes future mail from the forwarding domain more likely to be filtered.
support.google.com · 2026-10-15
- [9]Shipmail pricing
Shipmail plan prices, mailbox limits, team access, and send limits.
shipmail.to · 2026-10-15
- [10]Shipmail email client connection settings
Shipmail IMAP, SMTP, and JMAP settings: mx1.shipmail.to, IMAP on port 993 with SSL/TLS, SMTP on port 465 with SSL/TLS or 587 with STARTTLS, the full email address as username, and the mailbox password or an app password.
shipmail.to · 2026-10-15
- [11]Shipmail mailbox docs: adding aliases
Open a mailbox and choose Aliases to add any available local part on any verified domain in the organization. An alias shares the parent mailbox's inbox, storage, access, display name and signature, has no separate password and does not use another mailbox allowance. In compose, the From menu lists the mailbox and its aliases.
shipmail.to · 2026-10-11
- [12]Shipmail catch-all docs
A catch-all mailbox receives email sent to any address on the domain that does not match a mailbox; one catch-all per domain, set from Mailboxes, then the mailbox's Catch-all option. Replies go out from the address the sender used. Without catch-all, mail to unknown addresses bounces. Catch-all mail counts toward the mailbox storage quota.
shipmail.to · 2026-10-15
- [13]Shipmail docs: forwarding incoming mail
Settings, Incoming mail, Forwarding: up to three destination addresses per mailbox, each confirmed by link before forwarding starts. Filter by one sender, by the mailbox address or alias that received the mail, or both. The original stays in the Shipmail mailbox and spam is not forwarded. The forwarded copy is sent from the mailbox address so it passes the destination's authentication checks, with the original sender's name kept and the original address set as Reply-To when the message has none.
shipmail.to · 2026-10-11
- [14]Shipmail transactional email documentation
Shipmail transactional email: an app sends from its own sending subdomain of a domain already verified in Shipmail, and replies go to a Shipmail mailbox. Sends count toward the plan's monthly quota, a sender costs nothing extra, Activity shows delivery status, and a retry with the same Idempotency-Key returns the first message. Every email from a sender carries its mailbox's address as Reply-To, so replies arrive in that mailbox's Transactional folder; the sending address itself cannot receive email. On a paid plan, an organization's transactional email starts at a safety limit of 1,000 recipients a day, raised daily to twice the highest clean day of the last 7 days, up to 25,000 automatically; the plan keeps 80% of its daily limit as a floor; a migration review with the last 30 days gets an answer within one business day.
shipmail.to · 2026-11-09
- [15]Shipmail domain setup documentation
Adding a domain to Shipmail: four DNS records (MX, SPF, DKIM and DMARC), published automatically or by hand, suggested merging of an existing SPF record, and verification that rechecks the records every 30 seconds.
shipmail.to · 2026-10-11
Questions worth answering
Common questions about Cloudflare Email Routing alternative.
Is Cloudflare Email Routing free?
How many addresses can Cloudflare Email Routing handle?
Can Cloudflare Email Routing forward to multiple addresses?
How do I turn off Email Routing in Cloudflare?
Can I keep Cloudflare DNS and use Shipmail for email?
Related guides
More on Shipmail pricing, comparisons, and team workflows.
Email, newsletters and booking pages on your own domain, in one plan.
Get started for free