What's Changing with Cloudflare's Email Service?
Cloudflare Email Service integrates sending and receiving on Workers. No API keys needed, automatic SPF, and code-based receiving. A look at the differences from SendGrid and SES.
Resolving the Hassles of Sending and Receiving Emails All at Once
Cloudflare's "Email Service," announced in September 2025, is a new service that allows you to handle sending, receiving, and processing emails integrally on Workers. Released as a private beta, it's attracting attention among developers.
What Was the Problem?
To send emails from an app, you needed to register for an API with SendGrid, AWS SES, etc., manually set up SPF/DKIM/DMARC in DNS, and securely manage API keys. The risk of being treated as spam due to misconfiguration was always present, and receiving required a different mechanism, keeping sending and receiving disjointed.
Solved with Workers Bindings
With Email Service, you can send emails just by adding a few lines to your config file. API keys are unnecessary because Cloudflare handles authentication, reducing leak risks to zero. SPF and DKIM are also automatically configured. The sending code looks just like this:
await env.SEND_EMAIL.send({ to:[{email:"user@example.com"}], from:{email:"no-reply@yourdomain.com"}, subject:"Order Confirmation", html:"<p>Thank you</p>"});
Receiving is also Completed within Workers
Combined with the existing "Email Routing," incoming emails can also be processed within a Worker. From filtering senders to saving attachments to R2, and even linking with Workers AI, everything is completed serverlessly. It's perfect for automatic inquiry replies and transactional emails (order confirmations, password resets).
Differences from Competitors
While SendGrid and Resend take 30 to 60 minutes to set up, Cloudflare takes less than 5 minutes for DNS-managed domains. The lack of API key management is also a differentiator. Pricing assumes a paid Workers plan (from $5/month), with details on sending charges to be released after the beta ends. Note that due to a specification change starting July 2025 where Email Routing blocks emails without SPF/DKIM authentication, existing users must check their settings.
For existing Workers developers, the biggest appeal is being able to incorporate email functionality without additional infrastructure, and further feature expansion is expected toward general availability.
【References】
Cloudflare Blog "Announcing Cloudflare Email Service's private beta" https://blog.cloudflare.com/email-service/
Cloudflare Docs "Send emails from Workers" https://developers.cloudflare.com/email-routing/email-workers/send-email-workers/
Cloudflare Docs "Email Routing overview" https://developers.cloudflare.com/email-routing/