Cloudflare Launches Email Sending Service Supporting Transactional Emails
Cloudflare offers Email Sending functionality under the Workers Paid plan, allowing transactional emails to be sent via Workers bindings, REST API, or SMTP, available in public testing starting April 2026.
The Workers Paid plan includes 3,000 outbound emails per month, with additional emails charged at $0.35 per 1,000; new accounts start with a conservative daily sending limit, which is dynamically adjusted based on sending behavior, delivery rates, and account reputation, with no fixed daily cap published in the official documentation.
If the domain is already hosted on Cloudflare, the system automatically handles SPF and DKIM records when configuring the sending domain, requiring no additional manual setup; the service supports HTML, plain text, attachments, and custom headers, with a maximum of 50 recipients per email and a message size limit of 5 MiB.
The official documentation specifies that Email Sending is aimed at transactional scenarios such as account verification, order confirmations, and alerts, not for marketing or bulk emails; sending to verified destination addresses within the account is free and does not count against the quota under any plan.
Some developers report that the actual daily available quota can reach thousands of emails, suitable for low-frequency transactional scenarios like registration verification codes, password recovery, and order notifications, and integrates directly with existing Cloudflare DNS and Workers ecosystems.
Funding and attention are directed towards developers embedding email sending into existing infrastructure platforms; teams managing domain hosting and Workers deployment reduce the switching costs from external email services, while traditional independent email providers face pricing and integration pressures in small-scale transactional scenarios.
The service is still in public testing, with daily quotas increasing as reputation improves; hard bounces count against the monthly quota, while sends blocked by suppression lists do not count.
Source: Public Information
ABAB AI Insight
Cloudflare previously offered free inbound forwarding through Email Routing, initiated private testing for Email Sending in 2025, and transitioned to public testing in April 2026, incorporating sending capabilities into the Workers Paid plan, continuing its path of bundling edge computing, DNS, and security capabilities.
The capital path reflects the addition of email sending as a feature of the Workers paid plan, with resource investments in automatic DKIM signing, reputation management, and multi-protocol access, strategically locking in developers who have already used its DNS and edge computing with low barriers to integration, rather than independently competing for the large-scale email market.
This is similar to early cloud vendors bundling storage or queues as foundational platform services, and akin to some CDNs embedding security features to reduce third-party dependencies; the current phase represents a platform functionality expansion, focusing on reducing migration friction through the existing customer base.
Essentially, this represents a shift in pricing power: transactional emails transition from independent SaaS pay-per-use to embedded quotas and marginal cost pricing within the platform, simplifying authentication configuration through domain hosting, and using dynamic reputation quotas to control abuse risks, making small-scale developers more inclined to stay within a single vendor ecosystem.
ABAB News · Cognitive Laws
Infrastructure platforms first address authentication friction, then price sending quotas
Dynamic reputation quotas are better at controlling abuse than fixed packages
The switching costs for existing domain and compute customers are lower than the acquisition costs for independent email services