On paper, both tools look similar. They route inbound email from addresses like
hello@yourdomain.com into an existing inbox. That is enough for a hobby
project, a personal site, or a simple one-person setup.
But business buyers usually need more than “mail arrives in Gmail.” They need a setup that works with customer-facing aliases, supports a polished reply workflow, avoids DNS lock-in, and still feels manageable when the company adds more domains, more addresses, or more people.
Quick verdict
| Question | Cloudflare Email Routing | Forward |
|---|---|---|
| Best for free receive-only forwarding | Best fit | Yes |
| Works without moving your DNS to Cloudflare | No | Yes |
| Better fit for branded business email workflows | Limited | Best fit |
| Supports scaling beyond a simple solo setup | Limited | Best fit |
| Best overall choice for business email | Only for basic setups | Best fit |
If you only need basic inbound forwarding and already run Cloudflare DNS, Cloudflare is a solid free option. If you want a business-ready setup that leaves more room for branded reply workflows and operational flexibility, Forward is the better choice.
Who each option is for
Cloudflare Email Routing is best for:
- personal projects and side sites
- founders already committed to Cloudflare DNS
- very basic inbound forwarding with a few aliases
- users optimizing mostly for “free” and not for workflow depth
Forward is best for:
- small businesses using multiple customer-facing aliases
- teams that want to keep Gmail or Outlook while using branded addresses
- businesses that do not want DNS lock-in
- operators who need a cleaner long-term setup than a receive-only utility
Feature comparison
| Need | Cloudflare Email Routing | Forward |
|---|---|---|
| Forward email from your domain | Yes | Yes |
Create common aliases like hello@ and support@ |
Yes | Yes |
| Use your existing DNS provider | No | Yes |
| Works well as part of a branded Gmail reply workflow | Limited | Best fit |
| Good fit for multiple domains and business routing | Limited | Yes |
| Purpose-built for email operations | No | Yes |
Where Cloudflare wins
Cloudflare Email Routing wins on one simple thing: it is a convenient free add-on if you are already in the Cloudflare ecosystem. If your domain already uses Cloudflare nameservers and you only need mail forwarded into one inbox, it is hard to beat the simplicity.
- free for basic receive-only forwarding
- easy if your DNS already lives in Cloudflare
- good enough for simple personal or low-stakes setups
- works well when “mail arrives” is the entire requirement
Where Forward wins
Forward becomes the stronger option once email starts acting like part of the business instead of just a technical convenience. That usually happens faster than most teams expect.
- No Cloudflare DNS requirement. Use the DNS provider you already trust.
- Better business fit. Forward is built around business email routing, not as a side feature.
- Cleaner branded workflow. It fits better with the “custom domain in Gmail” use case buyers actually want.
- More room to grow. Adding aliases, domains, and routing rules stays aligned with business use.
- Focused product value. The product exists to solve email forwarding well, not incidentally.
Biggest Cloudflare Email Routing limitations
The biggest limitation is not a missing checkbox. It is that Cloudflare Email Routing is still a narrow receive-and-forward tool. That matters when a business expects a more complete branded email experience.
- DNS lock-in. You need Cloudflare nameservers. If your domain lives on Route 53, Porkbun, Google Cloud DNS, or anywhere else, you cannot use Cloudflare routing without moving the whole DNS setup.
- Receive-first design. The product solves inbound routing well, but businesses often need a better answer for branded replies and daily workflow, not just inbox delivery.
- Less aligned with growing operations. Once you add multiple aliases, multiple brands, or customer-facing workflows, a lightweight free routing utility can start to feel thin.
When businesses outgrow Cloudflare
Businesses usually outgrow Cloudflare Email Routing when one of these things becomes true:
- you want
sales@,support@,billing@, andfounder@to feel like part of one system - you want Gmail-based replies from branded addresses to feel less improvised
- you do not want DNS decisions to dictate your email routing product
- you manage more than one domain or more than one public-facing brand
- you want a business email tool, not only a free DNS-side utility
That is the real dividing line in this comparison. Cloudflare is enough for “I need some forwarding.” Forward is better for “I need this to work like part of the business.”
Do you need Google Workspace for either option?
Not always. Many small businesses do not need full mailbox hosting for every public-facing
address. A lean setup often looks like this: use forwarding for addresses like
hello@ and support@, route them into Gmail, and only pay for full hosted inboxes
when the workflow actually demands them.
If that is your goal, read Do You Actually Need Google Workspace? (Probably Not) and How to Set Up Professional Email for Your Domain (Step-by-Step).
How to switch from Cloudflare Email Routing to Forward
If Cloudflare was enough at first but now feels limiting, the switch is straightforward:
- add your domain in Forward
- set the required MX and TXT records in your DNS
- recreate your public-facing aliases
- test inbound routing before fully removing the old setup
- finish your Gmail send-as or business reply workflow
If you are still deciding whether email forwarding is the right model at all, also read Email Forwarding vs. Traditional Email Hosting and Email Deliverability Guide.
Final recommendation
Choose Cloudflare Email Routing if you want a no-cost, receive-only setup and your domain already lives on Cloudflare.
Choose Forward if you want a better business email foundation: fewer constraints, a cleaner branded workflow, and a setup that scales past the first alias.