- Free Gmail allows about 500 emails per day; Google Workspace raises this to 2,000 messages per day (trial accounts only 500), with a separate 100-recipients-per-message cap when sending via SMTP.
- Free Outlook.com allows roughly 300 recipients per day; Microsoft 365 (Exchange Online) meters recipients rather than messages, capping external recipients around 10,000 per day and throttling to about 30 messages per minute.
- Yahoo Mail documents about 500 messages per day with a 100-recipients-per-message cap and an unofficial hourly throttle; Apple iCloud allows about 1,000 messages and 1,000 recipients per day.
- Most providers use a rolling 24-hour window, not a midnight reset, and exceeding a limit typically suspends sending for about 24 hours.
- The published number is never your real ceiling: providers throttle or block on bounce rate and complaints long before the volume cap, and mailboxes are designed for correspondence, not bulk sending.
If you have ever watched a mail merge stall at message 2,001 or an account suddenly start rejecting mail mid-campaign, you have hit a sending limit. Every major mailbox provider caps how much you can send, and the caps differ not just by provider but by account type and even by how you connect. Knowing the real 2026 numbers is the first step, but the more important lesson is that the published limit is almost never the ceiling that actually stops you. This guide covers both: the current limits for Gmail, Outlook, Yahoo, and more, and the reputation reality that matters more than any number.
Understanding these limits protects your Sender Reputation and keeps your mail flowing, because the fastest way to damage deliverability is to treat a personal or business mailbox as a bulk sending platform. Let us start with the numbers, then explain why they are only half the story.
The 2026 Sending Limits by Provider
Here are the current documented limits. Treat them as current-as-of-2026 reference points, since providers adjust them without much notice, and always verify against each vendor's own limits page before planning a campaign around a single figure.
| Provider / Account | Daily Limit | Per-Message Cap | Notes |
|---|---|---|---|
| Gmail (free) | ~500 emails/day | 100 via SMTP | Exceeding triggers ~24h block |
| Google Workspace (paid) | 2,000 messages/day | 2,000 (500 external) | Trial accounts only 500/day |
| Outlook.com (free) | ~300 recipients/day | Varies | Can rise with account history |
| Microsoft 365 | ~10,000 external recipients/day | up to 1,000/message | Meters recipients; ~30 msgs/min throttle |
| Yahoo Mail | ~500 messages/day | 100 recipients | Unofficial hourly throttle ~100 |
| Apple iCloud | ~1,000 messages/day | 500 recipients | 1,000 total recipients/day |
A few important nuances behind the table:
- Messages vs recipients. Google and Yahoo largely count messages (with a separate per-message recipient cap), while Microsoft 365 counts external recipients rather than messages. This matters: on Microsoft, BCC-blasting a large list drains your recipient quota fast, and you are blocked at whichever meter fills first.
- SMTP lowers per-message caps. When you send through SMTP (a third-party client or a script) on Gmail, the per-message recipient cap drops to 100, though your daily total is unchanged.
- Trial and new accounts are lower. A trial Google Workspace account sends only 500 per day, not 2,000, and new or unverified accounts across providers often start with reduced quotas that rise as they build credibility.
- Tenant-wide limits exist. Microsoft 365 added a tenant-wide external recipient allowance, so one mailbox or app can exhaust quota for the whole organization.
How the Limits Reset
A common misconception is that limits reset at midnight. Most providers use a rolling 24-hour window instead: your limit resets 24 hours after you sent your first email of the period, not at a calendar boundary. This is why sending a batch in the evening can leave you blocked the next morning even though the date changed. When you exceed a limit, the typical consequence is a temporary suspension of sending for about 24 hours, after which normal sending resumes, assuming nothing else is wrong.
The Published Limit Is Not Your Real Ceiling
Here is the point most guides miss, and the one that actually matters for deliverability. The provider's published volume cap is a technical ceiling, not a safe operating level. In practice, providers throttle, filter, or block you based on your sending quality long before you approach the numeric limit. Quality enforcement kicks in first.
If your bounce rate climbs or your spam complaints rise, providers will restrict you well under the volume cap, because a mailbox suddenly sending large volumes with poor engagement looks statistically like a compromised or abusive account. The daily number tells you when you will be hard-stopped; your reputation tells you when you will be quietly filtered, and the second happens first. This is why senders who technically stay under 2,000 a day still see their mail go to spam: they hit the reputation ceiling, not the volume ceiling.
The most important sentence in this article: hitting a provider's sending limit means you are already using a mailbox as a bulk sender, and that is the actual problem. Gmail, Outlook, and Microsoft 365 are designed for a person writing to other people. The limits exist specifically to stop them being used as bulk platforms, because an account that suddenly sends thousands of messages is, statistically, a compromised account. If you are bumping against these caps, the answer is not to find a workaround; it is to move to infrastructure built for volume.
How to Actually Send at Scale
If you need to send more than a mailbox comfortably allows, the correct path is not to trick the limits but to use the right infrastructure. Running bulk mail through a personal or business mailbox does not just risk suspension; it actively ties your domain's reputation to bulk sending from an IP pool designed for correspondence, which can push your ordinary business email into spam too.
- Use a dedicated email service provider or SMTP relay. Platforms built for volume (ESPs and transactional email services) are designed to send at scale with proper infrastructure, reputation management, and authentication. This is the right tool for newsletters, marketing, and high-volume transactional mail.
- Authenticate properly. Whatever you send through, implement and align SPF, DKIM, and DMARC. Bulk senders are also required to offer one-click unsubscribe under current Gmail and Yahoo requirements, which apply to anyone sending roughly 5,000 or more messages a day to personal inboxes. Verify your setup with a DMARC checker.
- Warm up new infrastructure. Do not move to a new sending platform or domain and immediately blast your full volume. Warm up gradually, starting with your most engaged recipients, so you build reputation instead of triggering filters.
- Protect your bounce and complaint rates. Since quality enforcement hits before volume caps, keep your list clean with verification and hygiene, and keep bounces under 2 percent and complaints under 0.3 percent. This is what actually lets you send more.
- Do not distribute across many mailboxes to dodge limits. Spreading a campaign across multiple accounts to evade caps is exactly the snowshoe pattern filters are built to catch, and it damages every domain involved.
If you are hitting Gmail or Microsoft 365 limits with legitimate mail, treat it as a signal to graduate to proper sending infrastructure, not as a puzzle to work around. The workarounds people reach for (rotating multiple accounts, BCC-stuffing, third-party scripts hammering SMTP) are precisely the behaviors that get accounts flagged and domains blocklisted, because they mimic what spammers do. Moving newsletters and bulk mail to a dedicated ESP costs less than a damaged domain reputation, and it separates your bulk sending from your day-to-day business mail so a problem with one never poisons the other.
The Bottom Line
The 2026 sending limits are worth knowing: roughly 500 a day on free Gmail, 2,000 on Workspace, recipient-metered caps around 10,000 on Microsoft 365, about 500 on Yahoo, and a rolling 24-hour reset across most providers. But the numbers are the least important part of the story. The published cap is a hard ceiling; your bounce rate, complaint rate, and reputation are the soft ceiling that stops you first, and hitting either usually means you are asking a correspondence mailbox to do a bulk sender's job. Send at scale the right way, on infrastructure built for it, with clean lists and proper authentication, fold it into your broader deliverability practice, and the limits stop being a wall you keep running into.
Frequently Asked Questions
A free Gmail account allows about 500 emails per day, and exceeding that typically triggers a roughly 24-hour sending block. A paid Google Workspace account raises the limit to 2,000 messages per day, though trial Workspace accounts are capped at 500. When you send through SMTP (a third-party client or script), the per-message recipient cap drops to 100, though your daily total is unchanged. Limits reset on a rolling 24-hour window, not at midnight.
Free Outlook.com allows roughly 300 recipients per day, which can rise with account history. Microsoft 365 (Exchange Online) meters external recipients rather than messages, capping them around 10,000 per day and throttling sending to about 30 messages per minute, with up to 1,000 recipients per message. Microsoft also enforces a tenant-wide external recipient allowance, so a single mailbox or app can exhaust the quota for the whole organization. Verify current figures on Microsoft's limits page before planning.
No. Most providers use a rolling 24-hour window rather than a calendar-day reset, so your quota frees up 24 hours after you sent your first email of the period, not when the date changes. This is why a batch sent in the evening can leave you blocked the next morning despite the new date. When you exceed a limit, sending is typically suspended for about 24 hours before it resumes, assuming your reputation is otherwise healthy.
Use infrastructure built for volume rather than trying to work around a mailbox's limits. A dedicated email service provider or SMTP relay is designed to send at scale with proper reputation management and authentication, which is the right tool for newsletters and high-volume mail. Authenticate with aligned SPF, DKIM, and DMARC, offer one-click unsubscribe, warm up new infrastructure gradually, and keep bounces and complaints low. Do not spread a campaign across multiple accounts to dodge caps, since that is the snowshoe pattern filters catch.
Because the published volume cap is a technical ceiling, not a safe operating level. Providers throttle, filter, or block based on sending quality long before you reach the numeric limit: if your bounce rate climbs or spam complaints rise, they restrict you well under the cap, since a mailbox suddenly sending high volume with poor engagement looks like a compromised account. Your reputation is the ceiling that stops you first, so keep bounces under 2 percent and complaints under 0.3 percent.