Dedicated IP vs shared IP for email marketing

The conventional wisdom is that dedicated IPs are the professional choice and shared IPs are for beginners. That framing gets the decision wrong for most senders. The right choice depends on your sending volume, consistency, and how much operational attention you want to spend on IP reputation management.

This guide explains what each option actually means in practice, what moves the needle for deliverability, and when dedicated IPs genuinely make sense versus when they make things harder.

What shared and dedicated IPs actually are

When you send email through a provider like Amazon SES, SendGrid, or Mailgun, your messages leave from an IP address. That IP address has a reputation with inbox providers -- Gmail, Microsoft, Yahoo -- built from the sending history associated with it.

Shared IPs mean multiple senders use the same IP address pool. Your reputation is averaged with other senders on the pool. A well-managed shared pool from a reputable provider maintains healthy sending patterns and is actively monitored for abuse. Most email volume in the world leaves from shared IPs.

Dedicated IPs mean you get one or more IP addresses used exclusively by your account. Your reputation on those IPs is entirely determined by your own sending behavior. Nobody else can affect it -- but nobody else's good behavior helps it either.

Why dedicated IPs are not automatically better

The appeal of dedicated IPs is obvious: you control your own reputation. If something goes wrong, it is your fault and your problem to fix. If everything goes right, the benefit is yours alone.

The problem is that IP reputation requires volume to build and maintain. Inbox providers learn about an IP's trustworthiness by observing its sending patterns over time. An IP that sends consistently, at meaningful volume, with good engagement signals builds a strong reputation. An IP that sits idle for weeks and then sends a burst looks suspicious -- because that pattern matches how spammers operate.

This creates a trap that catches a lot of senders: they pay for a dedicated IP because they want better deliverability, but their volume is too low to build any reputation on it, so their deliverability gets worse, not better.

What actually determines deliverability

The factors that move inbox placement for most senders, in rough order of importance:

Domain reputation

Gmail, Microsoft, and Yahoo have shifted significant weight toward the domain in your From address and the domain your DKIM signature covers. A clean sending domain with proper authentication and good engagement history performs well regardless of which IP pool it uses. A domain with a history of complaints performs poorly on dedicated IPs just as much as shared ones.

Authentication

SPF, DKIM, and DMARC alignment are table stakes. Without them, IP reputation is mostly irrelevant -- major providers will filter or reject your mail regardless. With them correctly configured, your domain reputation starts accumulating. This is the single highest-return thing most senders can do for deliverability and it has nothing to do with IP type.

List quality and engagement

Inbox providers measure what happens after your email arrives. High open rates, low spam complaints, low unsubscribes -- these signals tell providers that recipients want your mail. A permission-based list of engaged subscribers delivers well on shared IPs. A scraped or purchased list delivers poorly on dedicated IPs. The list is more important than the IP.

Bounce and complaint management

Hard bounces that are not suppressed and complaints that accumulate damage reputation fast on any infrastructure. Processing these correctly -- automatically suppressing hard bounces, monitoring complaint rates -- matters far more than whether you have a dedicated IP.

Sending consistency

Erratic sending patterns -- quiet for a month, then a large burst -- look like abuse to inbox providers. Consistent sending at predictable volume builds reputation steadily. This applies to dedicated IPs especially: an inconsistent sending pattern on a dedicated IP builds no reputation, and the IP looks cold every time you resume.

When dedicated IPs genuinely make sense

Dedicated IPs are the right choice when:

• You send at sustained volume. A rough minimum is 50,000 to 100,000 emails per month, sent consistently. Daily sending at this volume gives inbox providers enough signal to build a meaningful reputation on your IP. Below this, shared pools typically outperform.
• You want to isolate sending streams. Separating transactional email (password resets, receipts) from marketing campaigns on different IPs prevents a bad marketing run from affecting transactional deliverability. This is legitimate -- but it requires sufficient volume on each stream to maintain reputation on each IP.
• Your sending program is mature and healthy. Dedicated IPs amplify your existing reputation. If your engagement metrics are strong, your lists are clean, and your authentication is correct, a dedicated IP lets that good reputation compound on infrastructure that belongs entirely to you. If any of those things are shaky, a dedicated IP amplifies the problems too.
• You are migrating from another provider. Moving a high-volume sending program to new infrastructure requires a warmup period regardless. Starting on dedicated IPs and warming them deliberately is a legitimate approach when you have the volume to do it correctly.

When shared IPs are the right choice

Shared IPs from a reputable provider are the right choice when:

• Your monthly sending volume is under 100,000 emails
• Your sending is irregular -- seasonal spikes, occasional campaigns
• You are building a new sending program and volume is still growing
• You want consistent deliverability without the operational overhead of warmup and reputation monitoring
• You are sending from Amazon SES and do not yet have the volume to maintain a dedicated IP reputation

The warmup requirement for dedicated IPs

A new dedicated IP has no reputation. You cannot start sending your full volume on day one. Inbox providers need to see a gradual ramp from small sends to full volume over several weeks before they trust the IP with large quantities of mail.

A typical warmup schedule starts at a few hundred emails per day in week one, doubles roughly every week, and reaches full volume after four to eight weeks depending on total volume. During warmup, you monitor bounce rates, spam complaint rates, and inbox placement closely and slow down if signals deteriorate.

This is real operational work. For a team with someone focused on deliverability, it is manageable. For a small operation where email is not the primary focus, it is often more overhead than the benefit justifies.

The comparison most guides skip

The practical recommendation

Start on shared IPs. Focus on the things that actually drive deliverability: domain authentication, list quality, bounce suppression, and consistent sending. Build engagement with your subscribers. If your program grows to 100,000+ monthly emails sent consistently, evaluate whether dedicated IPs make sense at that point.

The deliverability gains from dedicated IPs at high volume are real. The deliverability losses from dedicated IPs at low volume are also real. The warmup overhead is real at any volume. Start with what works without operational complexity and graduate to dedicated IPs when the volume genuinely justifies them.