Send WordPress Email Through Cloudflare

It stops WordPress from mailing out of your web server and hands each message to Cloudflare Email Service. The plugin takes over wp_mail, so core notices and mail from other plugins all reach Cloudflare through its Email Sending API. It also logs every send, sets one from name and address for the site, and includes a test send.

Yes. No charge, no paid tier, no license key, and nothing sits behind an upgrade. It installs from the WordPress Plugin Directory like any free plugin. The sending service behind it belongs to Cloudflare, and the next answer covers that.

Yes, though the money goes to Cloudflare, not us. Email Sending needs the Workers Paid plan on the account you send from, and your sending domain must be onboarded for Email Sending on the account that owns the API token. The plugin cannot work around either. If you already pay for Workers, you have nothing more to buy.

The API. It calls the Cloudflare Email Sending API over HTTPS, so you never enter an SMTP host, port, or username. You supply your Account ID and an API token, and each wp_mail message goes out against your own Cloudflare account.

It is Cloudflare’s email product for developers, with outbound sending and inbound routing in one place. It targets transactional mail: password resets, order confirmations, verification messages, and alerts. Workers reach it through a native binding, any platform can call its REST API, and authenticated SMTP exists too. This plugin uses the REST API, so an ordinary WordPress site needs no custom code.

Routing handles incoming mail and forwards what people send to addresses on your domain. Sending handles outgoing mail. Both sit under Cloudflare Email Service but do opposite jobs. The plugin only deals with mail leaving WordPress, so you do not need Routing, and switching it on will not make your site send anything.

Three things: a Cloudflare account on the Workers Paid plan, the sending domain onboarded for Email Sending on that account, and an API token with permission to send. Have them ready first, because the plugin uses them but cannot make them. Once you have the token, the WordPress side takes a couple of minutes.

Activate the plugin and open its settings. Type in your Cloudflare Account ID, paste the API token, and fill in the from address and from name for the site. Save, then run the test send. If the message arrives, WordPress is sending through Cloudflare and you are done.

Yes, if the plugin calls wp_mail, and nearly all do. Because this plugin replaces wp_mail itself rather than hooking into other plugins one at a time, anything built on the standard function is covered on activation. The exception is a rare plugin that opens its own connection and skips wp_mail entirely.

Many shared hosts block outbound mail or send it unauthenticated from an IP address with no reputation. A mailbox provider then sees a message claiming to be from your domain with nothing to back it up, and it drops the message or files it as spam. No error appears, so the site looks healthy while receipts and password resets disappear.

Each entry holds the recipients, subject, body, headers, timestamp, delivery status, and Cloudflare’s response. That settles the question of whether a message left and when. If a customer reports a missing receipt, the log tells you at once whether to look at your site or at their inbox.

You choose: 7, 14, 30, 60, 90, 180, or 365 days, or forever. The default is 30 days. The log lives in your database, so a busy store sending hundreds of messages daily will want a shorter window, since a table that never shrinks makes every backup heavier. A cleanup button applies the setting right away.

Both, and the change covers the whole site. WordPress defaults to a generic sender that rarely matches your brand, and plugins inherit it. Set the from address and from name once and every message follows, with no theme edit and no functions.php snippet for the next update to wipe out.

Run the test send from the settings screen. It mails a real message over the connection you configured and reports the result. A wrong token, a domain not yet onboarded, or a from address your account may not use will show up there during setup, not in a complaint from a customer.

It is in beta, and Cloudflare says features and APIs may change before general availability. Email Sending entered public beta in April 2026. Whether to run production mail on it is your call, and a beta carries no promise of a mature product’s stability. The email log helps, since you can watch real delivery results instead of guessing.

It is listed in the WordPress Plugin Directory, so you can install it from the Plugins screen in your admin with no download. Questions about the plugin come to us. Questions about your Cloudflare plan, domain onboarding, or API tokens go to Cloudflare, because we cannot see inside your account.