How Many Cold Emails Per Day Per Inbox? Limits vs Safe Volume

The technical ceiling is high: Google Workspace allows 2,000 messages per user per day and Microsoft 365 allows 10,000 recipients per mailbox per day. But those limits exist to stop abuse, not to tell you what is safe for cold outreach. Cold email tools advise far lower volumes (Instantly suggests 30 to 50 a day per inbox), and your own bounce and complaint numbers should set the real figure.

This post separates the two things people mix up: what the provider will technically let you send, and what you can send without hurting deliverability. All provider limits below were read from the providers' own pages on 1 October 2026.

The hard limits, from the providers' own documentation

The hard limits are per-user caps published by Google and Microsoft; exceed them and the account is blocked from sending for up to a day. They differ in what they count, which matters more than the headline number.

Google Workspace

From Google's Gmail sending limits in Google Workspace page:

Limit	Value
Messages per user per day	2,000 (1,500 for mail merge, 500 for trial accounts)
Total recipients per day	10,000
External recipients per day	3,000
Unique recipients per day	3,000, of which 2,000 external (500 external on trial accounts)
Recipients per message via SMTP/IMAP	100

Two lines from that page are worth quoting directly: "Sending limits can change without notice" and "Limits per day are applied over a rolling 24-hour period, not a set time of day." If you hit a limit, Google says the user can't send new messages "for up to 24 hours".

The row that bites cold senders first is unique external recipients: 2,000 a day. Every cold email goes to an external address, so that is the effective ceiling, not the 2,000 messages figure.

Personal Gmail

A free @gmail.com account is far tighter. Google's help page on sending limits describes the error appearing if you send to "more than 500 recipients in a single email and or more than 500 emails sent in a day", with recovery taking 1 to 24 hours. Cold outreach from a personal Gmail address is a bad idea for other reasons too, but the cap alone rules it out at any scale.

Microsoft 365 / Exchange Online

From Microsoft's Exchange Online limits service description:

Limit	Value
Recipient rate limit	10,000 recipients per day, per mailbox
Message rate limit	30 messages per minute
Tenant External Recipient Rate Limit (TERRL)	Depends on licence count; 5,000 a day for trial tenants
Sending from an onmicrosoft.com address	100 external recipients per organisation per 24 hours

Microsoft's page explains that once the recipient limit is reached, the mailbox cannot send again until its count over the previous 24 hours drops below 10,000. Hitting the onmicrosoft.com cap returns an NDR with code 550 5.7.236.

The tenant limit is the one small teams miss. Microsoft's page says it "depends on the number of licenses a tenant has" and points to its announcement post. Practical365 reports the formula from that announcement as 500 × (licences^0.7) + 9,500. Worked through:

Licences	Tenant-wide external recipients per day
1	10,000
5	11,043
10	12,006
25	14,259

The tenant cap grows slowly with licences, so adding mailboxes to the same tenant buys less headroom than you might expect. Microsoft is also blunt that "Exchange Online isn't suited to accommodate bulk-mailing scenarios."

Why the hard limit is the wrong number to plan around

The provider caps measure what the platform will carry, not what recipients' mail servers will accept into the inbox. Spam filtering on the receiving side looks at your reputation, your complaint rate and your bounce rate. None of that is aware of your Workspace quota.

Three published rules make this concrete:

1. Google's sender guidelines say: "Don't send messages to people who didn't sign up to get messages from you." (Google sender guidelines) There is no officially sanctioned cold volume, because cold email is outside what the guidelines describe. Every number you pick is a risk decision you are making yourself.
2. Google wants your user-reported spam rate below 0.3%, and ideally below 0.1%. At a 0.3% complaint rate, three complaints per thousand messages is enough to cross the line. A single inbox sending 2,000 cold emails a day only needs six people to press "Report spam".
3. Bulk sender status is counted per domain and is permanent. Google's bulk sender FAQ says "we count all messages sent from the same primary domain" toward the 5,000-a-day threshold, including subdomains, and that "Email senders that have been classified as bulk senders are permanently classified as such." Microsoft has a similar 5,000-a-day line for Outlook.com, Hotmail and Live addresses, above which mail that fails authentication is rejected with 550 5.7.515 (Microsoft support).

