Skip to content
Sales Pitch
Menu
English

500 vs 2,000: Gmail Sending Limits, How They're Counted, What to Do

, 16 min read

500 vs 2,000: Gmail Sending Limits, How They're Counted, What to Do

Decorative Gmail sending limits title card

Free Gmail accounts cap out at roughly 500 messages a day, while Google Workspace accounts get about 2,000 messages a day, with separate caps on total, unique, and external recipients. These limits reset on a rolling 24-hour window, and the method you use to send (web, SMTP, API) changes how many recipients fit in a single message. If your outreach needs more volume, the correct move is to follow Google’s Postmaster requirements or shift to a dedicated bulk-sending provider rather than trying to push past the caps.

TL;DR:

  • Sending over 1,500 recipients daily via mail merge or multi-step sequences exceeds Google’s recipient limits, risking temporary suspension.
  • External-recipient counts are often reached before message caps in high-volume outreach, especially when including CCs or auto-forwarding rules.
  • Using the Gmail API or dedicated bulk senders helps avoid individual account throttling, but still respects overall recipient and message limits.
  • Hitting a limit prompts a temporary pause of outbound emails for 24 hours, with inbound mail and workplace functions remaining unaffected.
  • To scale safely, follow Google’s sender guidelines, gradually increase volume, and monitor reputation metrics through Postmaster Tools.
Usesalespitch
Plan More Reliable B2B Outreach
Get actionable insights, practical templates, and tools for improving cold email strategies, deliverability, and sales efficiency.
Visit Sales Pitch

Table of Contents

1. Gmail and Google Workspace limits at a glance

Before planning any outreach sequence, it helps to see every limit side by side. The figures below come directly from Google Workspace’s official limits documentation, which separates message counts from recipient counts, a distinction that trips up a lot of senders who assume “messages sent” and “people reached” are the same number.

A few things worth noting about how these numbers actually behave:

  • The rolling 24-hour window means a block does not clear at midnight. It clears exactly 24 hours after the message that tipped you over.
  • Mail merge has its own cap of 1,500 recipients a day, separate from the general message limit, according to Google’s sending limits table.
  • Receiving mail, replying within an existing thread, and internal administrative notifications generally do not count against your outbound limits the same way new outbound campaigns do.
  • New or trial Workspace accounts start with lower caps, and some limits only increase after a domain accumulates enough paid usage, a process that Google notes can take weeks.

The practical takeaway: a sales rep sending five follow-up emails to the same 200 prospects has sent 1,000 messages by message count, but the recipient counters matter more for planning, since repeated sends to the same list consume unique-recipient capacity differently than fresh lists do.

2. How Gmail counts messages and recipients, with examples

Gmail tracks at least four separate counters: total messages sent, total recipients across all messages, unique recipients (deduplicated), and external recipients (people outside your Workspace domain). A sender can stay well under the message cap while still exhausting recipient capacity, which is the single most common reason outreach campaigns get blocked unexpectedly.

Here is how that plays out in practice:

  1. A five-step follow-up sequence sent to 1,000 prospects produces 5,000 total recipient events across the campaign, even though each individual email only goes to one person. If that sequence runs on a single Workspace account in one day, it blows past the 3,000 external-recipient daily cap, according to Google’s documented limits, even though the account never approaches its 2,000-message ceiling.
  2. A mail merge to 1,600 unique addresses exceeds the 1,500-recipient mail merge limit on its own, regardless of how many messages that merge technically generates.
  3. A single email cc’d to 50 people inside your own Workspace domain and 10 outside it counts as one message but 60 recipients, 10 of which count toward the external-recipient total.

Auto-forwarding rules, inbox filters, and group sends add another layer of complexity. A message sent to a Google Group with 300 members typically expands to 300 individual recipients for quota purposes, similar to how Exchange Online treats distribution groups as expanded recipients rather than a single addressee. Auto-forwarding rules that silently copy every inbound or outbound message to a second address can also contribute to recipient counts without the sender realizing it.

