Gmail's sending limits in 2026 depend on the account. A personal Gmail account can send up to 500 emails a day, and to no more than 500 recipients in one email. A paid Google Workspace account can send 2,000 messages a day per user, to at most 10,000 recipients in total, 3,000 of them external, with 500 messages a day on a trial. Workspace daily limits run over a rolling 24 hours, and an account that hits one cannot send for up to 24 hours. The Gmail API adds its own quotas on top, measured in quota units per minute, and they changed on 1 May 2026.
This guide puts every Gmail limit in one place: the personal account, Google Workspace, the Gmail API, the SMTP relay service and the sender rules that apply when you send to Gmail users at volume. It ends with what those numbers mean for cold email, where the limit that actually stops you is rarely the one Google prints in a table. Every figure comes from Google's own help and developer pages, read on 8 October 2026.
What are Gmail's sending limits in 2026?
Google publishes different limits for each way you send. The figures that matter:
| How you send | Daily limit | Recipients per message | Source |
|---|---|---|---|
| Personal Gmail account | Up to 500 emails a day | 500 | Gmail Help |
| Google Workspace user | 2,000 messages a day; 1,500 for mail merge | 2,000 total, 500 external | Workspace Admin Help |
| Google Workspace trial | 500 messages a day, 500 external unique recipients | Not published separately | Workspace Admin Help |
| Gmail API | The account's own daily limits, plus API quotas | 500 | Gmail API usage limits |
| SMTP by POP or IMAP users | The Workspace user limits | 100 | Workspace Admin Help |
| SMTP relay service | 10,000 messages per user | 100 per SMTP transaction | Workspace Admin Help |
Three rules apply to Google Workspace accounts. Daily limits run over a rolling 24-hour period, not a calendar day. Google states that sending limits can change without notice. And once an account hits a limit, it cannot send new messages for up to 24 hours, although it still receives mail and works normally otherwise.
What are the Google Workspace sending limits?
Google Workspace accounts get higher limits than personal Gmail, with several counters running at once. Google's Workspace help lists these per user:
| Limit | Value |
|---|---|
| Messages per day | 2,000, or 1,500 for mail merge, 500 on a trial account |
| Recipients per message | 2,000 total, with a maximum of 500 external |
| Recipients per message over SMTP by POP or IMAP users | 100 |
| Recipients per message with the Gmail API | 500 |
| Total recipients per day | 10,000, or 1,500 for mail merge |
| External recipients per day | 3,000 |
| Unique recipients per day | 3,000, of which 2,000 external, 500 external on a trial |
| Messages auto-forwarded per day | 10,000, not counted in the daily sending limit |
| Auto-forward filters | 40 |
Recipients are counted each time a message goes out: five messages sent to ten addresses count as 50 total recipients but 10 unique recipients. Messages sent from aliases, by delegated users and by the vacation responder all count toward the user's limits.
Trial accounts. A new Workspace account starts on lower trial limits that do not rise during the trial. After you convert to a paid subscription, limits increase automatically once the domain has paid at least $100 in total, and Google says the increase can take up to 75 days after that threshold. A Workspace domain converted from a trial should not count on full limits on day one: the increase needs $100 in total payments, plus the domain cost if Google sold it, and can take up to 75 days after that.
What are the Gmail API limits?
The Gmail API has two layers of limits. The first is the same per-user sending limits as any Workspace or Gmail account, plus a hard limit of 500 recipients per message. Google's Gmail API error guide states that the API enforces the standard daily sending limits, shared by all of a user's clients, so sending through the API gives you no extra daily volume. The second layer is the API's own usage quotas, counted in quota units.
Google updated those quotas on 1 May 2026. Cloud projects that used the API between November 2025 and April 2026 keep their previous quotas; projects created on or after 1 May 2026 get the new ones:
| Gmail API quota | Limit |
|---|---|
| Per minute, per project | 1,200,000 quota units |
| Per minute, per user, per project | 6,000 quota units |
| Daily billing threshold, per project | 80,000,000 quota units |
Each method costs a set number of units. Sending a message with messages.send or drafts.send costs 100 units, reading a message with messages.get costs 20, listing messages costs 5 and setting up push notifications with watch costs 100. At 6,000 units per user per minute, one user of a new project can make up to 60 send calls a minute if it makes no other calls, far faster than the daily sending limit allows anyway. When you do hit a time-based quota, Google recommends retrying with truncated exponential backoff rather than hammering the endpoint.
Is the Gmail API free?
Today, yes, for usage under the daily billing threshold. Google's usage limits page now defines a per-project threshold of 80 million quota units per day, below which usage is not charged, and says it will share full billing details later in 2026 with at least 90 days' notice before any change takes effect. That threshold cannot be raised. 80 million units a day is 800,000 sends or 4 million messages.get calls per project, which a large inbox product can approach, so anyone building a high-volume email product on the Gmail API should watch that announcement.
Connecting other people's Gmail accounts brings a separate cost that has nothing to do with quotas. Apps that read mail use scopes Google classifies as restricted, and a public app using them must pass Google's verification, plus an annual security assessment when mail data passes through its servers. Our EmailEngine review covers what that involves for a self-hosted mailbox API, and our breakdown of Nylas pricing covers the managed alternative, where you verify your own Google app unless you pay for Nylas's pre-verified Google Shared App, an add-on to the annual Pro or Enterprise plan.
What are the Google Workspace SMTP relay limits?
The SMTP relay service routes mail from your own servers and applications through Google, and it has its own, higher limits. Each user can send up to 10,000 messages in 24 hours to no more than 10,000 unique recipients, with up to 100 recipients per SMTP transaction. Across the whole organization, Google allows up to 4.6 million non-unique recipients in 24 hours and 319,444 in any 10-minute window, and it may lower those limits based on your sending practices.
The relay is meant for on-premise devices and applications that generate outbound mail, such as ticketing systems and notifications. Using it to push cold email past the mailbox limits does not avoid the sender rules below, and it puts your whole organization's sending reputation at stake.
What happens when you hit a Gmail sending limit?
The sender gets an error such as "You have reached a limit for sending email" or "You exceeded the maximum recipients", and the account cannot send new messages for up to 24 hours. Personal Gmail accounts can usually send again within 1 to 24 hours. Workspace users keep access to the rest of their account, and the limits reset after the suspension period.
Exceeding the limits can carry heavier consequences. Google's Workspace help warns that an account exceeding its sending limits might be suspended, and that accounts that send spam might be permanently restricted from sending email. If a large number of your emails bounce because the addresses are invalid, a personal Gmail account can also be blocked from sending, and Google says you may be able to send again after 24 hours. That is why cold email lists get verified before they are sent.
Which rules apply when you send to Gmail users at volume?
Sending limits cap what a mailbox can send. Google's email sender guidelines decide whether that mail is delivered. Since February 2024, every sender to personal Gmail accounts must set up SPF or DKIM, have valid forward and reverse DNS, use TLS and keep the spam rate reported in Postmaster Tools below 0.3 percent. Senders of 5,000 or more messages a day to personal Gmail accounts, counted across the whole primary domain, must also authenticate with SPF, DKIM and DMARC, make it easy to unsubscribe, with one-click unsubscribe on marketing messages, and honour unsubscribe requests within 48 hours.
Google recommends keeping the spam rate below 0.10 percent and never reaching 0.30 percent. Since November 2025, Gmail has been ramping up enforcement, with temporary and permanent rejections for mail that does not meet the requirements. These formal requirements apply to mail sent to personal Gmail accounts, and most B2B cold email lands in Workspace-hosted inboxes instead, but spam complaints hurt a domain's reputation either way: a mailbox can stay well inside its 2,000 daily messages and still lose its deliverability if recipients mark its mail as spam.
What do Gmail's limits mean for cold email?
Google's limits are ceilings, not targets. A cold email program that sends close to 2,000 messages a day from one Workspace mailbox is far more likely to run into spam complaints than into the sending limit. Teams that run cold email at volume usually work the other way around:
- Many mailboxes, low volume each. Volume is spread across a pool of mailboxes, each sending far below Google's ceiling, so no single mailbox carries all the volume, although mailboxes on the same domain still share its reputation.
- Secondary domains. Cold email goes out from separate registered domains, not subdomains of the main domain, so a reputation problem is less likely to reach invoices, support or internal mail.
- Warmed, paid accounts. Accounts that start on a Workspace trial keep trial limits until conversion, and new mailboxes have no reputation; Google's own guidelines advise avoiding sudden volume spikes.
- Authentication and unsubscribe from day one. SPF, DKIM, DMARC and a working unsubscribe are baseline, not optional extras.
- Verified lists and fast stop rules. Invalid addresses cause bounces, and anyone who replies or asks to stop should leave the sequence immediately.
This is the layer cold email tools exist to run, and a part that is easy to underestimate when you build on the Gmail API directly. Our comparison of cold email software and our guide to Instantly alternatives cover the tools, and our outreach API comparison covers the APIs you can build on. AI-driven outreach multiplies the same risk, as our guide to AI SDRs explains.
On Swarmhit, the cold email API, in beta and opened workspace by workspace, runs that layer for you. One campaign spreads its volume across a mailbox pool, with one mailbox per lead for the whole thread, per-mailbox daily caps and today's usage readable in the API, sending windows, and bounce and complaint suppression. You can connect your own Google, Microsoft or IMAP mailboxes, or buy a domain and Google Workspace or Microsoft 365 mailboxes that arrive connected and already warming, and join campaigns once their warmup hold ends.
Spread cold email across mailboxes, not onto one
Swarmhit's cold email API runs mailbox pools, per-mailbox daily caps, sending windows and bounce suppression in the same campaigns as LinkedIn.
Cold email in beta from $59 a month for 50,000 sends, unlimited mailboxes; pricing may change during the beta.
FAQ
How many emails can I send per day with Gmail?
A personal Gmail account can send up to 500 emails a day, and to no more than 500 recipients in a single message. Google does not say exactly when the counter resets for personal accounts. If you hit the limit, Gmail shows an error, and Google says you should be able to send again within 1 to 24 hours. Workspace accounts get higher limits, counted over a rolling 24 hours.
How many emails can Google Workspace send per day?
A paid Google Workspace user can send 2,000 messages a day, or 1,500 through mail merge, to at most 10,000 total recipients, 3,000 external recipients and 3,000 unique recipients, 2,000 of them external. Trial accounts are limited to 500 messages a day. Limits rise after conversion once the domain has paid at least $100, which Google says can take up to 75 days.
What is the Gmail API rate limit?
Since 1 May 2026, the Gmail API allows 1,200,000 quota units per minute per Cloud project and 6,000 quota units per minute per user. Sending a message costs 100 units, so one user of a new project can make up to 60 send calls a minute. Projects that used the API between November 2025 and April 2026 keep their previous quotas. API sends still count against the account's daily sending limit.
Does sending through the Gmail API raise the daily limit?
No. Google's Gmail API error guide says the API enforces the standard daily sending limits, shared by all of a user's clients: API, web or SMTP. The API adds its own per-minute quotas and a 500-recipient cap per message, but it does not lift the 2,000 messages a day on Workspace or the 500 emails a day on personal Gmail.
How long does a Gmail sending limit last?
Up to 24 hours. Once an account hits a sending limit, it cannot send new messages for up to 24 hours, then the limit resets. Personal Gmail accounts can often send again within 1 to 24 hours. Workspace users can still receive mail and use other Google services meanwhile. Accounts that exceed their limits risk suspension, and accounts that send spam can be permanently restricted.
What is the Google Workspace SMTP relay limit?
The SMTP relay service allows each user up to 10,000 messages in 24 hours, to at most 10,000 unique recipients, with no more than 100 recipients per SMTP transaction. Across an organization, Google caps relay traffic at 4.6 million non-unique recipients in 24 hours and 319,444 in any 10-minute window, and can lower those limits based on your sending practices.




