An inbox interface versus routing infrastructure
Routing answers “where should incoming messages go?” A mailbox also answers “where do I read, search and reply?” Cloudflare’s programmable email features are useful for developers, but they are not the same product as a ready-to-use personal inbox. Freemail adds that interface while using your own Resend account for delivery.
The plans compared
Freemail Free, with paid upgrades explicitly noted, versus Email Routing on Workers Free; Email Sending Beta on Workers Paid noted separately. Prices are in USD unless stated otherwise. Commitment, renewal and regional conditions matter; check the official checkout before buying.
The table scrolls horizontally on narrow screens. Focus it to scroll with the keyboard.
| What matters | Freemail Free (paid upgrades noted) | Cloudflare Email Routing — named plans above |
|---|---|---|
| Service price | $0 Freemail subscription; Pro $5/month and Team $15/month add cloud storage | Routing: $0. Arbitrary-recipient sending needs Workers Paid, starting at USD $5/month |
| Domain and addresses | Free: one custom domain and two addresses for one user | Routing rules for your domain; destination addresses must be verified |
| Mail storage and access | Free: one receiving browser; export backups. Paid plans: cloud storage across devices | Forwards into your destination inbox; Routing itself is not a webmail inbox |
| Sending | Your own Resend account/key required on every plan; provider quotas and charges apply | Separate Workers Paid service: 3,000 outbound/month included, then $0.35 per 1,000; verified-destination sends are free |
| Workflow | Online-first webmail and browser installation; no IMAP or Exchange service | Cloudflare DNS/dashboard and optional Worker/API development |
Choose Freemail when
A small, separate inbox fits
- You want a domain inbox with a compose screen instead of building routing and sending workflows.
- You want domain conversations separate from your personal destination inbox.
Choose Cloudflare Email Routing when
Its workflow matters more
- You only need forwarding into Gmail or another existing mailbox.
- You are building custom email processing with Cloudflare Workers.
Before switching from Cloudflare Email Routing
Save your routing rules and list every alias and destination first. Recreate the addresses you need in Freemail, remembering Free’s two-address limit. Configure the required mail records without changing unrelated Cloudflare web records or account settings.
Questions about Cloudflare Email Routing and Freemail
Can Cloudflare send email now?
Yes. Cloudflare documents a separate transactional Email Sending Beta service on Workers Paid for arbitrary recipients. Free routing and sending to verified destinations have different rules. This is not a Cloudflare-hosted personal webmail inbox.
Can I leave Email Routing MX records beside Freemail’s MX records?
Do not mix unrelated providers’ MX sets as a migration shortcut. Follow the chosen provider’s DNS instructions; incoming delivery may otherwise reach the wrong system.
Sources and review notes
Checked on . The recommendation is Freemail’s assessment for individual domain owners, not an independent review or a measured reliability benchmark.
Try the workflow before moving your domain
Read the DNS guide and Free storage conditions before changing an existing mailbox. You can compare the setup with your current workflow first.
Compare all ten services · Free domain-email options · Forwarding versus a mailbox