Each licensed Salesforce org can send single emails to a maximum of 5,000 external email addresses per day based on Greenwich Mean Time (GMT), except for the Developer Edition orgs limitation mentioned at the bottom of this article. For orgs created before Spring ’19, enforcement of this limit varies based on where the email originates.
When trying to send emails and this limit has been reached, an error will occur stating, "SINGLE_EMAIL_LIMIT_EXCEEDED". For additional information on monitoring this limit, visit this Salesforce Support YouTube Video .
Single emails sent using the email author or composer in Salesforce don't count towards this limit. There’s no limit on sending single emails to contacts, leads, person accounts, and users in your organization directly from the Account, Contact, Lead, Opportunity, Case, Campaign, or custom object pages.
In Free or Trial orgs, sending email via UI composer is also counted against this limit.
Note: In Lightning Experience, emails sent via an approval process rather than directly from the email composer count towards the limit. When using calls to alert internal Salesforce users, it is best to send them to the user's ID rather than the user's email address. This helps preserve email limits in situations where a majority of the notifications are for internal users.
For more information and details on the limitations of different email features by edition, see Email and Email Template Allocations per Edition in Salesforce Help.
Note: Developer Edition orgs and orgs evaluating Salesforce during a trial period have stricter limits on the number of emails sent per day and per email.
See also:
List Email Limitations
Mass Email Limitations
Overview of email limit types
000381534

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.