Cloudflare's Email Sending service remains in private beta as of April 2026, with expanded access now rolling out to select developers on the waitlist. The service aims to fix a critical pain point for developers and business teams: building email delivery into applications without managing separate third-party vendors.
Email Sending allows developers to send transactional emails directly from Cloudflare Workers and joins the popular Email Routing product to form the new Cloudflare Email Service. This unification matters for anyone building applications that rely on timely, critical messages like password resets, signup confirmations, billing notifications, and security alerts.
What Makes Cloudflare's Approach Different
The service automatically handles DNS configuration, setting up SPF, DKIM, and DMARC records for any verified sending domain. This is significant because SPF, DKIM, and DMARC are the technical foundation of email deliverability. In the past, developers had to manually configure these authentication protocols or rely on external service providers to do it for them.
The tight DNS integration means email providers can verify your sending domain and trust your emails. Without proper authentication, transactional emails risk being filtered as spam or rejected entirely. If transactional messages go to spam, arrive late, or get blocked, users may lose access, miss payments, question whether a transaction succeeded, or stop trusting the application.
No API Keys, Native Integration
There is no separate API key to manage or risk leaking; a call to env.SEND_EMAIL.send() is all it takes. This native binding approach eliminates a common security vulnerability. Instead of managing API keys and secrets, developers can use the Email binding in their wrangler configuration to send emails securely with no risk of leaked credentials.
Features Built for Production Use
The service integrates with popular frameworks such as React Email, supports SMTP and REST API access for external services, and includes delivery observability for bounce rates, delivery events, and per-message status. In production, developers have clear visibility over emails with bounce rates and delivery events, and when a user reports a missing email, they can quickly dive into the delivery status to debug issues.
Email Service is a global service that delivers emails with low latency anywhere in the world, without the complexity of managing servers across regions. This addresses a key operational burden for growing applications.
Pricing and Availability
Email Sending will be available to paid Workers users, while Email Routing remains free. Cloudflare has confirmed the service will require a paid Workers subscription and will be charged based on messages sent, though the company has not yet published official pricing or a confirmed public beta date.
Why This Matters for Your Business
For business owners and growth teams managing email workflows, this represents a shift toward consolidation. Rather than juggling email deliverability as a separate concern, developers can embed it into the application's core infrastructure using tools they already work with daily. This can reduce setup time, eliminate vendor complexity, and lower operational costs for high-volume senders.
Cloudflare will need to publish competitive pricing and demonstrate strong deliverability before it can claim a clear position in the transactional email market, but the technical architecture supports the core requirements: reliable delivery, automatic authentication configuration, and developer-first UX.
If your team already uses Cloudflare Workers for serverless functions, the native integration could simplify your email infrastructure without introducing new dependencies or API management overhead.
