Cold Email Sending Limits 2026: Google Workspace and Outlook 365 Explained

By Puzzle Inbox Team · Jun 21, 2026 · 12 min read

Cold email sending limits explained: Google Workspace and Outlook 365 official caps vs safe per-inbox volume, plus exact math for scaling cold email in 2026.

Why Cold Email Sending Limits Are the Whole Game

If you run outbound, the single number that decides whether you hit quota is your daily send volume. Not your copy. Not your offer. The cold email sending limits you pick per inbox decide whether your domains stay healthy for six months or get burned in six days. Most operators get this wrong because they read the official Google Workspace and Microsoft 365 limits, do the math, and assume they can send that many cold emails per day. They cannot. The official limits are for transactional and internal mail. Cold email lives by a different set of numbers, and those numbers are what we enforce on every Puzzle Inbox account.

This guide walks through the official caps, the realistic per-inbox volume for cold outreach, and the exact inbox math you need to hit 200, 1,000, 5,000, or 10,000 cold emails per day in 2026. If you want to skip the theory and just provision, the prices are on /pricing and the workflow is on /how-it-works.

The Official Google Workspace and Microsoft 365 Limits

Google publishes a per-user sending cap of 2,000 messages per 24 hours for paid Workspace accounts (500 for trial accounts). External recipients are capped at 3,000 per day. Microsoft 365 publishes a recipient rate limit of 10,000 per 24 hours and a recipients-per-message cap of 500. Read those numbers literally and you would think a single Workspace inbox can send 2,000 cold emails per day. That is the trap.

Those limits are anti-abuse ceilings, not safe operating volumes. They exist to stop a compromised account from blasting 100,000 spams in an hour. They do not represent what an inbox can send without getting filtered, throttled, or suspended when the content is cold outreach to recipients who never asked for it. The official caps are the speed limit on the highway. The safe cold email sending limits are how fast you can actually drive in fog.

The Safe Cold Email Sending Limits We Enforce

Puzzle Inbox runs a hard cap on every inbox we provision. On Google Workspace, the maximum is 12 cold emails plus 12 warmup emails per inbox per day, for a total of 24 sends per inbox per day. On Outlook 365, the maximum is 3 cold emails plus 3 warmup emails per inbox per day, for a total of 6 sends per inbox per day. These are not suggestions. They are the ceilings we built the product around, and they match what we have seen keep deliverability above 90 percent across millions of cold sends.

Why so much lower than the official caps? Because cold email is judged by a different scoring system than the one Google and Microsoft advertise. The official limits are bandwidth. The real limits are reputation, and reputation is built and destroyed at the per-inbox level.

Why Google Per-Inbox Volume Can Be Higher Than Outlook

Google scores reputation per mailbox. Each inbox accumulates its own send history, complaint rate, bounce rate, and engagement signal. A Workspace mailbox that has been warming for three weeks and has clean engagement can push more cold sends per day without tripping filters, because the score is local to that mailbox. This is why our Google ceiling sits at 12 cold per inbox: the per-inbox reputation can carry that load when the warmup is healthy.

Microsoft does not work the same way. Outlook 365 tolerates a high number of mailboxes per tenant (100 in our setup, more on that below) but it punishes per-inbox complaint rates much harder. A single Outlook mailbox that gets two spam complaints in a week can see its delivery rate collapse, and the damage spreads to neighboring mailboxes on the same tenant faster than it does on Google. To keep per-inbox complaint rates microscopic, we cap Outlook 365 cold email volume at 3 cold sends per inbox per day. Lower per-inbox volume means lower per-inbox complaint probability, which means the tenant stays healthy.

The result is symmetric. Google gives you higher per-inbox volume across fewer inboxes per domain. Outlook gives you lower per-inbox volume across many more inboxes per domain. Total per-domain throughput ends up close. We explain the trade-off in more depth on /our-process.

Mandatory Inbox Count Per Domain

This part is not negotiable. Every Google Workspace domain we provision runs exactly 3 inboxes. Every Outlook 365 domain we provision runs exactly 100 inboxes. These numbers come from the reputation models above. Three Google inboxes per domain is the sweet spot where Google's per-domain reputation stays stable and you still get meaningful per-domain volume. One hundred Outlook inboxes per domain is what Microsoft tolerates without flagging the tenant as a bulk sender, given the low per-inbox volume.

You cannot buy 1 Google inbox or 5 Google inboxes on a domain. You cannot buy 50 Outlook inboxes on a domain. The unit of provisioning is the domain, and the domain comes pre-configured with the correct inbox count. Details on the provisioning model live on /buy-google-workspace-cold-email-inboxes and /buy-outlook-365-cold-email-inboxes.

