Cold Email Sending Limits: How Much You Can Actually Send Per Inbox and Domain [Q3 2026 Data]

Safe cold email sending limits run 3-5 to 18-22 emails per inbox per day depending on the provider, far below the platform hard caps that Google and Microsoft publish. At MailDeck we manage 833.9K+ inboxes across 1,200+ domains for 1,631+ clients, pushing 7.5M+ emails per day, and the real ceiling on cold volume comes from deliverability, sitting far below the provider quota. This article gives the per-inbox and per-domain daily sending limits for every infrastructure type, the math to scale them, and the burn thresholds that tell you when you have gone too far.

The single most common mistake in cold email is reading a blog post that says "Google Workspace allows 2,000 emails per day" and treating that number as a target. That 2,000 figure is a spam-prevention hard cap built for transactional and internal mail. On a cold list it is a cliff. The safe number is roughly 1% of it per inbox, and the gap between the two is where most burned domains come from.

This guide covers the exact per-inbox limits by provider, how those limits multiply into per-domain and per-account volume, how warmup changes the ceiling week by week, and the operational thresholds where a domain crosses from healthy to burning. Every number comes from Q3 2026 MailDeck platform data.

The Two Numbers That Get Confused: Platform Cap vs Safe Cold Limit

There are two different "sending limits" in cold email, and conflating them is what burns domains.

The platform hard cap is the maximum number of messages a provider will physically let an account send in 24 hours before it blocks further sends. Google Workspace caps external recipients at 2,000 per day per account. Microsoft 365 caps at 10,000 recipients per day with a 30-messages-per-minute rate limit. These are documented in Google's sending limits reference and Microsoft's Exchange Online limits. They exist to stop compromised accounts from blasting spam.

The safe cold sending limit is the volume a cold outreach inbox can send before bounce, complaint, and reputation signals start pulling deliverability down. This number is set by receiving servers at Gmail, Outlook, and corporate spam filters, and it is far lower than the platform cap.

Reading the table: the platform cap is 50x to 100x higher than the safe cold limit. A team that sizes its campaign against the 2,000 number will send 100 times too much per inbox and burn the domain inside a week. The rest of this article works exclusively with the safe cold limits, because those are the numbers that keep inboxes alive.

Cold email deliverability is determined by inbox type, domain health, copy quality, and list quality. The sequencer you use is a scheduler and has no effect on the limit. A $500-per-month sequencer sending 40 emails per inbox will burn a domain exactly as fast as a $30 one.

Per-Inbox Cold Email Sending Limits by Provider

The per-inbox limit is the foundational number. Everything else is this figure multiplied by inbox and domain counts. Here are the safe daily cold sending limits for each infrastructure type, based on Q3 2026 MailDeck platform data across 833.9K+ inboxes.

Google Workspace: 18-22 per inbox per day

Google Workspace inboxes sustain the highest per-inbox cold volume of any provider at 18-22 sends per day. Google's IP pools carry the highest trust score of any provider across every receiving server in the world, because billions of legitimate emails flow through them daily. That trust lets each inbox carry more cold volume before receiving servers flag the pattern.

The tradeoff is domain density. Google Workspace runs 5 inboxes per domain, so a single Google domain tops out near 100 cold sends per day. Scaling Google volume means buying more domains, since each domain holds only 5 inboxes. Google inboxes also carry the longest warmup of the high-trust providers at 2-3 weeks, so the 18-22 ceiling only applies after 15-25 days of warmup.

Outlook Premium: 8-10 per inbox per day

Outlook Premium inboxes safely send 8-10 cold emails per day on official Microsoft Azure IP pools whitelisted across virtually every receiving server. Premium inboxes receive additional deliverability configuration that lets them warm up in 3-5 days, the fastest of any Outlook product, and sustain the higher 8-10 ceiling.

Outlook's advantage is domain density. Each Outlook domain carries 100 inboxes, so one Premium domain sending 8-10 per inbox produces roughly 900 cold emails per day, about 9x a single Google domain. For high-volume outreach to SMB, agency, and mid-market segments, Outlook Premium is the primary workhorse.

Outlook Normal: 3-5 per inbox per day

