How many inboxes and domains you need for cold email, by volume
How many inboxes and sending domains your cold email volume actually requires, with the math worked by daily target, the costs and where the shortcuts break.
ON THIS PAGE · 8 SECTIONS
- The two inputs that decide the number
- Inbox caps by age and setup
- Domains and inboxes by daily send volume
- Why subdomains do not multiply your headroom
- How many spare domains to hold in reserve
- What a setup like this actually costs
- Build the ramp before the volume arrives
- Questions about how many inboxes you need for cold email
THE SHORT VERSION
- Inboxes needed equals your daily send target divided by the safe sends per inbox per day, usually 20 to 30 once an inbox is warmed, up to 40 on an aged domain or a dedicated IP.
- Domains needed equals inboxes divided by inboxes per domain, 2 to 3 is the safe range. Fewer per domain costs more domains but caps how much volume one bad domain can take down with it.
- A team sending 1,000 cold emails a day needs roughly 35 to 45 inboxes across 12 to 20 domains, not the 3 or 4 a vendor's starter package tries to sell.
- Subdomains of one root domain do not buy you separate headroom against Google's 5,000-a-day bulk sender threshold. The count rolls up to the primary domain either way.
- Hold 15 to 20 percent of your domains as pre-warmed spares, so a flagged domain does not take a live campaign offline while a fresh one warms from zero.
How many inboxes you need for cold email comes down to a division problem, not a vendor package. Take your daily send target, divide it by how many emails one inbox can safely send a day, then divide that number again by how many inboxes you are willing to put behind a single domain. A team sending 500 emails a day lands around 17 to 20 inboxes split across 6 to 10 domains. A team sending 5,000 a day lands around 170 to 200 inboxes across 60 to 100 domains. The exact figures move with how aggressive your sending caps are and how much domain concentration risk you accept, but the formula underneath never changes.
If you just want the number for your own volume, use our free domains and inboxes calculator. The rest of this article explains the math behind it.
This piece sets out the caps that actually hold up in 2026, a volume to infrastructure table you can adapt to your own numbers, why buying subdomains instead of separate domains does not multiply your headroom, how many spare domains to keep in reserve and what the whole stack costs. For the layers underneath this number, authentication, warmup and monitoring, we covered those in outbound infrastructure architecture. This piece is the calculator that sits on top of it.
The two inputs that decide the number
Most teams size their inbox count from whatever a sending tool's default package offers, then wonder six weeks in why they are either throttled or sitting on idle capacity. The number comes from two inputs you already have, not from a vendor's bundle.
The first input is your daily send target, which should come from your account list and your cadence, not from a round number that sounds ambitious. If you have not sized that list yet, our guide on how to build a TAM list covers that step. The volume math here only makes sense once that number is real. The second input is your safe sends per inbox per day, which depends on how old the inbox is and whether it sits on a shared or dedicated IP. Multiply those two together and you get capacity per inbox. Divide your target by that capacity and you get inboxes. Divide inboxes by how many you allow per domain and you get domains. Three numbers, one formula. Everything below is just filling in the inputs correctly.
Inbox caps by age and setup
The safe sends per inbox per day is the number teams get wrong most often, usually by copying a figure from a blog post without checking how old that writer's domains were.
Source: Litemail, 2026
Plan your build around 25, the middle of the warmed range, unless you already know your setup sits at the aggressive end with aged domains and dedicated IPs behind every inbox. Planning around 40 from day one and hitting a wall at 15 because your domains are three weeks old is the single most common way teams end up short on sending capacity right when a campaign needs it most.
Domains and inboxes by daily send volume
Here is the math worked out across five common targets, using 25 safe sends per inbox per day and rounding up to whole inboxes and whole domains.
| Daily send target | Inboxes needed | Domains at 3 per domain | Domains at 2 per domain |
|---|---|---|---|
| 300 | 12 | 4 | 6 |
| 500 | 20 | 7 | 10 |
| 1,000 | 40 | 14 | 20 |
| 2,000 | 80 | 27 | 40 |
| 5,000 | 200 | 67 | 100 |
Three inboxes per domain costs fewer domains to manage. Two per domain costs more domains but means losing one domain costs you less volume at once. Most teams land in between, closer to two for a first build and closer to three once a domain has a year of clean sending behind it.
If your real setup runs closer to 35 to 40 sends per inbox because your domains are aged and on dedicated IPs, cut these inbox and domain counts by roughly a third. If you are still in the first 90 days on every domain you own, plan around the low end of the cap instead and expect to add domains again once your sending history earns the higher ceiling.
Why subdomains do not multiply your headroom
A shortcut keeps coming back every time a team tries to cut their domain bill: buy one root domain, spin up ten subdomains under it and treat each one as a separate low-volume sender. It does not work. Google says exactly why in its own sender guidelines.
THE USUAL SHORTCUT
- Register one root domain.
- Create ten subdomains, each sending under the bulk threshold.
- Assume each subdomain counts as its own low-volume sender.
WHAT ACTUALLY HAPPENS
- Google counts messages per primary domain, aggregated across every subdomain of that root.
- All ten subdomains' volume adds up against the same 5,000-a-day bulk sender line.
- A reputation hit on the root domain reaches every subdomain hanging off it too.
Google defines a bulk sender as anyone sending close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. That count is calculated per primary domain, aggregated across the subdomains sitting under it. Cross that line and you are permanently treated as a bulk sender, required to hold SPF, DKIM and a published DMARC record with a spam complaint rate under 0.3 percent, ideally under 0.1 percent. Miss that bar and mail gets routed to spam or rejected outright.
Source: Gmail Help, email sender guidelines, 2026
Most teams running the volumes in the table above never get near 5,000 a day on a single domain, so the compliance line itself rarely bites. The real cost of the subdomain shortcut is reputation, not the threshold. A subdomain inherits enough of its root's standing that a spam complaint spike on one still drags on the others, which defeats the entire point of splitting volume across separate senders. Buy separate root domains for separate sending identities. Subdomains are for mail you are not willing to lose the main domain over, not a way to multiply your allowance.
How many spare domains to hold in reserve
A domain will eventually get flagged. A stale list segment, a copy angle that reads wrong to one mailbox provider's filter or just bad luck with a shared IP range will take one out sooner or later. The question is not whether that happens. It is whether you have somewhere to move the volume when it does.
FROM THE YARD
Keep 15 to 20 percent of your domain count as pre-warmed spares, sitting idle but ready. The moment a domain's spam complaint rate climbs past 0.1 percent, move that campaign's volume to a spare while the flagged domain rests for 60 to 90 days. A spare that is already warm costs you nothing but a bit of idle capacity. A replacement warmed from zero costs you two to four weeks of sending while the campaign it was supposed to carry sits stalled.
For the 1,000-a-day tier in the table above, 14 domains at three inboxes each means holding 2 to 3 extra domains warmed and waiting at all times, not bought the week a domain gets flagged. Most flagged domains never go back into full sending once they rest. Treat the spare as the real replacement. Treat the recovered domain as a bonus if it turns out clean.
What a setup like this actually costs
The inbox and domain count translates directly into a monthly bill. It is smaller than most teams expect once they stop pricing pre-warmed inboxes at the top of the market.
Source: Maildeck, cold email infrastructure cost, 2026
Work it through the 1,000-a-day tier: 40 inboxes at $2.50 to $6 a month runs $100 to $240. Add 14 domains at $10 to $15 a year, roughly $12 to $18 a month. Call it $115 to $260 a month for mailboxes and domains before the sending tool that rotates and schedules across them. Google Workspace caps you at 5 mailboxes per domain by platform rule, which is well above the 2 to 3 we recommend for reputation reasons, so the platform limit is rarely what constrains you. Microsoft 365 allows more mailboxes under one domain than Google Workspace does, which some providers use to cut the domain count and the bill that comes with it, but packing more mailboxes onto fewer domains brings back the concentration risk the per-domain cap was meant to avoid in the first place. Cheaper is not better if one bad domain now costs you five times the volume.
New inboxes need a ramp before they carry this volume. Our founder Hlib Storchak covers how to warm up cold email domains step by step on storchak.eu.
Build the ramp before the volume arrives
None of these numbers are useful if the domains and inboxes are not already warmed by the time a campaign needs them. Infrastructure takes weeks to earn trust and cannot be rushed into existence the week a list is ready to send.
- Size the target first. Pull the daily number from your account list and cadence, not from ambition. A list that supports 300 accounts a month does not need a 5,000-a-day build.
- Register domains and inboxes 30 days ahead. Buy the domains, configure DNS, publish SPF, DKIM and DMARC and let the mailboxes receive a few days of normal mail before any sending starts.
- Ramp each inbox over 4 weeks. Start around 5 to 15 sends a day and increase gradually rather than jumping straight to the warmed cap, which reads as automation to every major mailbox provider.
- Connect to real campaigns once warmed. Only move an inbox onto live cold volume after it has cleared the ramp, at the 20 to 30 a day ceiling, not before.
- Review the spare count monthly. Check that 15 to 20 percent of domains sit warmed and idle, ready to absorb a flagged domain's volume without a gap.
More inboxes do not fix a list nobody wants to hear from. They just get the rejection delivered faster, from more addresses at once.
That last point is worth saying plainly. Infrastructure sized correctly protects delivery. It does not manufacture interest. No amount of extra domains fixes a weak account list or an offer nobody asked for. We size this exact stack as part of the infrastructure layer inside the system we build with clients, matched to the account list and cadence underneath it rather than sold as a fixed package.
Questions about how many inboxes you need for cold email
How many inboxes do I need to send 1,000 cold emails a day?
Around 35 to 45 inboxes at a conservative 20 to 30 sends per inbox per day, split across 12 to 20 domains depending on whether you hold 2 or 3 inboxes per domain. Fewer inboxes work once your domains are aged past 90 days and can carry 35 to 40 sends a day each.
How many inboxes can I safely put on one sending domain?
Two to three is the safe range. Google Workspace allows up to 5 mailboxes per domain by platform rule, but allowing it is not the same as it being safe. More mailboxes on one domain means one spam complaint spike or one blacklisting takes a larger share of your total volume down at once.
Do subdomains count separately from my main domain for Google's bulk sender rule?
No. Google counts messages per primary domain, aggregated across every subdomain sitting under it. Ten subdomains sending 600 messages a day each still add up to 6,000 against the same 5,000-a-day bulk sender line. A reputation problem on one subdomain affects the trust of the others too.
How many spare domains should I keep ready?
Plan for 15 to 20 percent of your domain count held as pre-warmed spares, sitting idle but ready to absorb a flagged domain's volume. A warm spare costs a small amount of idle capacity. A domain warmed from zero after a problem costs two to four weeks of stalled sending instead.
Is Microsoft 365 cheaper than Google Workspace for cold email infrastructure?
It can be, because Microsoft 365 allows more mailboxes under a single domain, which lowers the domain count and the registration bill for the same inbox total. That same flexibility concentrates more volume onto fewer domains, so the saving on domains trades against more risk if one of those domains gets flagged.
Sources: Gmail Help, email sender guidelines, 2026, Litemail, how many inboxes you need for cold email, 2026, Maildeck, cold email infrastructure cost, 2026