The Per-Domain Math

Once you fix the inbox count per domain and the per-inbox volume, the per-domain numbers fall out:

  • Google Workspace domain: 3 inboxes x 12 cold = 36 cold emails per domain per day, plus 3 x 12 = 36 warmup emails per domain per day.
  • Outlook 365 domain: 100 inboxes x 3 cold = 300 cold emails per domain per day, plus 100 x 3 = 300 warmup emails per domain per day.

Outlook gives you roughly 8x the per-domain cold throughput of Google. That sounds like Outlook wins until you remember Outlook 365 inboxes cost more per seat and the per-inbox reputation is more fragile. Most operators run a blend. The blend math is on /features.

How to Size Your Inbox Count for Daily Targets

Here is the operator math you actually need. Decide your daily cold send target, then work backward to inbox count.

Target: 200 cold emails per day

On Google: 200 / 12 = 17 inboxes, rounded up. That is 6 domains (18 inboxes). On Outlook: 200 / 3 = 67 inboxes, which fits inside a single Outlook domain (100 inboxes). For 200 per day, one Outlook domain is the cleanest answer if your audience is fine with Outlook sending reputation. If your audience is technical and you want Workspace, six Google domains is the equivalent.

Target: 1,000 cold emails per day

On Google: 1,000 / 12 = 84 inboxes, rounded up, which is 28 Google domains (84 inboxes). On Outlook: 1,000 / 3 = 334 inboxes, which is 4 Outlook domains (400 inboxes). At 1,000 per day, Outlook gets dramatically cheaper on a per-send basis. A common blend is 2 Outlook domains plus 10 Google domains for redundancy.

Target: 5,000 cold emails per day

On Google: 5,000 / 12 = 417 inboxes, which is 139 Google domains. On Outlook: 5,000 / 3 = 1,667 inboxes, which is 17 Outlook domains. At this volume, almost no one runs pure Google. The standard mix is 15 to 20 Outlook domains carrying the bulk, plus 20 to 40 Google domains for sender diversity. We walk through a 5k/day buildout on /blog/how-many-cold-email-inboxes.

Target: 10,000 cold emails per day

On Google: 10,000 / 12 = 834 inboxes, which is 278 Google domains. On Outlook: 10,000 / 3 = 3,334 inboxes, which is 34 Outlook domains. At 10k/day, Outlook is the only economically realistic primary, with Google as a 10 to 20 percent diversity layer. Expect to run 35 to 40 Outlook domains plus 30 to 60 Google domains. Setup and warmup at this scale takes 4 to 6 weeks.

The numbers above assume every inbox is fully ramped and warmed. A brand new inbox cannot send 12 cold per day on day one. If you provision 100 inboxes today expecting 1,200 cold sends tomorrow, you will burn the domains. Use the ramping schedule in the next section, or scale your daily target across the warmup period.

Warmup Volume and Why It Counts Toward the Cap

Warmup is not free volume. Every warmup email is a real send that consumes the same sending reputation budget as a cold email. The reason we cap warmup at the same level as cold sends (12 on Google, 3 on Outlook) is that warmup beyond that ratio stops helping and starts looking like noise to the filters. A 1:1 warmup-to-cold ratio is what we have measured as the sustainable equilibrium.

Warmup runs continuously, not just during the initial warmup period. Even mature inboxes that have been sending for six months keep their warmup flow active. This is what keeps the engagement signal positive when your cold reply rate dips during slow weeks. The full warmup model is on /blog/cold-email-warmup-guide.

The Ramping Schedule

New inboxes do not start at the cap. We ramp every inbox on a 3-6-9-12 schedule over four weeks on Google, and a 1-2-3-3 schedule over three weeks on Outlook. Concretely:

Google Workspace ramping

  • Week 1: 3 cold sends per inbox per day, 3 warmup per day.
  • Week 2: 6 cold sends per inbox per day, 6 warmup per day.
  • Week 3: 9 cold sends per inbox per day, 9 warmup per day.
  • Week 4 onward: 12 cold sends per inbox per day, 12 warmup per day (cap).

Outlook 365 ramping

  • Week 1: 1 cold send per inbox per day, 1 warmup per day.
  • Week 2: 2 cold sends per inbox per day, 2 warmup per day.
  • Week 3 onward: 3 cold sends per inbox per day, 3 warmup per day (cap).

If you provision a batch of inboxes today, your effective cold send capacity does not hit the maximum until week 4 (Google) or week 3 (Outlook). Plan campaign starts around that. The getting-started flow walks through scheduling at /getting-started.