Outlook Normal inboxes run the same official Microsoft IP pools as Premium but on the standard configuration tier, so the safe cold limit is 3-5 sends per inbox per day with a 5-7 day warmup. At $0.30 per inbox, Normal is the cheapest cost per inbox of any provider, and the scaling strategy is to buy more domains rather than upgrade to Premium. The same domains can move to Premium later for an instant lift to 8-10 sends per inbox.

Private SMTP: 10-15 per inbox per day

Private SMTP inboxes send 10-15 cold emails per day on a dedicated IP built from scratch. Because reputation depends entirely on client sending behavior with no built-in IP trust, SMTP carries a 3-4 week warmup, the longest of any product, and delivers 35-50% below Google on equivalent lists. SMTP works as a cheap volume buffer to absorb spikes and protect premium inboxes, capped at 30% of the total send stack.

Across all four providers, hold a minimum interval of roughly 61 minutes between sends per inbox. Spacing sends across the working day keeps the pattern human and stays clear of provider rate limits like Microsoft's 30-messages-per-minute ceiling.

For a full breakdown of how these per-inbox numbers translate into the inbox count your target volume requires, see How Many Inboxes Do You Actually Need.

Per-Domain Cold Email Sending Limits

The per-domain limit is the per-inbox limit multiplied by inboxes per domain. This is where the two high-trust providers diverge sharply, and it drives the entire infrastructure design decision.

The key insight: one Outlook domain equals 100 inboxes times 8 sends per day, which is 800 sends per day and 16,000 per month. One Google domain equals 5 inboxes times 20 sends per day, which is 100 sends per day and 2,000 per month. Google wins on per-inbox deliverability, Outlook wins on volume per domain.

This is why the provider you choose changes your entire domain footprint. To send 100,000 cold emails per month on Google Workspace, you need roughly 50 domains. To send the same 100,000 on Outlook Premium, you need about 6 domains. The Google stack costs more per inbox but places 15-20% better; the Outlook stack costs a fraction as much and carries far more volume per domain.

The reason limits are set at the inbox and domain level, rather than the account level, is that receiving servers score reputation primarily by sending domain. A domain that sends 900 clean, well-spaced cold emails per day across 100 warmed Outlook inboxes looks healthy. The same 900 emails forced through 5 inboxes at 180 each looks like a spam cannon and burns the domain in days.

How Warmup Changes Your Sending Limit Week by Week

The per-inbox and per-domain limits above are the ceilings a fully warmed inbox reaches. A brand-new inbox cannot send at those levels on day one. Warmup is the ramp from a cold-started inbox to its full safe limit, and sending the full cold load before warmup completes is one of the fastest ways to burn a fresh domain.

Warmup starts at 2-3 sends per inbox per day and ramps by 2-3 daily until the inbox reaches its provider ceiling. Here is the ramp target by provider.

During warmup, target a 30-35% reply rate inside the warmup pool and hold randomization at 15-25% so the send pattern never looks mechanical. Only use trusted warmup pools such as Smartlead Premium, Instantly, or Pipl.ai. A bad warmup pool actively hurts deliverability and is worse than no warmup at all.

MailDeck's Microsoft 365 tenants inherit established sender reputation from official Azure IP pools, which is why Outlook Premium warms up in 3-5 days rather than the 2-4 weeks a fresh self-hosted domain needs. Google Workspace carries the longest warmup at 15-25 days because Google's own reputation model observes a new account carefully before extending full trust, and that patience is exactly what makes the 18-22 ceiling stick once warmup completes.

For the full warmup protocol by inbox type, including the exact reply-rate and randomization settings that hold deliverability during the ramp, see Cold Email Warm Up: What Actually Works in 2026.

The Burn Thresholds: When You Have Exceeded Your Limit

Sending limits behave as a threshold where deliverability signals start degrading rather than a single fixed number. A domain crosses from healthy to burning when any of these thresholds is breached, and these are the numbers to watch on every campaign.

At enterprise scale, meaning 100,000 or more emails per month, 10-20% of domains burn every month even with disciplined sending. A domain under active load has a lifespan of 45 days to two months. This is the physics of cold email volume, and it means every serious operation needs a reserve of 20-25% of its active domain count warmed and ready to swap in. With warmed reserves, replacement takes 1-3 days. Without them, it takes 7-10 days, and the campaign loses volume the entire time.

