How many cold emails a day is safe on one domain

No single "safe number" is published by anyone who actually enforces the limits you are worried about. Google Workspace caps a paid mailbox at 2,000 messages a day and Microsoft 365 caps a mailbox at 10,000 recipients per rolling 24 hours (knowledge.workspace.google.com and learn.microsoft.com, checked 2026-08-27). Neither cap is the thing that gets a solo domain flagged. The real constraint is your spam complaint rate, and it bites long before volume caps do: a mailbox sending far below any published limit can still get flagged for reputation problems well short of Google's bulk-sender volume threshold, and once a domain is classified as a bulk sender, Google's own compliance floor is a spam rate under 0.30% or it loses inbox delivery until seven consecutive clean days pass (support.google.com/mail/answer/81126 and support.google.com/a/answer/14229414, checked 2026-08-27). For one mailbox on one domain with nobody watching deliverability full time, that means starting around 30 to 50 emails a day, ramping to 60 to 150 once the mailbox has a few weeks of history, and never treating a platform's stated ceiling as your target.

You are reading this because you are about to send a batch and you do not have a deliverability person to ask. Here is what the two mailbox providers actually publish, what five outreach vendors independently recommend, and where the two numbers stop lining up.

The hard cap vs. the real constraint

Google's published ceiling for a paid Workspace mailbox is 2,000 messages a day, with a maximum of 3,000 unique external recipients a day and 500 external recipients on any single message (knowledge.workspace.google.com/admin/gmail/gmail-sending-limits-in-google-workspace, checked 2026-08-27). That number reads like a target. It is not one. Google separately defines a "bulk sender" as anyone sending close to 5,000 messages or more to personal Gmail accounts within 24 hours, and bulk senders face mandatory SPF, DKIM, DMARC, one-click unsubscribe, and a spam rate kept under 0.30% or lose inbox delivery until seven consecutive clean days pass (support.google.com/a/answer/14229414, checked 2026-08-27). A one-person outbound desk sending 300 emails a day is nowhere near the 2,000 cap and can still get flagged, because the complaint math does not care about the cap.

Run the arithmetic on a small batch. At 50 emails a day, a single spam click is a 2% complaint rate, nearly seven times over Google's hard compliance floor. At 300 a day, one complaint is 0.33%, still over the line. You need enough volume that one or two bad reactions do not blow the ratio, and low enough volume that a new mailbox is not sending a pattern that looks automated. That tension, not the published cap, is what sets your real ceiling.

Google Workspace numbers, at source

Free personal Gmail gets blocked past 500 recipients in a single message or 500 messages sent in a day (support.google.com/mail/answer/22839, checked 2026-08-27). That is the ceiling most people confuse with the Workspace number, and it is not the one that applies once you are paying for a business mailbox.

A paid Workspace account gets 2,000 messages a day, up to 10,000 total recipients a day, up to 3,000 unique external recipients a day, and a per-message cap of 500 external recipients (2,000 recipients counting internal). A free-trial Workspace account is capped lower, at 500 messages and 500 external unique recipients a day, and that ceiling rises only once the domain has cumulatively paid at least $100 (knowledge.workspace.google.com, checked 2026-08-27).

The bulk-sender rules took effect February 1, 2024, with enforcement escalating from April 2024, a timeline corroborated independently by MarTech (martech.org). Cross a threshold and your domain needs SPF plus DKIM authentication (required for every sender regardless of volume), DMARC at minimum p=none for bulk senders, a From: domain that matches your SPF/DKIM organizational domain, TLS on the connection, and one-click unsubscribe honored within 48 hours for marketing mail. Exceed your quota outright and Google returns SMTP error 4.7.28, with guidance to pause at least 10 minutes and resume at a reduced rate.

Microsoft 365/Outlook numbers, at source

Exchange Online and Microsoft 365 mailboxes, across Business Basic through Enterprise E5 and Exchange Online Plans 1 and 2, share one recipient rate limit: 10,000 recipients per mailbox per rolling 24 hours, with a default per-message limit of 500 recipients across To, Cc, and Bcc (org-configurable between 1 and 1,000), and a message rate limit of 30 messages per minute per mailbox (learn.microsoft.com Exchange Online Service Descriptions, checked 2026-08-27).

There is a second, tenant-wide limit that gets confused with the mailbox limit: the Tenant External Recipient Rate Limit, which scales with licensed seats. Trial tenants are capped at 5,000 recipients per 24 hours tenant-wide, and any domain still on the default onmicrosoft.com address is capped at 100 external recipients per 24 hours, also tenant-wide. If you are on a paid seat with your own custom domain, this tenant limit will not bind a one-person operation. If you are still sending from a default onmicrosoft.com address, it will, and it is the more likely reason a batch stalls.

Outlook.com behaves differently depending on whether the account is a Microsoft 365 subscriber. A subscriber account gets 5,000 recipients a day, 500 per message, and a stricter 1,000-a-day sub-limit specifically for "non-relationship" recipients, people who have not emailed you back (support.microsoft.com, checked 2026-08-27).

Microsoft's own documentation describes the free-account limit only in general terms, saying it varies by usage history and runs lower than the subscriber limits, without publishing a specific figure (support.microsoft.com, on free Outlook.com sending limits).

What vendors recommend, and why they converge

The mailbox providers set the outer boundary. The vendors who sell warm-up and sending tools set the number people actually use day to day, and four of them land in roughly the same place independently.

Every one of these is a vendor with a commercial interest in the number it recommends, so treat the table as a consensus check, not a citation of authority. But the convergence is the finding: four separate companies selling different tools land within the same band, roughly 30 to 50 a day for a mailbox with no sending history, 60 to 150 once it has a few weeks of consistent, low-complaint activity behind it, and general agreement that pushing past 150 to 200 a day from a single inbox is where things start breaking. Smartlead is the one vendor with an explicit domain-level number, around 500 a day per domain, and it gets there by running multiple mailboxes on that domain, not by raising any single mailbox's ceiling.

The reasoning behind the convergence is consistent across all of them. Gmail's Postmaster Tools and Microsoft's SNDS both score a sending pattern over time, not a single day's volume. A new mailbox sending a small, steady batch that gets opened and replied to builds trust faster than the same mailbox sending a large batch on day one, even if that large batch is still under the provider's published cap.

Per mailbox vs. per domain, the unit that matters for you

Google's 2,000-a-day figure and Microsoft's 10,000-recipient figure are both per mailbox, not per domain, and that's the correct planning unit for a single sender: you have one mailbox and one domain, so the mailbox is where warm-up history accumulates and where the rate limits actually apply day to day. (Running several mailboxes on one domain changes the math: Google's per-mailbox allowances stack, but domain-level reputation still governs all of them together, and Microsoft layers a separate, tenant-wide recipient limit on top. That's a different planning problem from the one you have with a single inbox.)

The domain still matters here, for authentication, SPF, DKIM, DMARC alignment, and for the reputation signal that follows you if you eventually add a second mailbox on it. But the volume dial you are turning right now, the one that decides whether tomorrow's batch is 40 or 400, is a per-mailbox decision, and every source above measures it that way. Scaling past one mailbox turns that into a purchase rather than a setting, and forty inboxes costs $131 a month at Zapmail's published prices, not the $60 the one public estimate budgets.

Start closer to 30 to 50 a day than to 2,000. Watch reply and bounce rates weekly rather than trusting a single sending session. Raise volume only after a few consecutive weeks without a spike in complaints, and treat any provider's published ceiling as the point past which you have already left the safe range, not the number you are trying to reach. If you are weighing all of this against LinkedIn instead, the comparison that decides it is which of the two ceilings binds first at your volume.