How long does warming up take?

Typically two to six weeks depending on target volume. Reaching tens of thousands of messages a day takes longer than reaching a few hundred; the ramp length scales with the destination, not with impatience.

Can I skip warm-up on a dedicated IP?

No. A dedicated IP has no reputation at all, so sending at volume immediately is the worst case. Shared pools borrow the provider's existing reputation, which is why they tolerate faster starts.

Do automated warm-up services work?

They generate synthetic engagement between cooperating inboxes, which providers increasingly detect and discount. Real engagement from real recipients is the only durable signal.

What complaint rate is acceptable?

Below 0.1% is healthy. Above 0.3% triggers filtering and possible blocking at major providers, and recovery takes considerably longer than the original ramp.

TLS & Email🔒 Browser (client-side)API available📴 Works offlineintermediate

Email Warmup Scheduler

Calculates automated 14-day and 30-day domain sending warmup schedules, daily caps, and ramp speeds for new email domains.

Data stays in your browser

Ready to runInstant execution

All tools →

Result

—

What does this tool do?

Calculates automated 14-day and 30-day domain sending warmup schedules, daily caps, and ramp speeds for new email domains.

Why would I use it?

You are launching a new sending domain and need to build inbox reputation with Gmail, Yahoo, and Outlook.
You want to avoid hitting daily volume spikes that trigger spam filters or IP throttling.
You need a proven, step-by-step daily sending plan for marketing or transactional mail.

Real-life example

Input

Target Volume: 50,000 emails/day, Plan: 30 days, Speed: Standard

Output

Day 1: 50 sends (4/hr) → Day 15: 1,580 sends → Day 30: 50,000 sends (4,166/hr)

Includes hourly caps, dispatch delays, and 0.08% complaint circuit-breakers.

Input → Process → Output → Next

Input: Enter your target daily email volume, ramp duration (14 or 30 days), and speed.
Process: Computes geometric growth curves and hourly throttle recommendations.
Output: Day-by-day table showing daily cap, hourly rate, and cumulative volume.
Next action: Configure your email queue or ESP rate limits according to the schedule.

Common mistakes

Sending 50,000 emails on Day 1 on a brand-new domain (guarantees spam folder placement).
Ignoring bounce rates (stop sending if hard bounce rate exceeds 2.0%).
Not configuring SPF, DKIM, and DMARC before starting the warmup process.

What the result means

A statistically safe volume trajectory to establish sender reputation with mailbox algorithms.

Privacy & security

Your input is processed entirely in your browser and never sent to a YAS server.

API

Endpoint

POST https://yas.sh/api/v1/tools/email-warmup-calculator

Request Header

Content-Type: application/json

cURL

curl -X POST "https://yas.sh/api/v1/tools/email-warmup-calculator" \
  -H "Content-Type: application/json" \
  -d '{"targetDailyVolume":50000,"days":30,"speed":"standard"}'

JavaScript

const res = await fetch("https://yas.sh/api/v1/tools/email-warmup-calculator", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "targetDailyVolume": 50000,
  "days": 30,
  "speed": "standard"
}),
});
const data = await res.json();

Python

import requests

r = requests.post("https://yas.sh/api/v1/tools/email-warmup-calculator", json={"targetDailyVolume":50000,"days":30,"speed":"standard"})
data = r.json()

Field	Type	Required	Description
targetDailyVolume	integer	No (default 50000)	Target daily volume
days	integer	No (default 30)	Duration: 14 or 30 days
speed	string	No (default standard)	conservative, standard, aggressive

Success response

{ "slug": "email-warmup-calculator", "totalDays": 30, "targetDailyVolume": 50000 }

Calculate automated 14-day and 30-day domain sending warmup schedules.

Error responses

400 VALIDATION_ERROR — invalid input or unsupported option.
413 PAYLOAD_TOO_LARGE — input exceeds the 64 KB limit.
429 RATE_LIMIT_EXCEEDED — rate limit exceeded (60 req/min).

Limits

Maximum input: 64 KB per request.
Rate limit: 60 requests/min per IP address.
Authenticated accounts benefit from higher tier quotas.

How Email Warmup Scheduler works

Mailbox providers build reputation per sending domain and per IP, and a new sender has none. Warm-up ramps volume gradually so that positive engagement signals — opens, replies, messages moved out of spam — accumulate faster than negative ones. The calculator produces a daily schedule, typically starting in the tens of messages and increasing by a fixed percentage per day, with the ramp length set by the target daily volume.

The schedule is scaffolding, not the mechanism. Reputation is earned by recipient behaviour: providers weigh opens, replies, deletions without reading, and spam complaints. Sending the correct daily number to a disengaged list builds a negative reputation on exactly the schedule you planned, which is why warm-up must start with your most engaged recipients.

When to use it: real-world scenarios

Launching a new sending domain

A domain with no history sending at full volume on day one is treated as suspicious by every major provider. A ramp establishes a baseline they can evaluate.

Migrating between email service providers

Reputation attaches to the sending IP and domain, not to your list. Moving providers means starting the ramp again on the new infrastructure.

Recovering after a deliverability incident

Following a spam-trap hit or complaint spike, reducing volume and rebuilding with engaged recipients is the standard remediation path.

Adding a dedicated IP

Moving from a shared pool to a dedicated address means inheriting no reputation at all — the ramp is mandatory, not advisory.

Pro tips

Get SPF, DKIM, DMARC and reverse DNS correct before day one. Warming an unauthenticated domain builds reputation for a sender that providers already distrust.
Send to your most engaged recipients first. Early opens and replies are the strongest positive signals available.
Keep the daily volume steady rather than spiky. Irregular sending patterns look automated in the way providers penalise.
Monitor complaint rate and keep it below 0.1%; above 0.3% providers will act regardless of how careful the ramp was.

Limitations and edge cases

What this tool deliberately does not do, and where it will disagree with other implementations.

The schedule is a heuristic. No provider publishes its thresholds, and each weighs signals differently.
Warm-up cannot compensate for a purchased or stale list — it accelerates the damage instead.
Reputation attaches to both domain and IP; changing either resets part of the progress.
Automated warm-up services that exchange mail between fake inboxes generate artificial engagement and are increasingly detected and penalised.

Frequently asked questions

How long does warming up take?: Typically two to six weeks depending on target volume. Reaching tens of thousands of messages a day takes longer than reaching a few hundred; the ramp length scales with the destination, not with impatience.
Can I skip warm-up on a dedicated IP?: No. A dedicated IP has no reputation at all, so sending at volume immediately is the worst case. Shared pools borrow the provider's existing reputation, which is why they tolerate faster starts.
Do automated warm-up services work?: They generate synthetic engagement between cooperating inboxes, which providers increasingly detect and discount. Real engagement from real recipients is the only durable signal.
What complaint rate is acceptable?: Below 0.1% is healthy. Above 0.3% triggers filtering and possible blocking at major providers, and recovery takes considerably longer than the original ramp.