Cloudflare has launched a private beta for its new Email Service, allowing developers to send and receive transactional emails directly from their applications using Cloudflare Workers.
Quick Summary – TLDR:
- Cloudflare introduced a private beta of its new Email Service that supports both sending and routing emails.
- Developers can now use Cloudflare Workers to send transactional emails with built-in security and DNS configurations.
- The service is designed to improve email deliverability, speed, and observability.
- Email Sending will be available to paid Workers users, while Email Routing remains free.
What Happened?
Cloudflare announced the private beta release of Email Sending, a powerful new feature added to its existing Email Routing product. Together, they now form the Cloudflare Email Service, a comprehensive solution that enables developers to send and receive emails directly from their applications using Cloudflare Workers.
With a focus on developer experience, reliability, and speed, the company aims to eliminate the traditional pain points of managing transactional emails.
We’re announcing a private beta for Cloudflare’s new Email Service today.
— Kristian (@kristianf_) September 25, 2025
In the past, you could process emails in a Worker, now you can send emails too.
Crucial app infrastructure in the same easy-to-use bindings style developers love. Can’t wait to build with this. pic.twitter.com/vvZ5hJ2Zzw
A Unified Email Platform for Developers
Email plays a crucial role in the user experience, from onboarding to password resets and transactional updates. Until now, many developers struggled with setting up reliable email workflows. Cloudflare’s new solution is designed to simplify that process.
With the new service, developers can:
- Send transactional emails through Workers with a few lines of code.
- Automatically configure DNS records like SPF, DKIM, and DMARC to improve deliverability.
- Monitor bounce rates and delivery status to debug issues quickly.
- Integrate with existing frameworks like React Email for rich HTML-rendered content.
- Avoid API key leakage by binding Email directly in the wrangler.jsonc config file.
The service is globally distributed, ensuring low latency delivery across regions without the need to manage infrastructure.
Built for Modern Workflows
Cloudflare’s Email Service is deeply integrated into its developer platform. Developers can use the same tooling and environment they’re already familiar with:
- Local testing is available via wrangler so that devs can simulate email journeys without switching environments.
- Email processing can be combined with other Cloudflare services like R2 for attachment storage and Queues for async task handling.
- Inbound emails can be routed, parsed, and used to automate workflows like ticket creation, invoice processing, or even AI-powered summarization using Workers AI.
Email Routing and Sending: A Complete Loop
While sending email is important, Cloudflare also emphasizes the importance of receiving and processing emails. The existing Email Routing tool lets developers create programmatic workflows for incoming messages. Combined with the new sending feature, this opens the door to closed-loop communication flows.
For example:
- A user sends a support query.
- A Cloudflare Worker receives and parses the message.
- It creates a support ticket in a third-party system.
- An immediate confirmation is sent back to the user using Email Sending.
This seamless integration turns Cloudflare into a one-stop shop for building intelligent, email-based workflows.
Pricing and Availability
The new Email Sending feature will require a paid Workers subscription. Cloudflare says it will charge based on the number of messages sent, though pricing is still being finalized. Importantly, Email Routing remains free and will continue to be available as part of the platform.
Developers interested in trying out the new features can sign up for the private beta waitlist, with general availability expected soon.
SQ Magazine’s Takeaway
Honestly, this is a smart and overdue move from Cloudflare. As someone who’s wrestled with email delivery and DNS setup in dev projects, I know how annoying and fragmented this stuff can get. By wrapping email sending and routing into the same Cloudflare ecosystem where many developers already live, it removes friction and saves time. Plus, the integration with React Email, Workers AI, and built-in DNS configuration just screams developer-first design. If you’re building apps that rely on email, this could be a game changer.
