Email Sending Limits by Provider (and How to Scale)
Email sending limits are caps that mailbox and infrastructure providers place on how many messages you can send per minute, per hour, or per day. Personal inboxes typically allow a few hundred a day, business suites a few thousand, and dedicated sending platforms scale far beyond that. The limit you hit first tells you which tier you have outgrown.
Why sending limits exist at all
Every limit you run into is a spam-control mechanism wearing a different hat. A compromised Gmail account that could blast 400,000 messages before anyone noticed would be worth a fortune to a spammer. A daily cap turns that jackpot into a nuisance. The same logic drives limits at your web host, your CRM, and your transactional API.
There is a second reason that matters more once you are sending legitimately at volume: reputation isolation. Providers throttle new or unproven senders because volume from an unknown source is statistically more likely to be abusive. Limits are the training wheels. You earn your way off them by sending mail people want.
The practical consequence is that "how many emails can I send" is never one number. It is at least four numbers stacked on top of each other, and campaigns die when people plan around only one of them.
Sending limits by provider category
The table below groups providers by what they are actually built for. Treat the figures as the published order of magnitude, not gospel — every provider revises these, and paid tiers, account age, and verification status all shift them. Always confirm against your provider's current documentation before you plan a send.
| Provider category | Typical daily ceiling | Built for | What breaks first |
|---|---|---|---|
| Free consumer mailbox (Gmail, Outlook.com, Yahoo) | Low hundreds of recipients | Person-to-person mail | Daily recipient cap; account suspension |
| Business mailbox suite (Google Workspace, Microsoft 365) | Low thousands of recipients | Internal and client correspondence | Per-minute throttle and recipients-per-message cap |
| Shared web host SMTP | A few hundred per hour, often less | Contact form notifications | Hourly cap; shared IP reputation |
| Transactional API or SMTP relay | Tiered; scales with verified reputation | Receipts, resets, alerts, app mail | Per-second rate limit during bursts |
| Email marketing platform | Plan-based; effectively unmetered contacts on paid tiers | Campaigns and automations to opted-in lists | Complaint rate, not volume |
Notice the last column. Once you move past mailbox suites, volume stops being the binding constraint and recipient behavior takes over. That shift is the whole story of scaling email.
The four limits that actually stop you
When someone says "we hit our sending limit," they usually mean one of these four, and the fix is different for each:
- Recipients per message. How many addresses can appear in To, CC, and BCC combined. This is why a 900-person BCC blast fails on a business account that nominally allows thousands of recipients per day.
- Messages per day. A rolling 24-hour window, not a calendar day. Blow through it at 4pm and you are not reset at midnight.
- Messages per minute or per second. The throttle. Automated systems trip this constantly because they loop as fast as the code allows.
- Connections per host. How many simultaneous SMTP connections you may open. Exceeding it produces temporary failures that look like outages but are just backpressure.
A well-built sending system respects all four. A script someone wrote in an afternoon respects none of them, which is why homegrown senders so often produce a wall of deferrals. If you are seeing repeated 4xx responses rather than hard rejections, you are being throttled, not blocked, and the answer is to slow down rather than to retry harder.
How to work out the volume you actually need
Most people overestimate. Take your list size, multiply by campaign frequency per month, add automated sequences, then add transactional mail, then add roughly 30% headroom for a launch or a seasonal spike. A 6,000-person list sending two campaigns a month plus a five-email welcome sequence and order confirmations is nowhere near a million messages — but it will absolutely bury a Workspace mailbox.
Then separate the two streams. Marketing campaigns and transactional mail should not share a sending path, because a promotional complaint spike should never delay someone's password reset. Splitting them early is the cheapest deliverability decision you will ever make, and it is the core argument for routing app mail through a dedicated SMTP relay for application email while campaigns go out through your marketing platform.
When a mailbox stops being the right tool
Some signals are unambiguous. If any of these are true, you have outgrown mailbox sending:
- You are BCC-ing more than about 20 people to avoid exposing addresses.
- You cannot tell who opened, clicked, or bounced.
- There is no unsubscribe link, because the mailbox does not add one and you keep forgetting.
- You are splitting a send across two days to stay under a cap.
- Someone replied "please take me off this list" and you handled it by hand.
Point three is the dangerous one. Mailbox sending gives you no compliance scaffolding at all — no suppression list, no consent record, no automatic unsubscribe handling. That is a legal and reputational exposure long before it is a technical one.
Scaling volume without tripping filters
Raising your ceiling is easy. Raising it safely means warming up, because receiving providers judge unfamiliar sending patterns harshly. A sudden jump from 200 messages a day to 40,000 from the same domain reads as a compromised account.
A workable ramp looks roughly like this, with each stage held until complaint and bounce rates stay clean:
| Stage | Daily volume | Who to send to | Advance when |
|---|---|---|---|
| Week 1 | A few hundred | Most recently engaged contacts only | Bounces stay low and opens are strong |
| Week 2 | Roughly double week 1 | Engaged in the last 90 days | No spam-folder reports from seed testing |
| Week 3-4 | Double again, per week | Engaged in the last 180 days | Complaint rate stays well under 0.1% |
| Week 5+ | Full list volume | Everyone still active | Metrics hold steady for two full sends |
Two rules make or break the ramp. Send to your most engaged people first, because their opens and replies are the positive signal that buys you room. And never mix a warmup with a list you just imported and have not cleaned — old addresses turn into hard bounces exactly when you can least afford them. If you want the full picture of what receiving providers are grading you on, our guide to improving email deliverability covers authentication, engagement, and infrastructure together.
Limits on the receiving side
Your provider's cap is only half the equation. Receiving domains impose their own per-sender rate limits, and large mailbox providers apply them dynamically based on your reputation. A sender with a clean history gets accepted quickly; an unknown one gets deferred and retried. This is why two companies sending identical volume can have wildly different throughput.
You influence this with the things you already know you should do: authenticate with SPF, DKIM, and DMARC so your mail is attributable, keep complaint rates low, honor unsubscribes instantly, and remove hard bounces after a single failure. IGSendMail sets up SPF, DKIM, and DMARC automatically at domain connection, which removes the most common cause of self-inflicted throttling.
A migration path that does not lose deliverability
Moving from a mailbox or an old platform to a real sending platform is straightforward if you sequence it. Connect and authenticate your sending domain first. Import and verify your list, dropping addresses that fail validation rather than "testing" them on a live send. Send your first real campaign to your most engaged segment only. Then widen out over two to three sends while watching bounce and complaint rates. IGSendMail includes free 24-hour migration, which handles the list, template, and authentication moves in one pass so you are not warming up a domain twice.
Frequently asked questions
How many emails can I send per day from Gmail?
A free Gmail account allows a low-hundreds daily recipient count, and Google Workspace raises that into the low thousands. Both are designed for correspondence, not campaigns, and neither provides unsubscribe handling, bounce processing, or reporting. Check Google's current documentation for exact figures, as they change.
What happens if I exceed my sending limit?
Most providers return a temporary failure and defer the remaining messages, so they queue rather than vanish. Repeated or aggressive overage can trigger a temporary sending suspension on your account. Consumer mailbox providers are the strictest and may lock sending for 24 hours.
Do sending limits count recipients or messages?
Usually recipients. One message addressed to 50 people typically counts as 50 against your quota, not one. This is the single most common reason people miscalculate their remaining capacity.
Does a dedicated IP raise my sending limit?
Not directly. A dedicated IP isolates your reputation from other senders, but it starts with no reputation at all, so your effective throughput is lower until you warm it. Dedicated IPs make sense at sustained high volume, not as a fix for hitting a mailbox cap.
Can I split a large send across several accounts to get around limits?
You can, and it is a bad idea. Splitting sends across mailboxes fragments your reputation, breaks unsubscribe suppression, and is treated as evasion by most providers' terms of service. Move to a platform built for the volume instead.
Ready to stop planning campaigns around a mailbox quota? Launch with IGSendMail — unlimited contacts on paid plans, 99% inbox deliverability, automatic SPF, DKIM, and DMARC, and free 24-hour migration from your current provider. Plans start at $19/mo, with a free plan for up to 2,500 contacts.