Limits
Email sending quotas, rate limits, and how to request higher limits for production use
Cloudflare Email Service has the following limits to ensure optimal performance and prevent abuse. These limits apply to emails sent via both the REST API and the Workers binding unless noted otherwise.
Your account may have daily sending limits based on Cloudflare's assessment of your account standing. These limits are applied on a per-account basis, may vary, and may be adjusted over time based on your sending behavior. If you need higher sending limits, contact Cloudflare Support ↗ to request an increase.
When you first start using Email Service, you can send emails to verified email addresses in your account. This allows you to test and develop your application before sending to arbitrary recipients.
Accounts on a paid plan can send emails to any recipient, subject to daily sending limits.
| Component | Limit | Notes |
|---|---|---|
| Recipients (to, cc, bcc) | 50 per email | Combined across all recipient fields |
| Subject line | 998 characters | RFC 5322 compliant |
| Total message size | 25 MiB | Including attachments |
| Header size | 16 KB | All custom headers combined |
The following limits apply only when sending emails via the Workers binding. They do not apply to the REST API.
| Limit | Value | Notes |
|---|---|---|
| CPU time | 50ms per request | Standard Workers CPU limit |
| Subrequests | 50 per request | Includes email send operations |
| Memory | 128MB | Standard Workers memory limit |
All email sending must follow applicable anti-spam laws and regulations to maintain good standing and deliverability.
- CAN-SPAM Act (United States)
- GDPR (European Union)
- CASL (Canada)
- Include proper unsubscribe mechanisms
- Honor opt-out requests promptly