InboxRatio
Check your domain

Gmail sending limits: account caps, the bulk-sender line, and when to use an ESP

Search for Gmail sending limits and most of what comes back is written for one audience: people trying to push as much outreach as possible through as many mailboxes as possible without getting caught. This guide is written for everyone else. If you run a business on Google Workspace, send invoices from a personal Gmail account, or are trying to work out why a colleague's account suddenly stopped sending, the useful answer is not a list of workarounds. It is a clear picture of two different things Google calls limits, what the published numbers are, and the point at which the honest fix is a different tool. The short version, from Google's documentation as checked in September 2026: about 500 messages a day for a personal Gmail account, 2,000 a day for a paid Workspace user, and a 5,000-a-day bulk-sender line that is not a cap at all.

Two kinds of limit that get mixed up

The first kind is an account sending limit: a cap on how much one Gmail or Workspace account can send in a rolling day. It exists to stop compromised or abused accounts from becoming spam cannons, and hitting it blocks that account from sending.

The second kind is the bulk-sender threshold in Google's Email sender guidelines: roughly 5,000 messages a day to personal Gmail accounts. It is not a cap at all. Nothing stops you sending the 5,001st message; crossing the line changes which requirements Google applies to your domain's mail, from whatever platform it is sent. Confusing the two produces both classic mistakes: treating 2,000 messages a day as a target for a Workspace mailbox, and assuming a domain that sends through an ESP is "under the limit" because no single mailbox is busy.

Personal Gmail accounts

Google's Gmail Help page on sending limits for personal accounts says you may hit a limit if you send a message to more than 500 recipients, or send more than 500 messages in a day. The documented result is a bounce or an error such as "You have reached a limit for sending mail", and Google says you should be able to send again within 1 to 24 hours.

That allowance is sized for a person. A personal account is the wrong identity for anything resembling a mailing list, and the same page points people with large distribution needs toward a Google Group rather than a bigger send.

Google Workspace accounts

Workspace accounts get larger caps, which Google publishes in its Workspace Admin documentation. As checked in September 2026, the limits per user account are:

| Limit | Published value | |---|---| | Messages per day | 2,000 (1,500 for mail merge; 500 on trial accounts) | | Recipients per message | 2,000 total, of which at most 500 external | | Recipients per message via SMTP (POP/IMAP users) | 100 | | Recipients per message via the Gmail API | 500 | | Total recipients per day | 10,000 (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 trial accounts) | | Messages auto-forwarded per day | 10,000 | | Auto-forward mail filters | 40 |

Two rows matter more than the headline 2,000. The unique external recipient cap is the one that actually binds anyone mailing a list: 2,000 different outside addresses a day is far below the message count most people have in mind. And the per-message recipient ceiling drops to 100 when a mail client or application submits over SMTP, which is why a CRM that "worked in testing" starts failing on a real distribution list.

Google's page also states plainly that sending limits can change without notice. Treat the table as a snapshot of the documentation, not a contract, and check Google's current page before designing a workflow around any single number.

What happens when you hit one

Per the same Workspace documentation, after reaching a limit the user can't send new messages for up to 24 hours. The account still receives mail and can use other Google services, and the restriction lifts on its own. On the wire, Google's SMTP error reference lists 550 5.4.5 ("Daily user sending limit exceeded") for the daily quota and 452 4.5.3 for a message with too many recipients. The bounce-back text your application receives will usually quote one of them.

The useful reaction is diagnostic, not mechanical. A human correspondent almost never reaches 2,000 messages or 2,000 external recipients in a day, so an account that does is telling you something: an integration is mailing through a person's credentials, a mail-merge habit has outgrown the product, or the account has been compromised and is sending on someone else's behalf. The last possibility deserves checking first, because a hijacked mailbox damages the domain reputation every other employee's mail depends on.

The SMTP relay allowance

Workspace administrators have one more route: the SMTP relay service at smtp-relay.gmail.com, configured in the Admin console for applications and devices. Google's relay documentation sets its own ceilings: a user can't send to more than 10,000 unique recipients in a 24-hour period, there is a 100-recipient limit per SMTP transaction, and Google says it might reduce the recipient limit for an account depending on its sending practices. Exceeding a relay limit returns an SMTP error at send time.

The relay suits invoices, notifications and device mail sent as your domain. It does not come with list management, bounce processing or unsubscribe handling, and the full comparison of Google's three sending routes is in sending email through Google Workspace.

The 5,000-message line is not a sending limit

Now the number that shows up in every search result and is routinely misread. Google's sender requirements define a bulk sender as one that sends close to 5,000 messages or more to personal Gmail accounts within 24 hours. Three details from Google's FAQ change how you should think about it:

  • It counts your domain, not your mailbox. Messages sent from the same primary domain count together, so a newsletter platform, a billing system and a support desk all sending as subdomains of one domain add up to one total.
  • It is permanent. Google's FAQ says bulk sender status has no expiration date. One busy day is enough.
  • It is about recipients at personal Gmail. The guidelines apply to mail sent to personal Gmail accounts. Google's FAQ says they don't apply to messages sent to Google Workspace accounts.

