Most senders should use a shared IP. A dedicated IP only pays off above roughly 100,000 emails a month sent consistently, with the discipline to warm it and keep it warm.
Most senders should use a shared IP. A dedicated IP only pays off above roughly 100,000 emails a month sent consistently, with the discipline to warm it and keep it warm. Below that volume the IP sits under-loaded, its reputation gets thin between sends, and a well-run shared pool beats it.
If you run cold email from Google Workspace or Microsoft 365 mailboxes, you are already on shared infrastructure and that is the right call. The dedicated-versus-shared decision only comes up when you send through a standalone provider like Amazon SES, SendGrid, or Postmark at real scale. This is a comparison post: the verdict is shared for nearly everyone, and here is the math that says so.
A shared IP is a sending IP address used by many senders at once, with reputation pooled and managed by the email service provider. A dedicated IP is a single address used by one sender, who owns its reputation entirely. Shared IPs suit senders below roughly 100,000 emails a month; dedicated IPs suit high-volume senders with consistent daily patterns and dedicated deliverability management.
Shared, unless every one of these is true: you send more than about 100,000 emails a month, your daily volume is steady rather than spiky, and someone on your team owns deliverability as a job. Miss any one and a dedicated IP will likely hurt you, because a lightly used dedicated IP has no reputation momentum and every gap in sending lets it cool.
| Dimension | Shared IP | Dedicated IP |
|---|---|---|
| Monthly cost | Included in the plan | $50 to $500 per IP, commonly $100 to $250 |
| Warm-up burden | Pool is already warm | You warm it from zero over weeks |
| Reputation control | Shared with other senders | Entirely yours, good and bad |
| Volume fit | Under ~100,000 / month | Over ~100,000 / month, consistent |
| Neighbor risk | A bad sender in the pool can affect you | None, you are the only sender |
| Best for | Startups, small teams, variable volume | Enterprise senders, steady high volume |
A pool of IP addresses that many customers of an email provider send through together. The provider manages the pool: it vets new senders, enforces complaint and bounce thresholds, and removes accounts that put the pool at risk. Because dozens or hundreds of senders use it continuously, the pool stays warm on its own, so your mail benefits from established reputation from day one.
The tradeoff is that you do not fully control the IP's reputation. A high-quality provider that polices its pool aggressively makes this a non-issue for most senders. A lax provider that lets spammers in makes it a real risk. The pool's management quality matters more than the fact that it is shared.
One IP address, used only by you. Its reputation reflects your sending and nothing else. That is the appeal: no neighbors, full control, and a reputation you can build deliberately.
It is also the catch. A dedicated IP starts with no reputation and has to be warmed from zero over several weeks, sending small volumes that ramp gradually. And it needs a steady stream of mail forever after to stay warm. An IP that sends 5,000 one day and nothing for three days looks unstable to mailbox providers, which is worse than being one clean sender in a well-run pool.
Industry guidance puts the practical floor near 100,000 emails a month, with 300,000 the point where a dedicated IP reliably maintains its own reputation. Below 100,000, the IP is under-loaded and the warm-up discipline outweighs the reputation benefit.
The cost math points the same way. At $100 to $250 a month for the IP, the per-email cost only makes sense once you are sending 100,000 to 200,000 a month. Under that, a shared IP is both cheaper per email and better for deliverability.
Mailbox providers care about predictable sending patterns as much as absolute numbers. A sender doing 120,000 a month in a smooth daily rhythm is a good dedicated-IP candidate. A sender doing 120,000 a month in three big batches around campaign launches is not, because the IP goes cold between batches and each spike reads as anomalous.
If your volume is high but lumpy, a shared pool absorbs the variance for you. That is one of the quiet benefits of shared infrastructure: the pool's baseline traffic smooths out your peaks and troughs.
For cold outreach, this decision usually does not apply. Cold email runs from mailboxes on secondary domains hosted on Google Workspace or Microsoft 365, and those send through the provider's shared outbound IPs. You do not get to choose, and you should not want to: a cold operation running 40 emails per mailbox per day across a dozen mailboxes is sending maybe 15,000 a month, far below any dedicated-IP threshold.
Standalone SMTP providers like Amazon SES, SendGrid, and Postmark offer a dedicated IP as a paid add-on, mostly for transactional and marketing mail at scale. If you are considering one for cold email, the honest answer is that your domain reputation and list quality will decide your inbox placement far more than the IP type will. The rest of your setup matters more too: SPF, DKIM, and DMARC, warm-up, inbox rotation, and staying inside Gmail and Outlook sending limits.
Agencies running cold email for many clients face a version of this decision. Some cold email infrastructure providers sell "dedicated pools," small groups of IPs reserved for one customer's mail. The pitch is isolation without the volume burden of a single dedicated IP.
The reality check: a pool of three lightly used IPs has the same cold-reputation problem as one lightly used IP, just spread thinner. It only helps if the combined volume across the pool clears the warm-enough threshold. Below that, a well-managed general shared pool, where your clients' mail rides alongside thousands of vetted senders, delivers better. See how to set up cold email infrastructure and why are my emails going to spam.
The Warm-Enough Threshold: a dedicated IP only helps if you can feed it enough steady volume to stay warm, roughly 100,000 a month or about 3,000 a day, every day. Below that floor, the IP cools between sends and a well-run shared pool beats it.
The threshold turns a vague debate into one arithmetic check. Add up your genuine monthly sending volume, not your peak, your average. If it is under 100,000, stop here: use a shared IP, and put your effort into list quality and domain reputation, which is where your inbox placement is actually won or lost.
If it is over 100,000, ask the second question: is it steady, and does someone own it? Two yeses mean a dedicated IP is a reasonable move. A no on either means you will get more from staying on a managed pool a while longer. The quotable version: "A dedicated IP is a responsibility you buy, not a result you buy."
Most senders, and nearly every cold email sender, are better off on shared for years longer than they think.
IP type is a smaller lever than most people expect. What decides whether your mail reaches the inbox, on shared or dedicated, is your complaint rate and bounce rate, and both come from the list.
InboundLabs is a sales intelligence platform built on a database of 280M verified B2B contacts with 98% email deliverability on verified contacts. It layers buyer intent signals on firmographic data and lets you filter by industry, headcount, region, and title, so your sends stay clean and relevant no matter what infrastructure they go through. Monthly plans, no annual lock-in. Free to start, no credit card required.
See how InboundLabs finds verified contacts instantly → inboundlabs.app
Use a shared IP unless you send more than about 100,000 emails a month, consistently, with a person who owns deliverability. Below that, a dedicated IP is under-loaded, expensive per email, and a warm-up burden you take on for no gain. Cold email from Workspace or Microsoft 365 mailboxes runs on shared IPs by design, and that is correct: a typical cold operation sends a fraction of the dedicated-IP threshold. Spend the energy you would put into IP management on list quality and domain reputation instead, because that is what actually moves inbox placement.
Should I use a dedicated or shared IP for cold email?
Shared. Cold email runs from Google Workspace or Microsoft 365 mailboxes on the provider's shared IPs, and a typical cold operation sends around 15,000 a month, far below the roughly 100,000 monthly volume where a dedicated IP starts to make sense. Your domain reputation and list quality decide inbox placement far more than IP type.
At what volume does a dedicated IP make sense?
Around 100,000 emails a month as a practical floor, and closer to 300,000 for a dedicated IP to reliably hold its own reputation. Below 100,000 the IP is under-loaded, its reputation stays thin between sends, and the per-email cost of the IP is higher than staying on a shared pool.
How much does a dedicated IP cost?
Typically $50 to $500 per IP per month depending on the provider and tier, most commonly $100 to $250. That fixed cost only produces a competitive per-email rate once you are sending 100,000 to 200,000 a month, which is another reason low-volume senders should stay on shared IPs.
What is the risk of a shared IP?
That another sender in the pool behaves badly and drags down the shared reputation. A provider that vets senders, enforces strict complaint and bounce limits, and removes risky accounts keeps this from mattering. The pool's management quality is the thing to evaluate, not the fact that it is shared.
Does a dedicated IP improve deliverability?
Only if you send enough consistent volume to keep it warm and actively manage its reputation. A lightly used or spiky dedicated IP delivers worse than a clean sender on a well-run shared pool. IP type is a smaller factor than list quality, authentication, and domain reputation.
Do I need to warm up a dedicated IP?
Yes, from zero, over several weeks, sending small volumes that ramp gradually while you watch complaint and bounce rates. And it needs steady sending afterward to stay warm. A shared pool skips this entirely because it is kept warm by the continuous traffic of every sender in it.
A real email deliverability test sends your message to a set of seed addresses across Gmail, Outlook, Yahoo, and business domains, then reports where each one landed: primary inbox, Promotions, spam, or blocked. A spam score out of 10 is not that.
In September 2025, Google removed the domain and IP reputation dashboards from Postmaster Tools. The one chart most senders used to check domain reputation is gone.
Inbox rotation means sending one campaign from many mailboxes instead of one, so no single account sends enough volume to trip a spam filter. Instead of pushing 200 emails a day through one inbox, you push 20 a day through ten.
Gmail's technical sending limits in 2026: a free Gmail account can send to 500 recipients per rolling 24 hours, and a Google Workspace account can send to 2,000 recipients per day, of which a maximum of 2,000 can be external. New Workspace accounts start much lower, often around 500 a day, and...
No commitment. No credit card. Just 50 free verified contact lookups.