Gmail vs Outlook Sending Limits for Cold Email: Official Caps vs Safe Volumes

Google Workspace permits up to 2,000 messages per day per mailbox; Microsoft 365 caps external recipients at 2,000 per day with a 30-messages-per-minute throttle. Neither number is a cold email budget. Send anywhere near the official caps with cold outreach and you'll burn the mailbox — the safe cold volume on both providers is 50–100 emails per day per warmed mailbox.

The most expensive misreading in cold email is treating provider limits as permission. The caps exist for legitimate transactional and internal mail; deliverability systems judge cold outreach by entirely different math.

The official numbers

• Google Workspace: the official sending limits are 2,000 messages per rolling 24 hours per account (500 on trial accounts, 1,500 for mail merge), with up to 10,000 recipient-counts per day.
• Microsoft 365 / Exchange Online: Microsoft's limits documentation sets a 10,000-recipient daily rate limit and 30 messages per minute — and Microsoft's External Recipient Rate Limit caps external recipients specifically at 2,000 per day. Cold email is, by definition, all external.

Why the safe number is 20–40x lower

Provider caps are enforcement ceilings, not reputation guidance. Mailbox providers score cold mail on engagement: a mailbox sending 1,500 cold emails a day generates bounce and complaint volume that trips spam classification long before it trips the official cap. Sales.co platform data across 5,000+ campaigns (2025–2026) consistently shows per-mailbox cold volume above ~100/day correlating with inbox-placement decay, while 50–100/day on warmed mailboxes holds placement steady. The ramp to get there safely is a 2–4 week warm-up — covered in depth at our sibling site howtowarmupemail.com.

Volume comes from architecture, not throttle settings

If your pipeline needs 1,000 sends a day, the answer is not one mailbox at 1,000 — it's 10–15 mailboxes across 4–5 domains at 50–100 each. That keeps every individual sender under the engagement radar, isolates damage when a domain degrades, and never approaches either provider's enforcement ceiling. The domain math lives at howmanydomainsforcoldmail.com, and the consequences of ignoring it are catalogued in what happens when you send too many.

Managing that architecture by hand — provisioning domains, authenticating them, warming each mailbox, and load-balancing sends — is exactly the infrastructure problem platforms like Sales.co automate: multi-domain, multi-mailbox sending with per-mailbox volume ceilings enforced by default.