Free Forwarding Options, Including Custom Logic With Workers
Free email forwarding is one of those services that looks commoditized until you push on the edges. Most providers give you a handful of aliases, a catch-all, and little else. Cloudflare Email Routing sits in a different category because it runs on the same network as Cloudflare DNS and can be extended with Cloudflare Workers, which means the ceiling on what you can build for $0 is unusually high. This comparison covers five free options, from the simplest alias tool to a programmable forwarding pipeline, and flags the limits that actually bite in production.
Cloudflare Email Routing as the baseline for free forwarding
Cloudflare Email Routing forwards email for domains using Cloudflare DNS, and the setup is short: add the domain to your Cloudflare account, delegate nameservers, and let the dashboard add the MX, SPF and DKIM records automatically. There is no per-mailbox fee and no cap on the number of domains you can attach, which is why it has become the default answer for people running side projects and personal domains. The catch is architectural: Cloudflare Email Routing does not support sending or replying from the domain. It is inbound-only. You receive at your custom address and reply from whatever mailbox you forwarded to.
Two operational rules matter more than the marketing suggests. First, destination addresses must be verified before rules activate, so a typo in the destination field produces a rule that silently does nothing until you click the verification link. Second, each routing rule supports one destination address. If you want a single alias to fan out to three inboxes, that is three rules, not one rule with three recipients. Cloudflare caps routing rules per domain at 200, which is generous for a personal domain and tight for an organization mapping hundreds of role addresses.
The mechanics are worth knowing before you commit. A catch-all rule catches addresses not matched by other rules, so you can point [email protected] at one inbox without enumerating aliases in advance. This is the feature that competes most directly with paid catch-all offerings elsewhere. Messages larger than 25 MiB are rejected at the SMTP layer, so a 30 MB attachment bounces before it ever reaches your Gmail or Outlook inbox. For ordinary correspondence that limit is invisible; for people who forward scanned documents and design files it shows up quickly.
Comparing the free tiers: Gmail, Outlook, Zoho and improvmx
Google’s own forwarding tools are free but constrained. Gmail can forward incoming mail to another address through a confirmation-based setting, and Google Workspace supports routing rules, but neither gives you a custom-domain alias without paying for Workspace seats. If your goal is email forwarding to Gmail from a domain you own, Gmail is the destination, not the forwarder. The same logic applies to Microsoft 365 and Outlook: the mailbox is the endpoint, and the forwarding layer has to live somewhere else.
Dedicated forwarding services fill that gap, and their free tiers are where the comparison gets interesting. The table below summarizes what each option gives you without a credit card.
- Cloudflare Email Routing: unlimited domains and aliases, catch-all, automatic MX/SPF/DKIM, inbound only, 200 rules per domain, 25 MiB message cap, Worker extensibility.
- improvmx: free tier covers one domain with a limited alias count, forwarding to a verified destination, catch-all available, outbound SMTP is a paid feature.
- ForwardEmail (open source): free plan with alias limits, catch-all and regex-style addressing on paid tiers, self-hosting possible for teams that want control.
- Zoho Mail free plan: a real mailbox on a custom domain for a small number of users, with forwarding rules inside the account, but webmail-only access on the free tier.
- Gmail or Outlook plus a registrar forward: many registrars bundle basic forwarding, usually one address per domain, no catch-all, no logging.
The pattern is consistent: free tiers compete on alias count and catch-all availability, and they converge on inbound-only behavior. None of them let you inspect a message and decide where it goes based on its contents. That is the gap Cloudflare Workers closes.
Where the free tiers stop
Registrar forwarding is the weakest option in practice. It typically supports a single address, offers no visibility into delivery failures, and breaks silently when the destination mailbox starts rejecting mail. improvmx and similar services are stronger, but their free plans meter aliases and reserve advanced routing for paid tiers. Zoho’s free mailbox is genuinely useful if you want to send as your domain, but the mailbox quota and webmail-only access make it a poor fit for high-volume forwarding. If you set up Cloudflare Email Routing, it wins the plain-forwarding comparison on volume and simplicity, and it loses on outbound until you add a sending path.
Adding custom forwarding logic with Cloudflare Workers
This is the option most comparisons miss. Cloudflare Workers can intercept inbound mail handled by Email Routing, parse the message, and decide what to do with it before delivery. The Worker receives the raw message, exposes headers and body, and can forward, drop, or rewrite based on conditions you write in JavaScript. Because Workers have a free daily request allowance, the whole pipeline stays at zero cost for personal and small-team volumes. No other free forwarding service offers conditional logic at this level.
Practical examples are easy to sketch. You can forward messages to a priority inbox when the subject contains “invoice” and to an archive address otherwise. You can drop mail from known spam senders without training a filter. You can route by sender domain so that mail from a specific client lands in a labeled Gmail folder via a plus-address. You can strip or rewrite headers before forwarding, which helps when the destination provider flags forwarded mail. The Worker email processing model also lets you store a copy in R2 or KV for retention, though that moves beyond pure forwarding.
A minimal Worker pattern for subject-based routing
The code shape is straightforward. An email handler receives the message, reads the headers, and calls the forwarding API with a destination address. A conditional on the subject line is a few lines of JavaScript. The Worker is bound to your Email Routing configuration in the Cloudflare dashboard, and the route fires for every message that matches the rule you attached it to. Testing is the part people underestimate: send real messages with varied subjects and confirm the destination receives them, because a thrown exception in the Worker results in the message being rejected rather than delivered.
Two constraints shape what you can build. The 25 MiB message size limit still applies, and Workers have CPU time limits per invocation, so heavy parsing of large MIME bodies is not free in the performance sense. Keep the logic to header inspection and simple string matching unless you have measured the cost. Also remember that each routing rule still supports one destination address, so a Worker that fans out to multiple recipients has to issue multiple forwards or hand off to a downstream service.
Picking the right free option for your setup
If you want a custom domain that receives mail in Gmail with no maintenance, Cloudflare Email Routing is the shortest path. Verify the destination address, enable the catch-all if you want it, and you are done in under ten minutes. If you need to send as the domain, pair it with a free Zoho mailbox or a Gmail “send as” configuration using an SMTP relay, and accept that outbound is a separate problem from inbound forwarding.
If you need conditional routing, the Worker path is the only free option that delivers it. Start with one rule and one condition, confirm delivery, then expand. Keep a plain forwarding rule as a fallback so that a Worker failure does not black-hole your mail. The Cloudflare Email Service groups Email Routing and outbound sending under one product line, so the outbound gap is narrowing, but for now treat inbound and outbound as two decisions rather than one.
For teams evaluating AllMail-style consolidation or migrating between providers, the practical test is simple: count your aliases, decide whether you need catch-all, check the message size ceiling against your actual attachments, and confirm whether you need logic beyond a static mapping. If the answer to the last question is yes, Cloudflare Workers with Email Routing is the free option that actually does the job, and the rest of the list becomes a fallback rather than a first choice.