One wrinkle that catches teams off guard: if multiple domains share the same Google MX records, recipients across those domains can be counted toward the same external-recipient pool. Google’s guidance on sender issues recommends testing small batches across shared-MX domains before running a full campaign, since the counters do not always behave the way an org chart would suggest.

Pro Tip: Before launching a multi-step sequence, calculate total recipient events (steps times list size), not just message count, and compare that number against the external and unique-recipient caps, not the daily message cap.

3. Limits by sending method: web, SMTP, API, and IMAP

How you submit a message changes what caps apply and how forgiving the system is about bursts. The four common paths, web interface, SMTP relay, Gmail API, and IMAP-based third-party apps, each carry their own ceilings and throttling behavior.

  • Web UI (Gmail inbox): Caps out at the standard per-message recipient limit (500 for free accounts, 2,000 for Workspace, with a 500-external sublimit), and is the slowest path for bulk sending since it is built for human composition, not automation.
  • SMTP (smtp.gmail.com): Enforces the same daily totals but adds connection-level throttling. Sending too many messages too quickly over a single SMTP connection often triggers temporary throttling before the daily cap is even reached.
  • Gmail API: Offers more granular control and better error handling for automated systems, but still respects the same underlying daily and recipient caps documented by Google Workspace. The API is generally the better choice for custom-built outreach tools because it returns structured error codes instead of generic SMTP bounces.
  • IMAP and third-party desktop or mobile apps (GWSMO and similar connectors): Typically route through SMTP under the hood, so they inherit SMTP’s throttling behavior, plus whatever additional rate limits the third-party app itself imposes.

For high-throughput systems, the practical choice is between authenticated user submission (sending as yourself through SMTP or the API) and a dedicated SMTP relay or connector designed for transactional or marketing volume. Authenticated user submission is fine for a single rep running a few hundred emails a day. Once a team needs thousands of messages a day across multiple senders, a relay built for that purpose avoids tripping per-account limits entirely, since it is not constrained by a single Gmail or Workspace user’s quota.

4. What happens when you exceed Gmail’s sending limits

Hitting a limit does not mean your account is disabled. It means outbound sending pauses until the rolling window clears, while inbound mail and most other account functions keep working normally.

Typical signs you have hit a cap:

  • A direct message in the Gmail interface stating you have reached a sending limit, often paired with a prompt to wait before trying again, as described in Gmail’s own limits documentation.
  • An SMTP error such as 4.7.28, which Google’s sender guidance associates with quota or rate-limit issues rather than a permanent rejection, meaning a short pause and a retry on a single connection is the recommended response.
  • Bounce-back messages (NDRs) for the specific recipients that pushed you over a counter, even while earlier recipients in the same batch received their mail successfully.

A block is almost always temporary and tied to the 24-hour rolling window, not a permanent suspension, according to Google’s limits guidance, though repeated violations can draw closer scrutiny from spam filtering systems over time.

Most limit violations are per-user, not tenant-wide: one rep hitting their external-recipient cap does not stop colleagues on the same Workspace domain from sending. The exception is when a pattern of abuse affects the whole domain’s reputation, since Gmail’s spam filtering increasingly weighs sender reputation at the domain level, not just the individual account. That is the real cost of repeatedly brushing against limits: even after the block clears, aggressive sending patterns can quietly erode how spam filters treat future messages from that domain.

Individual sending limits affecting domain reputation

5. Best practices to avoid hitting limits and scale safely