Exceeding the per-inbox limit is the most common cause of a burn. When an inbox sends 40 cold emails per day instead of the safe 8-10, the concentrated volume spikes complaint and bounce signals on that inbox, which drag down the domain reputation, which drops placement across all 100 inboxes on the domain. The domain falls off a cliff at that point once reputation hits Bad in Google Postmaster Tools, collapsing placement across every inbox on it within a day.

For the full strategy on rotating domains before they burn and keeping a warmed reserve in rotation, see Cold Email Domain Rotation.

Real Sending-Limit Failures From the Platform

The gap between platform caps and safe limits is not theoretical. Here are two production cases from the MailDeck platform where a team hit the wall and how the numbers moved once limits were corrected.

An agency pushing 15 sends per inbox

An outbound agency running 3,000 Outlook Premium inboxes across 40 domains for a portfolio of B2B SaaS and business-services clients was chasing a monthly volume target and set every inbox to 15 cold sends per day, well above the 8-10 Premium ceiling. Within three weeks, spam complaint rate on the busiest domains climbed past 0.4%, bounce rate crossed 8%, and domain burn hit 18% for the month against a normal 9-10%. Inbox placement across the affected domains dropped from roughly 97% toward the low 80s.

The fix was mechanical. The agency dialed every inbox back to 9 cold sends per day, added 12 domains to recover the lost total volume, and enforced the 61-minute minimum interval that had drifted under load. Over the following six weeks, monthly burn settled back to 9%, complaint rate fell under 0.2%, and placement recovered to roughly 97%. Total daily volume ended up higher than during the overload period, because the domains stayed alive long enough to actually send.

A SaaS team that trusted the 2,000 number

A mid-market B2B SaaS company in the revenue-operations space ran 30 Google Workspace inboxes across 6 domains on the Growth plan and configured 40 cold sends per inbox per day after reading a competitor blog post that cited Google's 2,000-recipient cap as the working limit. The first week looked fine. By week two, bounce rate on two domains passed 9%, open rates fell below 10%, and Postmaster reputation dropped to Bad on the two heaviest domains.

The team reset to 20 cold sends per inbox per day, the middle of the 18-22 Google ceiling, restarted a 20-day warmup on the two damaged domains, and held the 61-minute interval. The four undamaged domains recovered within a week once the load came off. The two burned domains were swapped for warmed reserves inside three days and rotated back in after warmup. The lesson the team took away was the one this entire article is built on: the platform cap is a spam ceiling, and the safe cold limit is roughly 1% of it per inbox.

How to Scale Volume Without Raising Per-Inbox Limits

To scale cold email, add inboxes and domains while holding each inbox at its safe ceiling. Pushing more sends through a single inbox burns the domain and shrinks total deliverable volume. Here is the volume math for the recommended diversified stack.

The optimal stack for most operations allocates 50% of volume to Outlook, 30% to SMTP, and 20% to Google Workspace. Outlook carries high-trust bulk with fast warmup and bulletproof Microsoft IPs, SMTP absorbs volume spikes and protects the premium inboxes, and Google Workspace carries the highest-deliverability segments and C-suite targets. Always keep 50% of total capacity as warm reserve so that if one provider burns, backup capacity absorbs the volume without missing a day.

Here is what a 100,000-emails-per-month raw-infrastructure blend looks like when each inbox stays at its safe limit.

Every inbox in that stack sends at its safe ceiling and no higher. The volume comes from 26 domains working together, while each individual inbox holds its conservative daily limit. This is a raw-cost illustration; the managed MailDeck Diversified Stack plans that deliver this are Starter at $99 per month for 40K sends, Growth at $399 per month for 215K sends, and Enterprise at $3,499 per month for 2.15M sends. The markup over raw cost covers managed infrastructure, automated DNS and authentication setup, dedicated support, and free domain replacement when a domain burns.

