One Number Everyone Knows — And All the Others That Actually Bite
The 5,000 daily mass email cap is the Salesforce email limit most teams know. It is not the only one. Salesforce also caps single emails per user, restricts List Email batch sizes in Lightning, and constrains Apex API calls per transaction. Understanding the full picture — not just the headline figure — is what separates teams that plan sending strategically from those that discover a hard ceiling mid-campaign.
The 5,000 Daily Mass Email Limit
Salesforce restricts every production org to 5,000 outbound mass emails per rolling 24-hour window, regardless of edition or team size. This limit is org-wide: every campaign, list send, and automated bulk workflow competes for the same shared pool. According to Salesforce’s official email limits documentation, the cap applies exclusively to external recipients — emails to licensed Salesforce users use a separate internal allocation. The Salesforce mass email limits page covers how the pool is consumed across sending methods.
Single Email Limits by User
Each licensed Salesforce user can send up to 5,000 single emails per day from individual Contact, Lead, or Person Account records. This is a per-user limit — a 15-person team has 75,000 combined daily single email capacity. Single email limits track independently from the mass email pool; consuming one does not reduce the other.
For most organizations, single email limits are rarely the binding constraint. The org-wide mass limit runs out first. For a side-by-side breakdown of both limits, see Salesforce email limitations per day.
List Email Batch Size Constraints
Beyond the daily 5,000 ceiling, Salesforce caps how many recipients a single List Email operation can target. In Lightning, “Select All” on a filtered list view supports up to 500 recipients per send. Manually selecting individual records caps at 200. These are UI constraints, not daily-limit deductions — they control how many records can be targeted in one operation.
Teams with audiences larger than 500 must execute multiple batch sends or use campaign-based sends. See Salesforce Mass Email from List View and Send Mass Email in Salesforce Lightning for step-by-step guidance on each approach.
API and Apex Email Limits
Programmatic Apex sends another layer of constraints:
- MassEmailMessage: 5,000 per day (shared with the org pool), 250 target object IDs per call, 10 sendEmail() invocations per Apex transaction
- SingleEmailMessage: 5,000 per user per day, 100 recipients per call, 10-invocation-per-transaction limit
API sends draw from the same org-wide daily quota as UI sends — Apex bulk sends, and marketing campaign sends compete for the same 5,000 allocation. The 250-recipient-per-call ceiling on MassEmailMessage requires large lists to be split into batches via Batch Apex. Full details in Salesforce Mass Email API.
How Limits Vary by Edition and Environment
Edition does not increase the 5,000 ceiling — Enterprise and Unlimited orgs face the same cap as Professional. Key differences by environment:
- Developer Edition and all sandboxes: 15 emails per day to prevent test data from reaching live recipients
- Professional Edition: mass email may require full API access to be purchased separately
- All production orgs: 5,000 external mass emails per rolling 24-hour window
The rolling reset creates planning risk: a large morning campaign can block afternoon sends on the same calendar date. Monitor consumption via Setup > Email Log Files before large sends.
How to Monitor and Scale Beyond Email Limits
Native monitoring starts with Setup > Email Log Files, which provides a timestamped record of sends and delivery statuses. Coordinating a shared sending calendar across marketing, sales, and customer success prevents teams from unknowingly exhausting the org pool before critical sends go out.
For teams that consistently hit the ceiling, MassMailer removes the mass email cap entirely — operating 100% inside Salesforce with no middleware or data exports. All sent data stays in CRM records and flows into standard reports. See how 20/20 ForeSight scaled email volume 15x after hitting native limits, or compare MassMailer vs Salesforce Marketing Cloud to evaluate the right scaling path.
Not Sure Which Limit Is Blocking Your Team?
Book a 20-minute call. We’ll review your Salesforce email setup, identify which limits are affecting your sends, and show you exactly how MassMailer removes them — without touching your CRM data or changing your workflows.
Key Takeaways
- Salesforce caps mass emails at 5,000 per org per day, single emails at 5,000 per user per day, and MassEmailMessage API calls at 250 recipients per call.
- The 5,000 mass email limit is org-wide — all teams, campaigns, and Apex automation share the same pool, regardless of edition or team size.
- List Email batch operations are capped at 500 recipients per send in Lightning — a UI constraint that is separate from the daily ceiling.
- Salesforce uses a rolling 24-hour window, not a midnight reset — large morning sends can block same-day afternoon campaigns.
- Developer sandboxes are limited to 15 emails per day; all production orgs share the same 5,000 external mass email ceiling regardless of edition.
- AppExchange-native tools like MassMailer eliminate the mass email cap while keeping all send data inside Salesforce records.