Staying under Gmail’s caps is less about watching a single number and more about building sending habits that keep you well inside every counter at once. The following steps, drawn from Gmail’s sender guidelines and Postmaster guidance, cover both technical setup and day-to-day sending discipline.

  1. Authenticate your domain properly. Set up SPF, DKIM, and DMARC records, and confirm forward and reverse DNS match. These are baseline requirements Google checks for any sender, and missing one is a common reason legitimate mail lands in spam long before volume becomes the issue.
  2. Enable TLS on your sending infrastructure. Unencrypted connections are treated as a reputation signal, and Google’s guidelines list TLS as an expectation for senders who want reliable delivery.
  3. Ramp up volume gradually on a new domain or IP. Jumping from zero to thousands of daily sends overnight reads as suspicious to spam filters. Google recommends a slow, staged increase rather than an immediate jump to full volume.
  4. Monitor Google Postmaster Tools. This gives visibility into spam rate, domain reputation, and delivery errors before they turn into blocks, and it is the primary tool Google points senders toward for diagnosing reputation problems.
  5. Segment by engagement, not just by list. Sending repeatedly to addresses that never open or reply inflates your unique-recipient count without improving results, and it raises your complaint rate over time.
  6. Include a List-Unsubscribe header and honor it immediately. This is a requirement for high-volume senders and a best practice for everyone else. RFC 8058 defines the one-click unsubscribe mechanics that Gmail expects compliant senders to support.
  7. Track bounce and complaint rates actively. A rising bounce rate often signals a stale list, and complaints directly affect the spam-rate thresholds that determine whether your mail reaches the inbox at all.
  8. Use a separate sending domain or dedicated IP for high-volume campaigns. Keeping transactional and marketing mail separate from day-to-day business correspondence protects your core domain’s reputation if a campaign underperforms.

Pro Tip: Tighter, more relevant sequences beat longer ones. Fewer messages to more qualified recipients consume less of every counter and tend to produce better reply rates than wide, repeated blasts.

For reps building sequences by hand, better message quality is often the fastest way to stay under these caps entirely. We cover a set of practical starting points in our 12 cold email templates, built to cut unnecessary follow-up steps by making the first message land. And when volume problems turn out to be deliverability problems in disguise, our breakdown of what actually predicts the spam folder walks through the signals that matter most.

Once a team outgrows what a handful of Workspace accounts can safely handle, a platform built specifically for high-volume sending is worth comparing against trying to stretch Gmail further. Guides comparing dedicated email marketing platforms are a reasonable starting point for that evaluation.

6. Requirements for high-volume senders and Postmaster guidance

Once you send 5,000 or more messages a day to Gmail addresses, Google holds you to a stricter set of rules, documented in its email sender guidelines. These are not optional best practices at that volume. They are requirements for continued delivery.

  • SPF and DKIM are both required, not just recommended, and DMARC must be configured with at least a monitoring policy in place.
  • Forward and reverse DNS must resolve correctly for the sending IP, confirming the sending server matches its claimed identity.
  • TLS connections are required for message transmission wherever supported.
  • Spam rates must stay below strict thresholds. Google’s guidance sets 0.1% as the preferred ceiling and 0.3% as the hard limit, past which a sender becomes ineligible for Postmaster mitigation and more likely to see mail routed to spam or rejected outright.
  • One-click unsubscribe must be supported via List-Unsubscribe headers, consistent with the mechanics defined in RFC 8058.

A spam rate above 0.3% removes eligibility for Postmaster-based mitigation, while the preferred operating range sits at or below 0.1%, according to Google’s sender guidelines FAQ, which makes complaint tracking a daily concern for any team sending at scale rather than a monthly check-in.

Google’s counting for these thresholds generally applies at the primary domain level, meaning a bulk sender using several subdomains or related properties can still be evaluated as a single reputation unit if those domains route through shared infrastructure. For organizations weighing whether to handle this volume internally or hand it to a specialist, managed email and lifecycle campaign services are built around exactly this kind of compliance and monitoring work.

7. Troubleshooting checklist and admin actions for Workspace admins