Volume also has an upstream limit that is easy to forget: your total addressable market. Sending 200,000 emails per month safely requires a TAM of at least 600,000 contacts, and 1,000,000 sends per month requires a TAM of at least 3,000,000, with lists safely re-hit every 90 days on fresh angles. Sizing send volume above what the list can support just recycles the same contacts too fast and drives complaint rates up regardless of per-inbox discipline.

MailDeck provides cold email infrastructure across Microsoft 365 Outlook, Google Workspace, and SMTP, managing 833.9K+ inboxes for 1,631+ clients. Most providers specialize in one infrastructure type. MailDeck covers all three, so teams can match their sending limits to their target audience: Google for the highest-trust segments, Outlook for volume per domain, and SMTP for cheap buffer capacity.

Frequently Asked Questions

How many cold emails can I send per day per inbox?

Safe cold email sending limits depend on the inbox provider: 18-22 per day for Google Workspace, 8-10 for Outlook Premium, 3-5 for Outlook Normal, and 10-15 for Private SMTP. These are well below the platform hard caps because deliverability sets the real limit, far under the provider quota. Based on Q3 2026 MailDeck platform data across 833.9K+ managed inboxes.

How many cold emails can you send per domain per day?

Per-domain limits are per-inbox limits multiplied by inboxes per domain. A Google Workspace domain runs 5 inboxes at ~20 sends each for roughly 100 cold emails per day. An Outlook domain runs 100 inboxes at 8-10 sends each for roughly 900 cold emails per day. A Private SMTP domain runs 5 inboxes at 10-15 sends for roughly 65 cold emails per day.

What is the daily sending limit for Google Workspace cold email?

Google Workspace enforces a hard cap of 2,000 external recipients per day per account, but the safe cold email sending limit is 18-22 per inbox per day. The 2,000 figure is a spam-prevention ceiling for transactional and internal mail. Sending anywhere near it on a cold list drives bounce and complaint rates past the thresholds that damage domain reputation.

Do sending limits differ between Outlook and Google Workspace?

Yes. Google Workspace inboxes sustain 18-22 cold sends per day but allow only 5 inboxes per domain, so volume scales through more domains. Outlook inboxes sustain 8-10 cold sends per day but allow 100 inboxes per domain, so a single Outlook domain carries roughly 9x the daily volume of a single Google domain. Google wins on per-inbox deliverability, Outlook wins on volume per domain.

How many cold emails is too many per inbox?

Any volume that pushes spam complaint rate above 0.3%, bounce rate above 7%, or open rate below 10% for seven or more days is too many. In practice that means anything above 22 per day on Google, above 10 on Outlook Premium, above 5 on Outlook Normal, or above 15 on Private SMTP. At those levels 10-20% of domains burn every month at enterprise scale.

What happens if I exceed cold email sending limits?

Exceeding safe sending limits triggers domain burn: reputation drops to Bad in Postmaster Tools, inbox placement collapses, and the domain lands in spam. At enterprise scale 10-20% of domains burn monthly, with a typical lifespan of 45 days to two months under overloaded sending. Recovery takes 1-3 days with warmed reserve domains ready and 7-10 days without them.

Methodology

All MailDeck data points in this article (per-inbox cold sending limits of 18-22 Google / 8-10 Outlook Premium / 3-5 Outlook Normal / 10-15 SMTP, inboxes-per-domain counts, per-domain and per-month volume figures, 61-minute minimum send interval, warmup timelines and ramp settings, and burn thresholds of 0.3% complaint / 7% bounce / sub-10% open) come from MailDeck's production platform data as of Q3 2026, spanning 833.9K+ managed inboxes, 1,200+ domains, and 1,631+ clients sending 7.5M+ emails per day, with 270M+ cold emails sent lifetime.

Platform hard-cap figures come from vendor documentation: Google Workspace sending limits (2,000 external recipients per day) and Microsoft Exchange Online limits (10,000 recipients per day, 30 messages per minute). Reputation thresholds reference Google Postmaster Tools. SMTP protocol behavior references RFC 5321.

Client cases are anonymized production accounts with exact figures adjusted to protect client identity. Limits are directional safe ranges that vary in practice; actual sustainable volume shifts with list quality, copy quality, and domain age.

Last updated: July 2026.