Crossing the line obliges your domain to authenticate with both SPF and DKIM, publish an aligned DMARC record, and support one-click unsubscribe on marketing and subscribed mail. One rule applies at every volume: keep the user-reported spam rate in Postmaster Tools below 0.3%, with 0.1% as the level Google tells senders to stay under. The DMARC side is covered in DMARC for Gmail. None of it raises or lowers what any single account can send; it governs whether Gmail accepts, rate-limits or spam-folders your domain's mail.

Why engineering around the caps backfires

The advice that dominates this topic, spreading one campaign across many mailboxes or many lookalike domains so each stays under its cap, treats the limits as the obstacle. They are not. The per-account caps are an abuse control, and the behavior they are designed to catch is precisely a correspondence identity suddenly sending list-shaped volume. Splitting that volume across accounts does not make it look like correspondence; it multiplies the identities that look wrong.

It also does nothing about the requirements that actually decide placement. Mail from Workspace mailboxes carries no List-Unsubscribe header, feeds bounces back to a human inbox instead of a suppression list, and leaves recipients who don't want it one option: the spam button. Every one of those reports lands on the same domain your staff uses for ordinary mail. We don't publish quota-evasion techniques, and the reason is practical as much as principled: a domain that relies on them puts all of its mail at risk of the spam folder, including the one-to-one messages that were never the problem.

When the answer is a sending platform

The line between "use Gmail" and "use an ESP" is not a message count. It is the nature of the mail. Correspondence, one-to-one sales follow-ups that a person actually writes, and small internal notifications belong in Gmail or Workspace. Newsletters, promotions, onboarding sequences and application mail at any volume approaching the published caps belong on infrastructure built for them: a marketing platform or a transactional provider, both profiled neutrally in our services directory.

Moving is mostly setup. Put the new stream on its own subdomain so its reputation is kept apart from staff mail, authenticate it with aligned DKIM and SPF, then warm up the sending domain before real volume. Compare providers through the deliverability benchmark, where measured placement comparisons are published as test cycles complete, rather than on marketing claims about inbox rates.

Related guides

About this guide

Written by InboxRatio Editorial. Account limits follow Google's Gmail Help page for personal accounts and the Workspace Admin documentation "Gmail sending limits in Google Workspace"; relay limits follow Google's SMTP relay documentation; error codes follow Google's Gmail SMTP errors reference; bulk-sender definitions follow Google's Email sender guidelines and FAQ. All were checked in September 2026, and Google's current pages govern if numbers change. This guide covers legitimate sending and offers no quota- or filter-evasion techniques. No vendor sponsorship influences it.

Methodology

InboxRatio's benchmark sends real campaigns through the platforms we review to a controlled seed list and records where each message lands. This guide draws on Google's documentation rather than our measurements; the protocol is in how we test and our source rules in sources.

Last updated

10 October 2026. Google's published limits and sender guidelines reviewed quarterly.

Frequently asked questions

What is the Gmail sending limit per day? For personal Gmail accounts, Google's help page says you may hit a limit above 500 messages a day or 500 recipients in one message. For Google Workspace accounts, the documented cap is 2,000 messages per day (500 on trial accounts), with further caps on total, external and unique recipients.

How long does a Gmail sending limit block last? Google's Workspace documentation says a user who reaches a limit can't send new messages for up to 24 hours; its personal-account page says you should be able to send again within 1 to 24 hours. The account keeps receiving mail meanwhile.

Is the 5,000 emails a day rule a Gmail sending limit? No. It is the threshold at which Google classifies a domain as a bulk sender to personal Gmail accounts, counted across everything sent from the same primary domain. Crossing it triggers stricter authentication, unsubscribe and spam-rate requirements, and the classification is permanent.

Does the SMTP relay service have higher limits? Yes. Google documents up to 10,000 unique recipients per user in 24 hours through smtp-relay.gmail.com, with 100 recipients per SMTP transaction, and says it may reduce an account's limit depending on sending practices.

Can I increase my Google Workspace sending limit? Google publishes the limits as per-account values and says they can change without notice; its limits page doesn't describe a way to request higher ones. If routine sending approaches the caps, the workload has outgrown correspondence infrastructure and belongs on a sending platform.

Why does my CRM fail on large sends through Gmail? Most often the 100-recipient-per-message limit for SMTP submission, or the 2,000 unique external recipients per day. Check the bounce for 452 4.5.3 or 550 5.4.5, then move list mail off the mailbox.

The limits are a description of what a mailbox is for. Keep people mail in Gmail, move list-shaped mail to a platform on its own subdomain, and confirm the new domain's records with the email authentication checker before the first send.