Cloudflare

What Cloudflare Email Service is

Cloudflare Email Service is the email product of Cloudflare's developer platform. It pairs two features: Email Sending, a beta service for outbound transactional email that is available on the Workers Paid plan, and Email Routing, which handles incoming mail with Workers or forwards it to email addresses and is available on both the Free and Paid plans. The docs sum it up as a way to "Send transactional emails and route incoming emails to Workers or email addresses," and together the two features let an application both send and receive mail. It is a developer tool: the examples are code, and the product is aimed at the mail an application sends rather than newsletters or campaigns.

Cloudflare is the network and developer platform behind Workers, its storage and database products, its CDN and DNS. Its product pages describe systems "powering 20% of the Internet" and a network that lets developers deploy to 330+ cities. Email Service runs on that platform, and the docs' description of Workers says serverless applications built on it "can send emails directly from the edge."

What it is for

The overview lists the jobs Email Service is designed for:

• transactional emails such as welcome messages, password resets and order confirmations
• authentication flows: magic links, email verification and two-factor authentication
• notifications and alerts
• custom email addresses such as support@, contact@ and orders@
• email as a way to interact with agents, for example sending an email to create an issue in a ticket tracker

The worked examples in the documentation follow the same lines: specifying recipients, a user signup flow, magic link authentication, sending attachments, sending over SMTP, syncing recipient records, storing and processing incoming mail, spam filtering, and handling hard bounces.

Three ways to send

Inside a Worker, sending uses the EMAIL binding. The developer adds a send_email binding to the Wrangler configuration file and calls env.EMAIL.send() with a recipient, a from address, a subject and an HTML and plain-text body. The same Worker can export an email() handler that receives incoming messages through Email Routing. The overview's example forwards anything addressed to support@ to a team address and sends an automatic "We received your message" reply to the sender. The Wrangler file declares both sides: a send_email binding named EMAIL for outbound mail and an email binding for the routing handler. Receiving, deciding and replying inside one Worker is the part of Email Service that sets it apart from a send-only API.

Outside Workers, the REST API accepts a JSON POST to an account-scoped send endpoint authenticated with a bearer API token, and Cloudflare publishes official SDKs for the REST API in Node, Python and Go. Software that already speaks SMTP can use authenticated SMTP over TLS at smtp.mx.cloudflare.net on port 465, with an API token in place of a password. The docs carry an API reference for all three methods, separate Email Sending and Email Routing REST API references, and guides to local development for both sending and routing, so a team can build and test before it deploys.

Routing incoming mail

Email Routing sends incoming email to custom addresses, to Workers, or to external destinations. Routing rules and addresses, subdomains and MTA-STS each have a configuration guide, and the examples cover storing and processing incoming mail and filtering spam. Because Email Routing is on the Free plan and sending to verified destination addresses in the account is free on all plans, a team can set up custom addresses and forwarding, and send to its own verified addresses, without paying for Workers.

Deliverability, suppressions and observability

Cloudflare describes the deliverability side as "Automatic IP reputation management and deliverability optimization." The concepts section explains the email lifecycle, email deliverability, email authentication and suppression lists, and domain configuration has its own guide. Suppressions can be managed directly, and a changelog entry from late September adds that Email Sending suppressions can now apply to one sending domain instead of every sending domain in the account. The reference section adds a Postmaster page and a guide to the email headers the service uses. Outside Email Service, Cloudflare's docs list DMARC Management and Email security as separate products, alongside Email Routing's own entry in the product directory.

For monitoring, Analytics & Observability promises "comprehensive metrics and alerting," with documentation on metrics and analytics, audit logs and email logs. Event subscriptions are documented beside the REST APIs. Two related Cloudflare products extend this: Queues can process email events asynchronously, and Workers Analytics Engine can store and analyze custom email metrics.

Pricing and plans

Email Sending needs the Workers Paid plan. Email Routing works on the Free and Paid plans, and sending to verified destination addresses in your own account is free on every plan, even when only Email Routing is configured. Pricing and the platform's limits and quotas each have a dedicated page in the Email Service docs, and Email Sending is marked Beta throughout. The wider Cloudflare site offers a free start with no credit card required for building on the platform.

Agent tooling, community and support

Cloudflare leans into AI coding agents. The Email Service docs offer an agent setup guide, Cloudflare Skills, a Code Mode MCP server and domain-specific MCP servers, and llms.txt files that let an agent load the whole Email Service documentation in one go. Every docs page can be copied or viewed as Markdown.

Help comes through a Discord community where developers ask questions and discuss Email Service, product announcements on Twitter, a troubleshooting guide and an FAQ, and Cloudflare's general support and status pages. The site footer links a Trust Hub, compliance resources and a data protection section for teams that need to review Cloudflare's policies.

Who it suits

Cloudflare Email Service suits developers who already build on Workers and want application email without adding another vendor: signup and magic-link emails, password resets, receipts and alerts sent from the same code that handles the request, with incoming mail handled by the same Worker. The REST API, the Node, Python and Go SDKs and the SMTP endpoint make it usable from other platforms too, and teams that only want custom addresses and forwarding get Email Routing on the Free plan.

Sending is still in beta and the product is code-first, so it fits engineering teams better than marketers looking for campaigns, templates and list tools. Teams planning large volumes will want to read the Limits and Pricing pages before moving production mail across.