When sending stops working, the fastest path back to normal is identifying which counter was hit before attempting any fix. Guessing wastes the hours that a rolling window takes to clear.

  1. Check the Admin console’s email log search and message traces to see whether the block hit the message cap, the total recipient cap, or the external/unique recipient cap specifically.
  2. Pause all outbound sends from the affected account immediately rather than retrying, since repeated retries during an active block can extend scrutiny on the account.
  3. Reduce the next campaign’s recipient count well below the documented caps before resuming, giving the account headroom rather than sending right up to the limit again.
  4. Collect evidence before contacting Google support, including timestamps of blocked sends, the exact error text or bounce code received, and an estimate of recipient volume for the affected window.
  5. Escalate to Google Workspace support if the block persists well past 24 hours or recurs across multiple rolling windows without an obvious volume cause, since that pattern can indicate a reputation issue rather than a simple quota hit.
  6. Review domain authentication and recent sending patterns as a longer-term fix. A block is sometimes the symptom of a deeper reputation problem that authentication gaps or inconsistent sending volume created weeks earlier.

Admins should also confirm there is no quick workaround for a one-time volume spike. Google is explicit that there is no purchase option for a higher per-user quota: the sanctioned paths are reducing volume, waiting for the rolling window to clear, or routing the campaign through a dedicated bulk email provider built for that scale.

8. Planning B2B outreach sequences within Gmail’s limits

Most of the sales teams we talk with discover Gmail’s recipient caps the hard way, mid-campaign, when a sequence that looked modest on paper suddenly stalls. The fix is not sending less outreach. It is counting correctly before you launch.

A sequence with four touches to 800 prospects is 3,200 recipient events, not 800, and that number needs to be checked against the external-recipient cap before the first email goes out, not after the third one bounces. We recommend mapping every step of a sequence against total and external recipient limits during planning, not as a reaction to an error message.

Four-touch sequence producing 3,200 recipient events

Non-native English-speaking reps sending internationally face an added wrinkle: shorter, clearer sequences reduce both translation risk and recipient-count pressure at the same time, since fewer, sharper messages replace the padding that comes from over-explaining in a second language. That is part of why we built resources around B2B sales vocabulary, precision in wording reduces both friction and follow-up volume.

Ask yourself whether your fifth follow-up is earning its place in the sequence or simply consuming recipient quota that a more targeted list could use better.

— Samuel

Templates and deliverability guides that cut sending volume

The most reliable way to stay under Gmail’s limits is not clever quota management. It is sending fewer, better messages that need fewer follow-ups to get a reply. That is the practical core of what we publish at Sales Pitch: templates, scripts, and deliverability research built for reps who are actually running outreach, not just reading about it.

Usesalespitch

A few starting points if sending limits have you rethinking your sequence structure:

Browse the full library at Usesalespitch and pull the templates that fit your next sequence.

FAQ

How can I send more than 500 emails a day on Gmail?

A standard free Gmail account cannot exceed roughly 500 messages a day. Moving to a paid Google Workspace account raises the daily cap to about 2,000 messages, and sending volume beyond that requires following Postmaster guidelines or using a dedicated bulk email provider rather than attempting to push a single account past its quota.

How do I send a file over 25MB on Gmail?

Gmail automatically converts attachments larger than the standard Gmail size limit into a Google Drive link rather than rejecting the message outright. The recipient opens the link to download the file, and no manual setup is required since Gmail handles the conversion during send.

Why are only 10 emails sent per day in my Gmail?

A cap far below the standard 500-message limit usually points to a new or recently flagged account, a prior policy violation, or a security hold rather than a standard quota. Checking the Gmail account status and any security notifications in the account is the right first step, since this behavior falls outside Google’s documented standard limits.

Can I send 200 emails daily with Gmail?

Yes, 200 messages a day sits comfortably within both the free Gmail limit of about 500 and the Google Workspace limit of about 2,000, according to Google’s official limits table. At that volume, recipient-count caps are rarely the limiting factor unless each message goes to an unusually large recipient list.

What happens if I exceed Gmail’s sending limits?

Gmail temporarily pauses outbound sending for the affected account, usually clearing automatically once the rolling 24-hour window resets. Inbound mail and other account functions continue working normally during this time, and the block is per-user rather than affecting an entire Workspace domain in most cases.

Sources

More from the blog