So more inboxes on the same domain do not get you under the bulk threshold. They only spread the per-user quota.

What cold email tools recommend

Sending platforms publish their own per-inbox guidance, and it sits well below the provider caps. Instantly's cold email strategy article says: "From each email, we're going to be sending only 30-50 emails a day to avoid getting stuck in spam." It also recommends "max 3-5 email accounts" per domain and a warm-up period of at least two weeks before campaigns start.

Treat that as one vendor's operating advice, not a measured threshold. Nobody outside Google and Microsoft knows where their filters draw lines, and those lines differ by sender history. What the 30-50 range does give you is a planning number roughly 40 to 67 times below Google's unique external recipient cap, which leaves room for the things that actually get inboxes flagged: a bad list, a spike in complaints, or a domain that is a week old.

Worked example: how many inboxes do you need?

Count total daily sends including follow-ups, divide by your per-inbox cap, then divide by inboxes per domain. The mistake most people make is sizing for new prospects only and forgetting the follow-ups already in flight.

Assumptions (change them for your own case):

• You want to start 200 new prospects a day.
• Each prospect gets a 3-step sequence (first email and two follow-ups).
• Each inbox sends 40 a day (the middle of Instantly's range).
• Each domain carries 3 inboxes (the bottom of Instantly's range).

Once the sequence is fully running, each day includes step 1 for today's prospects, step 2 for an earlier batch and step 3 for an earlier batch still. Ignoring replies and unsubscribes, which stop a sequence early, the steady state is:

Step	Daily sends
Step 1 (new prospects)	200
Step 2	200
Step 3	200
Total	600 a day

600 ÷ 40 = 15 inboxes. 15 ÷ 3 = 5 sending domains.

Now add the bounce cost. If the list has not been verified and 5% of addresses are dead, 10 of each day's 200 first emails bounce. If your sequencer stops a contact on a hard bounce, as it should, dead addresses never reach step 2 or 3, so the bounces all land on first touches: new recipients, at the point your domain has the least history with them. The 15 inboxes also share them unevenly, and a single inbox that draws a bad batch can see a far higher rate than the average. Verify first, and the remaining risk is mostly on catch-all domains, which you can send separately in smaller batches. Our verification cost calculator works out what that pass costs at your volume.

A ramp that respects both limits

Start low, increase only when the numbers stay clean, and stop the moment they don't. This is a framework, not a schedule backed by provider data:

1. Warm up first. New inboxes and domains need history before they carry cold volume. See email warm-up schedule for a week-by-week version.
2. Start each inbox below your target. If the target is 40, begin well under it and raise it in steps.
3. Check three numbers before every increase: hard bounce rate, spam complaints (Google's guidelines refer to the user-reported spam rate shown in Postmaster Tools), and reply rate.
4. Never raise volume to fix a bad week. If replies drop and bounces rise, the problem is the list or the message. More sends make it worse.
5. Keep every inbox well inside the provider cap. If you find yourself near 2,000 a day on one Workspace user, something has gone wrong with the plan.

Infrastructure checks that come before volume

Volume is the last thing to tune; authentication and list quality come first. Before you set any per-inbox number:

• SPF, DKIM and DMARC pass for every sending domain. Check them with the SPF checker and DMARC checker.
• Each secondary domain is set up properly, with its own records and a redirect to your main site. Setting up secondary domains for cold email covers the details.
• The list is verified and catch-all addresses are separated, so step 1 is not where your bounces pile up. If bounces are already a problem, start with why cold emails bounce.
• Your follow-up count is decided in advance, because it multiplies daily volume. See how many follow-ups a cold sequence should have.

The practical answer

The number Google or Microsoft lets you send is a ceiling designed to stop compromised accounts, and for cold outreach you should never be near it. Size your inbox count from total daily sends including follow-ups, use a conservative per-inbox figure such as the 30-50 range Instantly publishes, and let bounce and complaint data move it up or down. If your numbers are bad at 30 a day, they will be worse at 300.

Before you plan volume, run your sending domain through the free deliverability audit to confirm the authentication basics are in place.