What Happens If You Exceed the Limits

Per our Terms, Puzzle Inbox reserves the right to terminate any account that exceeds the per-inbox sending limits at our discretion. This is not a soft warning system. The limits exist because exceeding them creates anti-abuse signal that damages the shared infrastructure other customers depend on. If one customer's tenant gets flagged for sending velocity, that hurts the entire pool of domains we operate.

The enforcement is automated. We monitor send velocity per inbox in real time, and inboxes that breach the cap get throttled at the OAuth layer. Repeat breaches trigger account review. We do not give second and third warnings because by the third warning the domain reputation is already cooked. If you need more volume, the answer is more inboxes, not more sends per inbox. Buy more domains on /pricing.

OAuth Only, No SMTP or IMAP

Every inbox we provision connects to your sending tool over OAuth. We do not issue SMTP credentials or IMAP credentials. This is partly a security decision and partly a deliverability decision. SMTP relays have a worse sending reputation than OAuth-authenticated sends, because Google and Microsoft can verify the sending application identity over OAuth. Cold email sent over SMTP from a Workspace mailbox in 2026 gets filtered at a noticeably higher rate than the same content sent over OAuth.

The practical impact is that any sending tool you use needs OAuth support for Google Workspace and Microsoft 365. The major cold email platforms all support this. If you are evaluating tools, OAuth compatibility is a hard requirement before anything else.

Per-Inbox Volume vs Per-Domain Volume vs Per-Tenant Volume

One more layer of math worth understanding. Cold email sending limits apply at three levels:

  • Per-inbox volume: 12 cold on Google, 3 cold on Outlook. This is the reputation unit.
  • Per-domain volume: 36 cold on Google (3 inboxes x 12), 300 cold on Outlook (100 inboxes x 3). This is the DNS unit.
  • Per-tenant volume: not directly capped by us, but Microsoft and Google watch tenant-level send velocity. Running 50 domains in one Microsoft tenant looks different from 50 domains spread across 50 tenants.

We provision each domain on its own tenant for Outlook to keep tenant-level signal clean. Each Google domain runs on its own Workspace organization for the same reason. This is invisible to you as the operator, but it matters when you scale cold email past 5,000 per day.

Why You Should Not Try to Cheat the Limits

Some operators try to game the system by spinning up inboxes outside Puzzle Inbox and pushing past the caps. We see the same pattern every quarter. Two months in, the domains start landing in spam. By month three, the tenant gets flagged and the operator is back asking us for fresh domains. The math never works. Lower per-inbox volume sustained over six months beats higher per-inbox volume that burns out in six weeks.

If your cold emails are already landing in spam, the fix is almost always lower per-inbox volume, better warmup, and better content, not workarounds. We have a full diagnostic flow on /blog/cold-emails-landing-in-spam-fix.

Delivery Timing

Every order ships in 24 to 72 hours. That timing includes domain registration, MX and SPF and DKIM and DMARC setup, mailbox provisioning, and OAuth handshake. You will not hit the full cold email sending volume on day one because of the ramping schedule above, but the infrastructure is ready to start ramping within three days of order.

How to Pick Your Starting Mix

If you are new to cold email at scale, start with one of these three configurations:

  • Small mix (under 500 cold/day): 2 Outlook domains (600 cold/day cap once ramped). Cheap, fast to ramp, simple to manage.
  • Medium mix (500 to 2,000 cold/day): 5 Outlook domains plus 5 Google domains. Outlook carries volume, Google adds sender diversity.
  • Large mix (2,000 to 10,000 cold/day): 15 to 35 Outlook domains plus 10 to 30 Google domains. At this scale, you want a dedicated operator running the campaigns.

None of these are static. The right mix changes as you learn which sender domains your audience replies to. Most accounts shift their ratio twice in the first six months. Pricing for each option is on /pricing.

Final Notes on Scaling Cold Email

The point of this whole article is that you cannot scale cold email by raising per-inbox volume. You scale by adding inboxes. The per-inbox cold email sending limits are physics, not policy. Google's 12 cold per inbox per day and Outlook's 3 cold per inbox per day are the numbers that keep deliverability sustainable. Everything else, the domains, the warmup, the OAuth, the ramping, is in service of holding those per-inbox numbers steady.

If you build your campaign math around 12 + 12 on Google and 3 + 3 on Outlook, you will know exactly how many inboxes you need for any daily target, you will know how long ramping will take, and you will not get surprised by deliverability collapse two months in. That is the entire job.

Related Reading

Discussions From the Community