- Sending consistency matters more than raw volume when choosing between a shared and a dedicated IP.
- A well-managed shared pool usually beats a cold or poorly run dedicated IP for senders under a few hundred thousand emails a month.
- A dedicated IP gives you full control of IP reputation, which rewards disciplined senders and exposes careless ones.
- Dedicated IP pricing varies widely: some plans include one, such as SendPulse SMTP Pro, while SendGrid, Amazon SES and Mailgun tie it to higher tiers or charge extra.
- Hybrid setups that separate transactional and marketing traffic by IP and subdomain often outperform going all in on either model.
“Get a dedicated IP once you hit 100,000 emails a month” is one of the most repeated rules in email, and one of the least useful. Plenty of senders above that line get worse results on a dedicated IP than they would on a well-run shared pool. Some senders below it genuinely benefit from one because of how, and how steadily, they send.
This guide swaps the volume rule for a real decision framework. By the end you will know which model fits your sending pattern, what each option actually costs across the main providers, and what you are signing up for either way.
What actually changes between shared and dedicated
Shared and dedicated IPs use the same SMTP servers, the same authentication (SPF, DKIM, DMARC) and the same content processing. The difference is who controls the reputation of the IP address your mail leaves from.
Shared IP. Your ESP spreads many customers across a pool of addresses and manages the pool’s reputation. Your behavior contributes, but does not decide the outcome alone. A good pool has strict onboarding, fast enforcement against high complaint rates and monitoring for compromised accounts. A bad pool has none of these, and every bad sender drags everyone down.
Dedicated IP. The address is yours alone, so your sending is the only thing receivers judge it on. Bad neighbors cannot hurt you, but good neighbors cannot help you either. A new dedicated IP starts with no history and has to be warmed up from scratch.
One thing does not change: your domain reputation. Gmail and other major providers weight the sending domain heavily, and it follows you across IPs. Changing the IP model is not a way to escape a damaged sender reputation.
The quick decision table
Use this as a starting point, then check the sections below for the factors that can move you up or down a row.
| Monthly volume | Sending pattern | Recommended model | Why |
|---|---|---|---|
| Under 50,000 | Any | Shared | Not enough volume to build or hold IP reputation on your own |
| 50,000 to 100,000 | Irregular or weekly bursts | Shared | Pool smooths out the spikes |
| 50,000 to 100,000 | Daily, steady, strong hygiene | Shared, or dedicated if included with your plan | Dedicated can work if volume is consistent and you can warm it |
| 100,000 to 500,000 | Weekly bursts | Shared, or dedicated with sends split across days | Bursts on a dedicated IP look suspicious |
| 100,000 to 500,000 | Daily, steady | Dedicated is reasonable | Enough steady signal to own a reputation |
| 500,000 to 2 million | Daily, steady | Dedicated | Your traffic dominates what receivers see anyway |
| Over 2 million | Multiple traffic types | Multiple dedicated IPs | Isolate reputation per stream |
| Any | Regulated industry or audit need | Dedicated | Clean isolation boundary for compliance |
What a dedicated IP really costs
The sticker price is only part of the cost. Pricing below is approximate and changes often, so confirm on each provider’s pricing page before you budget.
| Provider | How dedicated IPs are offered | Approximate cost |
|---|---|---|
| SendPulse SMTP | Included on the SMTP Pro plan (100,000 emails per month) | Plan from about €56/month with 6-month billing |
| SendGrid (Twilio) | Included on Pro-level plans, not on entry tiers; extra IPs available | Pro plans start in the high double digits per month; extra IPs cost more |
| Amazon SES | Paid add-on per dedicated IP, plus a managed dedicated IP option | Roughly $24.95/month per standard dedicated IP, on top of per-email fees |
| Mailgun | Included on higher-volume plans, otherwise tied to upgrades | Depends on plan tier |
SendPulse is one of the few providers that bundles a dedicated IP into a mid-volume plan rather than charging extra; see the SMTP pricing page for current terms. The limitation is the same as everywhere else: an included IP still arrives cold, so you need the discipline and the steady volume to warm and maintain it. SES is often the cheapest per email at scale but expects you to handle more of the monitoring and bounce processing yourself. SendGrid and Mailgun sit between the two, with more built-in tooling and higher plan prices.
The hidden costs
Warmup time. A new dedicated IP needs roughly four to six weeks of controlled ramping before full production volume. If you have a launch next week, a new dedicated IP is not an option.
Operational overhead. Someone has to watch bounces, complaints, Google Postmaster Tools, Microsoft SNDS and blocklists for that specific IP, and act fast when something slips. For a team with email operations staff, that is routine. For a marketer juggling ten other priorities, it is a gap where problems go unnoticed until customers complain.
Consistency. Receivers expect a dedicated IP to have a stable pattern. Sending 80,000 emails every Monday and nothing the rest of the week creates volatility that hurts delivery. A shared pool averages thousands of senders and produces a steady pattern automatically.
When a shared IP wins
Shared IPs are the right choice for more senders than conventional advice suggests. Choose shared if any of these apply.
You send under roughly 100,000 emails a month
At low volume, a dedicated IP simply does not generate enough engagement data for receivers to build a strong opinion. A pool with thousands of senders produces steady, diverse traffic, and your mail benefits from that established reputation.
Your volume is irregular
If you send half a million emails during launch week and then nothing for a month, a dedicated IP becomes a liability. Receivers see a spike from an address with thin history and filter it. On a shared IP, your spike blends into the pool’s normal traffic.
Nobody owns deliverability full-time
If no one reads DMARC reports, watches Postmaster Tools or responds to blocklist alerts, a dedicated IP can quietly degrade for months. Reputable ESPs build that monitoring into their shared pools. Use it.
You mix transactional and marketing on low volume
Small and mid-size senders often run receipts and newsletters through the same account. Good ESPs separate these into different shared pools automatically. Doing the same on dedicated IPs means managing two IPs and two warmups.
When a dedicated IP wins
You send consistently at high volume
Once you are sending several hundred thousand emails a month, spread across most days, your own traffic dominates what receivers see from the IP. Full control becomes an asset, and you have enough data to measure deliverability independently of the pool.
You work in a regulated industry
Financial services, healthcare, government and legal senders often need isolated infrastructure for audit or compliance reasons. A dedicated IP provides a clean, documentable boundary.
You need isolation from neighbors
If you have been hit by a bad neighbor in a shared pool before, a dedicated IP removes that risk. Your IP reputation is entirely your own.
You want a branded PTR hostname
On a shared IP, reverse DNS resolves to the ESP’s hostname. On a dedicated IP you can usually set it to something like mail.yourdomain.com, with forward-confirmed reverse DNS. It is a small trust signal, but it matters in B2B, where recipients and their security teams inspect headers. You can check what your mail currently shows with the header analyzer and the reverse DNS checker.
Received: from mail.yourdomain.com (mail.yourdomain.com [203.0.113.25])
by mx.recipient.example with ESMTPS id ...The hybrid approach
Many mature senders split traffic across both models by stream. The key idea is to isolate reputation where it matters most.
| Pattern | Best for | Trade-off |
|---|---|---|
| Dedicated for transactional, shared for marketing | Steady transactional volume, bursty campaigns | Two platforms or plans to manage |
| Dedicated for marketing, shared for transactional | Large marketing volume, modest transactional | Marketing mistakes affect only your own IP |
| Multiple dedicated IPs by stream | Very high volume, several distinct audiences | Each IP must be warmed and monitored |
Transactional mail (password resets, order confirmations, shipping updates) usually has steady volume and very low complaints, which suits a dedicated IP well. Marketing mail has spikes and higher complaint rates. Our guide to transactional vs marketing deliverability explains why keeping them apart protects the mail customers are waiting for.
How to evaluate a shared IP pool
Not all shared pools are equal, so if you choose shared, choose the ESP carefully. Our bulk email services comparison covers how the major platforms run their infrastructure. Questions worth asking:
- How are new senders vetted? Pools that accept anyone with a card are riskier than ones that review lists, content and volume.
- What complaint rate triggers suspension? Pools that act near 0.1% protect you far better than pools that tolerate 0.5% or more.
- Are pools segmented? Separate pools for transactional, marketing and newer or riskier senders are a good sign.
- Is there independent data? Look for published or third-party inbox placement figures, and check the pool IPs in your own headers against the blacklist checker.
- Is the ESP transparent? Providers that talk openly about blocklist incidents, Postmaster Tools and SNDS data tend to be more disciplined than those that say nothing.
How to run a dedicated IP properly
If you go dedicated, these habits make it work:
- Warm slowly. Follow a four to six week schedule and start with your most engaged subscribers, never your full list.
- Monitor daily during warmup, weekly after. Postmaster Tools, SNDS and blocklist checks belong in a routine.
- Keep a steady cadence. If your natural rhythm is one weekly blast, split it across several days.
- Run tighter hygiene than you would on shared. Suppress hard bounces immediately and sunset inactive subscribers sooner. Every bad send lands on your IP alone.
- Configure branded PTR and verify forward-confirmed reverse DNS.
- Test for drift. Reputation can erode slowly as list quality changes. Monthly placement tests and the sender reputation checker catch drift early.
Migrating between models
Switching in either direction takes planning.
Shared to dedicated. Start warming the dedicated IP while continuing to send the rest of your traffic through the shared pool. Shift volume gradually over four to six weeks, and do not drop the shared route until the dedicated IP is stable. Some providers, including SendGrid and SES, can automate this shift.
Dedicated to shared. This is often harder than it sounds, because you are moving an established sender into an environment you control less. Move a subset of traffic first, compare placement carefully and keep the dedicated IP available as a fallback for a few weeks.
Either way, the basics decide the outcome more than the infrastructure: steady sending, clean lists, low complaints and ongoing monitoring. The IP model only changes how directly those habits show up in your results. For the full set of habits, see the deliverability improvement guide.
Frequently asked questions
How many emails per month do I need before a dedicated IP makes sense?
The usual 100,000 per month figure is a floor, not a trigger. A dedicated IP starts to reliably outperform a good shared pool when you send several hundred thousand emails a month, spread across most days of the week. Below that, how steady your sending is matters more than how much you send, and a reputable shared pool is usually the safer choice.
Does a dedicated IP guarantee better deliverability?
No. It guarantees control over IP reputation, which is different from good reputation. If your list hygiene or engagement is weak, a dedicated IP makes the problem more visible because there is no pool average to hide behind. Domain reputation also carries heavy weight at Gmail and other providers, so a dedicated IP cannot rescue a domain with poor sending history.
Can I use a dedicated IP for cold email?
Technically yes, but it rarely makes sense. Cold email tends to have higher complaint rates and irregular volume, which is the opposite of what a dedicated IP needs. Many reputable ESPs also prohibit unsolicited outreach on their infrastructure entirely. Cold email is better suited to separate domains and tooling built for that workload, kept well away from your main sending domain.
What happens if a bad sender joins my shared IP pool?
At a well-run ESP, complaint and bounce monitoring catches the bad sender quickly, and the account is paused before the pool suffers much. At a poorly run ESP, the damage can last days or weeks. Watch for sudden placement drops you cannot explain, and check the sending IPs in your headers with a blacklist checker to see whether the pool has been listed.
Should I use more than one dedicated IP?
Only when volume or isolation demands it. Multiple IPs make sense at very high volume, often above a couple of million emails a month, or when you want to separate traffic types such as transactional and marketing. At lower volumes, splitting traffic across several IPs thins out the reputation signal on each one without adding real protection.