Most senders should stay on a shared IP. The group that genuinely benefits from a dedicated IP is smaller than the marketing pitch suggests, and the deciding factor is not how important your email feels but how much consistent volume you send. A dedicated IP only earns its keep when you send enough mail, every day, to build and hold your own reputation. Below that line a shared IP borrows the established reputation of a well-run pool, while a dedicated IP mostly buys you a warmup project and a reputation you are too small to maintain.
Reads public DNS only. Nothing is stored unless you save the domain to an account.
What the two models actually mean
A sending IP is the network address your mail leaves from, and mailbox providers like Gmail, Yahoo, and Microsoft track the reputation of that address alongside the reputation of your domain. The IP is one of the signals filters use to decide inbox versus spam.
With a shared IP, your email provider routes many customers through the same pool of addresses. The reputation of that pool is the aggregate of everyone sending through it. With a dedicated IP, one address (or a small set) is assigned to you alone, so the reputation attached to it reflects only your own sending.
Reputation is not only about the IP. Mailbox providers weigh domain reputation heavily too, and the two are distinct signals that can diverge. If you are unclear on how they interact, read domain reputation vs IP reputation before you decide, because the domain side often matters more than the IP for smaller senders.
The core tradeoffs
Four factors decide the choice: volume, reputation control, warmup burden, and cost. They pull in different directions, so weigh them together rather than in isolation.
| Factor | Shared IP | Dedicated IP |
|---|---|---|
| Best volume range | Low to moderate, or irregular | High and consistent, roughly 100,000+ per month |
| Reputation control | Borrowed from the pool | Fully yours, good or bad |
| Warmup burden | None; the pool is already warm | 4 to 8 weeks of gradual ramp |
| Cost | Included in most plans | An add-on, often a monthly fee per IP |
| Isolation from others | None; noisy neighbors affect you | Complete; you are your own neighbor |
| Blast tolerance | Poor; sudden spikes look abnormal | Good once warmed and established |
Volume
Volume is the first filter, and it is about consistency more than raw totals. A dedicated IP needs steady traffic so mailbox providers see a stable, predictable pattern. Common guidance from email service providers puts the practical floor around 100,000 messages per month sent regularly, and some providers, Postmark among them, recommend closer to 300,000 before a dedicated IP reliably outperforms a good shared pool. What matters is the daily rhythm. An IP that goes quiet for days at a time looks abnormal, and the reputation you built decays while it sits idle.
Reputation control
This is the real reason to go dedicated. On a shared pool your fate is tied to the worst-behaved senders in it, and a single spammy neighbor can drag placement down for everyone. A reputable provider polices its pools aggressively to prevent exactly this, which is why shared pools from good providers still perform well. On a dedicated IP there are no neighbors: your reputation is entirely a product of your own list hygiene, engagement, and complaint rate. That control cuts both ways. Send to stale lists or hit a spam trap and there is no pool to dilute the damage.
Warmup burden
A cold dedicated IP has no reputation, and mailbox providers distrust unknown addresses that suddenly send large volumes. You have to warm it up: start with a few hundred messages a day to your most engaged recipients and increase gradually, often by around 20 percent per day, over four to eight weeks until you reach full volume. A shared pool skips this entirely because it is already warm. Warmup is a real project with a real failure mode, so plan it deliberately. Our guide on how to warm up an email domain covers the ramp schedule and the engagement signals to watch.
Cost
Dedicated IPs are almost always a paid add-on, typically a fixed monthly fee per IP on top of your sending plan. The fee itself is modest, but it is only worthwhile if you actually use the capacity. Paying for a dedicated IP and then sending 20,000 messages a month is the worst of both worlds: you pay extra for a reputation you cannot keep warm, and you lose the safety of a pool that was already trusted.
When shared is the right call
Stay on a shared IP if any of these describe you:
- You send under roughly 100,000 messages per month. There is not enough traffic to warm and hold a dedicated IP, so you would trade a warm pool for a cold address.
- Your volume is irregular or seasonal. A retailer that sends heavily in Q4 and goes quiet in the summer will see reputation decay between peaks. The gaps are the problem, not the peaks.
- You send mostly transactional mail at low volume. Password resets and receipts benefit from the pool's established standing, and their steady trickle is rarely enough to warm an IP alone.
- You do not want to run a warmup. If nobody owns deliverability operations, a shared pool from a reputable provider is the safer default.
Shared does not mean second class. A well-managed shared pool from a provider like Postmark, SendGrid, or Amazon SES often delivers better inbox rates for a small sender than a self-managed dedicated IP would.
When dedicated wins
A dedicated IP is the better choice when all of the following hold together:
- High, consistent volume. You reliably send 100,000 or more messages per month, spread across the month rather than in isolated bursts.
- You want full control of your reputation. You are prepared to own list hygiene, complaint rates, and engagement, and you do not want your placement affected by other senders.
- You have the operational maturity to warm and maintain it. Someone monitors bounce and complaint rates and can react when a metric moves.
- You separate mail streams. Large senders often run one IP for transactional mail and another for marketing, so a promotional campaign that draws complaints cannot damage password-reset delivery.
If you meet the volume bar but not the operational one, fix the operations first. A dedicated IP amplifies whatever you feed it, good sending or bad.
How this interacts with the bulk sender rules
Since February 2024, Google and Yahoo classify any domain sending 5,000 or more messages per day to personal accounts as a bulk sender, and Microsoft has aligned with similar expectations for high-volume senders to its consumer inboxes. Bulk senders must authenticate with SPF, DKIM, and DMARC, keep the spam complaint rate below 0.3 percent (Google advises staying under 0.1 percent for reliable placement), and offer one-click unsubscribe per RFC 8058. See the Google and Yahoo sender requirements for the full checklist.
These thresholds bear on the IP decision for two reasons. First, a sender at 5,000 per day to Gmail alone is already in dedicated-IP territory by volume. Second, the complaint-rate ceiling is unforgiving on a dedicated IP, where there is no pool to average out a bad campaign. If you cross the bulk threshold, the IP choice and the compliance work arrive together.
Authentication is a prerequisite for either model. Whichever IP you use, your SPF record must authorize it (mind the ten DNS-lookup limit to avoid a PermError), your DKIM signature must validate with an aligned domain, and DMARC alignment must pass. Start with SPF, DKIM, and DMARC explained if any of that is not solid, because a dedicated IP does nothing for a domain that fails authentication.
A simple decision path
- Are you sending 100,000 or more messages per month? If no, stay shared.
- Is that volume steady across the month, not clustered in a few bursts? If no, stay shared.
- Do you have someone to run warmup and monitor complaint and bounce rates? If no, stay shared or fix that first.
- Do you want to isolate your reputation and separate transactional from marketing streams? If yes to all four, a dedicated IP is likely worth it.
When the answers are mixed, default to shared. The cost of an underused dedicated IP is measured in lost inbox placement, not just the monthly fee.
Frequently asked questions
Does a dedicated IP guarantee better deliverability?
No. A dedicated IP gives you control of your IP reputation, but reputation still has to be earned through good sending. A poorly maintained dedicated IP performs worse than a well-run shared pool, because there is no pool reputation to fall back on.
How long does it take to warm up a dedicated IP?
Plan for four to eight weeks. Start with a few hundred messages a day to your most engaged recipients and increase gradually, often by around 20 percent per day, watching bounce and complaint rates at each step. Rushing the ramp is the most common way to burn a new IP.
Can I switch from shared to dedicated later?
Yes, and that is often the right sequence. Start on a shared pool while your volume grows, then move to a dedicated IP once you consistently clear the volume threshold and have the operations to support warmup. Moving too early is the mistake, not moving late.
Should I get more than one dedicated IP?
Only if your volume justifies it or you are separating mail streams. Large senders split transactional and marketing traffic onto different IPs so complaints on one cannot harm the other. Splitting low volume across multiple IPs just makes each one harder to keep warm.
Before you change anything about your sending setup, confirm your authentication is actually passing. Run a free scan with SPFWise to check your SPF, DKIM, and DMARC in seconds and see exactly what mailbox providers see.