Jerbix

Cloudflare Email

Send transactional email through Email Routing in your Cloudflare account

Last updated November 3, 2026

Cloudflare Email sends through the mail routing inside your own Cloudflare account, with no third-party service account involved. Prerequisites: the domain is hosted in this Cloudflare account and Email Routing is enabled for it.

Steps

  1. Enable Email Routing. In the dashboard, go to Email → Email Routing, enable it, and

add a verified destination address.

  1. Configure the MX records. Point the domain's MX at Cloudflare's routing servers as the

dashboard shows:

RecordValue
Root MXroute1.mx.cloudflare.net (use the full list from the dashboard)
Root TXTv=spf1 include:_spf.mx.cloudflare.net ~all
DKIMTXT at cf2024-1._domainkey (added automatically when Email Routing is enabled)

Email Routing receives only: a forwarded message cannot be replied to from the original address — reply from the receiving account instead.

  1. Declare the `EMAIL` binding. Add a send_email binding in wrangler.jsonc. The binding

name must be EMAIL, because that is the name the code reads:

``jsonc title="wrangler.jsonc" "send_email": [ { "name": "EMAIL", "destination_address": "<your-verified-address>" } ] ``

This block ships commented out and the sample value REPLACE_ME is not a valid delivery address — replace it with a real one before enabling. destination_address restricts the binding to a specific verified address; use the address you actually send to.

  1. Set the sending address. MAIL_FROM wins; CLOUDFLARE_EMAIL_SENDER is only the fallback:

``bash MAIL_FROM=noreply@<your-domain.com> ``

Neither variable uses a `VITE_` prefix. MAIL_FROM must be a plain email address; a display name is rejected.

  1. Switch provider and deploy. In src/config/website.ts:

``ts mail: { enabled: true, provider: 'cloudflare', supportEmail: '<your-support-email>' }, ``

Then hand the runtime secret to the Worker and deploy:

``bash pnpm exec wrangler secret put MAIL_FROM pnpm deploy ``

Difference from Resend

Mail goes through the routing inside your account — no third-party service, no paid sending tier. The trade-off is that the domain must live on Cloudflare and sends are limited to the account's verified addresses.

Verify

bash
pnpm run check:env

The mail item should stop reporting missing configuration; whether the binding exists is listed by pnpm check as a deployment check. Then trigger a sign-up or a contact form submission and confirm the message is actually delivered.

bash
pnpm email:dev

Previews the templates in src/mail/templates/ on port 3001.

Notes

  • The Cloudflare Email binding can only send to verified addresses — check your account's

limits before deploying.

  • CLOUDFLARE_EMAIL_SENDER is only consulted when provider is cloudflare.

Once mail works, continue with the contact form in Email Overview, or Newsletter.