A professional email address at your own domain, such as [email protected], instantly makes a business look more credible than a generic free-mail address. The traditional way to get one was to pay for a hosted mailbox per user, every month, forever. Cloudflare Email Routing offers a simpler path for many people: forward email from any address at your domain straight to an inbox you already use, such as Gmail, for free. This guide shows you exactly how to set it up, and how to send replies that appear to come from your custom address.
TL;DR
- Cloudflare Email Routing forwards email from your domain to an existing inbox, completely free
- Setup takes minutes: Cloudflare configures the required MX and SPF records for you
- You can route specific addresses (
sales@,support@) or use a catch-all for every address - It is a forwarding service, not a mailbox; sending replies from your address needs one extra step
- Your domain’s DNS must be managed by Cloudflare to use it
- For programmatic handling of incoming mail, Email Workers let you process messages in code
What Cloudflare Email Routing Is
Cloudflare Email Routing
is a free service that receives email sent to addresses at your custom domain and forwards it to a destination inbox you already own. You do not get a new mailbox to log into; instead, mail addressed to [email protected] lands in your existing Gmail, Outlook or other inbox, with the original sender preserved.
This is ideal for the very common case where you want professional addresses on your domain but are happy to read and manage everything from an inbox you already use. There are no per-user fees and no separate webmail to check.
What Cloudflare Email Routing Does and Doesn’t Do
It is important to be clear about the boundaries, because this is where people get tripped up.
Email Routing does:
- Receive mail for any address at your domain
- Forward it to a verified destination inbox
- Support per-address rules and a catch-all for everything else
- Let you process incoming mail in code via Email Workers
Email Routing does not:
- Give you a mailbox or webmail interface
- Send outbound email on its own (it is a receiving and forwarding service)
That second point matters: out of the box, Email Routing handles incoming mail. To send a reply that appears to come from your custom address, you add one extra piece, covered below.
Cloudflare Email Routing Setup, Step by Step
You need your domain’s DNS managed by Cloudflare, because Email Routing configures the mail records for you. If your domain is already on Cloudflare, you are ready.
- Open Email Routing. In the Cloudflare dashboard, select your domain and open the Email Routing section.
- Enable it. Cloudflare will offer to add the required MX and SPF DNS records automatically. Accept this; these records tell the world that Cloudflare handles mail for your domain. You can confirm them afterwards with a quick DNS lookup .
- Add a destination address. Enter the inbox you want mail forwarded to (for example your Gmail address). Cloudflare sends a verification email; click the link to confirm you own it.
- Create routing rules. Map custom addresses to destinations, for example route
[email protected]to your verified inbox. Add as many as you need. - Optionally enable catch-all. Turn on the catch-all rule to forward mail sent to any address at your domain (including ones you never explicitly created) to your inbox. This is handy, though it can increase spam, so use it deliberately.
Within a few minutes, mail sent to your custom address will start arriving in your existing inbox.
Sending Replies From Your Custom Address
Because Email Routing only handles incoming mail, replying so the message appears to come from [email protected] needs one more step. The most common approach is to configure your existing email client to send as your custom address:
- In Gmail, use Settings, Accounts, “Send mail as” to add your custom address, supplying the SMTP details of an email-sending provider.
- This requires an outbound mail service to actually relay the message, since Cloudflare Email Routing does not send mail itself.
If you are building an application that needs to send transactional email (password resets, receipts, notifications) from your domain, that is a separate outbound concern. Cloudflare offers an email sending service for developers, and you can also trigger and process mail from a Worker. The key takeaway: routing handles receiving for free; sending uses an outbound service alongside it.
Processing Incoming Mail With Email Workers
For developers, one of the most useful features is Email Workers. Instead of just forwarding a message, you can run code on each incoming email: parse it, extract data, trigger an action, store an attachment in R2 , or forward conditionally based on the content. This turns your domain’s inbox into a programmable endpoint, which is powerful for support automation, ticketing, and webhooks-over-email patterns. If you are new to Workers, start with my overview of running code on the edge with Workers AI and the broader Workers platform.
Who Should Use Cloudflare Email Routing
Email Routing is a great fit when:
- You want professional business email addresses on your domain without paying per mailbox
- You are happy to read and manage mail from an inbox you already use
- You need multiple addresses (
sales@,support@,info@) all landing in one place - You want a catch-all so no mail to your domain is ever lost
It is not the right tool if you need full mailboxes with their own storage and webmail for a team, shared calendars, or heavy outbound sending. In those cases a hosted email suite is more appropriate. For most individuals, freelancers and small sites, though, free forwarding covers the need completely.
Key Takeaways
- Email Routing forwards mail from your custom domain to an existing inbox, for free
- Setup is quick: Cloudflare adds the MX and SPF records and you verify a destination inbox
- Route specific addresses or enable a catch-all for everything
- It receives and forwards only; sending replies from your address needs an outbound mail service
- Your domain’s DNS must be on Cloudflare to use it
- Email Workers let developers process incoming mail in code for automation
Frequently Asked Questions
Is Cloudflare Email Routing free? Yes. Email Routing is a free service for receiving and forwarding email from your custom domain to a destination inbox you already own. There are no per-address or per-user fees.
Does Cloudflare give me a mailbox? No. Email Routing is a forwarding service, not a mailbox. Mail sent to your domain is delivered to an inbox you already use, such as Gmail or Outlook. There is no separate webmail to log into.
Can I send email from my custom address with Email Routing? Not by itself. Email Routing handles incoming mail only. To send replies that appear to come from your custom address, configure “Send mail as” in your email client using an outbound email-sending provider’s SMTP details.
Do I need my domain on Cloudflare to use Email Routing? Yes. Email Routing requires your domain’s DNS to be managed by Cloudflare, because it configures the MX and SPF records needed to receive mail for your domain.
What is a catch-all address? A catch-all rule forwards email sent to any address at your domain, including ones you never explicitly created, to your destination inbox. It ensures no mail is lost, but it can also forward more spam, so enable it deliberately.
What are Email Workers? Email Workers let you run code on each incoming email rather than simply forwarding it. You can parse messages, extract data, store attachments, or forward conditionally. This is useful for support automation and processing inbound mail programmatically.
Comments