Send WordPress Email Through Cloudflare

WordPress stops sending mail from your web server and sends it through Cloudflare Email Service. The plugin takes over the wp_mail function, so core notifications and messages from other plugins all reach Cloudflare through its Email Sending API. It also logs every send, sets one from name and from address for the whole site, and includes a test send so you can confirm the setup.

Yes. There is no charge, no paid tier, no license key and nothing locked behind an upgrade. It installs from the WordPress Plugin Directory like any other free plugin. The sending service behind it is a different matter, because that belongs to Cloudflare, and the next answer covers it.

Yes, though the payment goes to Cloudflare. Email Sending needs the Cloudflare Workers Paid plan on the account you send from, and the sending domain has to be onboarded for Email Sending on the account that owns your API token. The plugin has no way around either. If you are already on Workers Paid, you have nothing more to buy.

It is the email product Cloudflare offers developers, with outbound sending and inbound routing in one service. It is meant for transactional mail such as password resets, order confirmations, verification messages and alerts. Workers can reach it through a native binding, any platform can use its REST API, and there is authenticated SMTP as well. This plugin talks to the REST API, so a normal WordPress site can use it without custom code.

Email Routing deals with incoming mail and forwards messages sent to addresses on your domain. Email Sending deals with outgoing mail. Both live under Cloudflare Email Service, but they do opposite jobs. The plugin only handles mail leaving your WordPress site, so you do not need Routing, and turning it on will not make the site send email.

You need three things: a Cloudflare account on the Workers Paid plan, the domain you plan to send from onboarded for Email Sending on that account, and an API token with send permission. Get them ready first, because the plugin uses them and cannot create them. With the token in hand, setup inside WordPress takes a couple of minutes.

Install and activate it, then open the settings screen. Enter your Cloudflare Account ID, paste the API token, and fill in the from address and from name the site should use. Save, then run the test send. If the test message arrives, WordPress is sending through Cloudflare and setup is finished.

Yes, provided the plugin uses wp_mail, and nearly all of them do. Since this plugin replaces wp_mail itself instead of hooking into plugins one by one, anything built on the standard WordPress mail function is covered as soon as you activate it. The exception is the rare plugin that opens its own connection and skips wp_mail altogether.

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

Every entry records the recipient, the subject, when the message went out and the delivery status returned by the send. That answers the usual question: did it leave, and when? When a customer says a receipt never came, the log tells you right away whether to look at your site or at their inbox.

As long as you choose. Retention is a setting, so you decide how much history to keep. A quiet site can hold months of entries without trouble, while a busy store sending hundreds of messages a day will want a shorter window, since the log sits in your database and a table that never shrinks makes every backup heavier.

Yes, both, and the setting covers the whole site. WordPress ships with a generic default sender that seldom matches your brand, and plugins usually inherit it. Setting the from address and from name once fixes every message the site sends, without theme edits or a snippet in functions.php that the next update could wipe out.

Run the test send from the settings screen. It sends a real message over the connection you set up and reports what happened. A wrong token, a domain not yet onboarded for sending, or a from address the account may not use will all show up right there, during setup, instead of in a complaint from a customer whose receipt never came.

It is still in beta, and Cloudflare says features and APIs may change before general availability. Email Sending entered public beta in April 2026. Plenty of sites use it in production, but make that call with open eyes and do not assume the stability guarantee of a mature product. The email log helps here, because you can watch real delivery results instead of guessing.

The plugin is listed in the WordPress Plugin Directory, so you can install it from the Plugins screen in your own admin without downloading anything. Questions about the plugin come to us. Questions about your Cloudflare account, plan, domain onboarding or API tokens go to Cloudflare, because we have no access to anything inside your account.