Resend Pricing in 2026: The $20 to $90 Jump & Volume Math
Resend pricing in 2026 broken down with real volume math — why the jump from 50k ($20) to 100k ($90) plus $0.90/1k overage hits growing SaaS apps hard.
On this page · 9 sections
Overview
Resend earned its reputation for a reason: great documentation, React Email, official SDKs in every language, and a permanent free tier of 3,000 emails/month (100/day) with no credit card required. For an early-stage app, it is one of the smoothest onboarding flows in developer tools.
The surprise only arrives once your app grows past 50,000 emails a month — or has a single noisy month from a product launch, annual renewal wave, or digest burst. That is where Resend's pricing jumps 4.5× in one step, from $20/mo to $90/mo, with $0.90 per extra 1,000 emails on overage. Here is the exact cost math as read on Resend's public pricing page on 2026-11-17, including how non-expiring email packs handle burst months without a forced plan upgrade.
Resend pricing tiers (read on 2026-11-17)
**Free ($0/mo — 3,000 emails/mo, 100/day cap).** Ideal for prototypes, personal projects, and staging. Note the 100/day cap: a single spike of 150 verification emails on launch day hits the daily ceiling long before you reach 3,000 for the month.
**Pro ($20/mo — 50,000 emails/mo, no daily limit).** For apps sitting comfortably between 5,000 and 50,000 emails/month, $20/mo is straightforward and buys you Resend's full DX ecosystem. Cross 50,000 and overage runs at **$0.90 per extra 1,000 emails**.
**Scale ($90/mo — 100,000 emails/mo).** Doubling your monthly allowance from 50k to 100k multiplies the base subscription by **4.5×** ($20 → $90). Even if you stay on Pro and absorb 80,000 emails via overage, 30,000 extra emails at $0.90/1k add $27 on top of $20 ($47 total) — and once you cross ~128k or need Scale features, the recurring $90/mo baseline sticks even in quiet months.
| Scenario / Monthly Volume | Resend (Nov 2026) | Mailbase (Yearly / Monthly) | Amazon SES (Raw AWS) |
|---|---|---|---|
| Up to 3,000 / mo (100/day) | $0 (no card needed) | €0 (card verified, own domain) | ~$0.30–$0.48 |
| 50,000 / mo steady | $20/mo (Pro) | €9/mo (€12 monthly, Starter) | ~$5–$8/mo + DIY stack |
| 60,000 / mo (50k + 10k burst) | $29 ($20 + $9 overage) or $90 Scale | €9 + €7.50 non-expiring 10,000 pack | ~$6–$9.60/mo |
| 100,000 / mo steady | $90/mo (Scale) | €29/mo (€39 monthly, Growth) | ~$10–$16/mo + DIY stack |
| 300,000 / mo steady | Custom / overage ($270+ at $0.90/1k) | €79/mo (€107 monthly, Scale) | ~$30–$48/mo + DIY stack |
Why burst months matter more than steady-state tiers
Real SaaS email volume is rarely flat. A B2B product might send 38,000 emails in August, then jump to 62,000 in September because of quarterly invoices, a waitlist invite wave, or a password-reset spike. On fixed-tier subscriptions, you either pay $0.90 per 1,000 overage every time you spill over, or you upgrade to a $90/mo tier and forget to downgrade in October.
That is why Mailbase pairs low monthly tiers (Starter €9/mo yearly for 50,000, Growth €29/mo for 100,000, Scale €79/mo for 300,000) with a **€7.50 pack of 10,000 emails that never expires**. If you only cross 50,000 emails twice a year, you buy a pack, burn 4,000 credits this month, and keep the remaining 6,000 credits for the next spike — no plan upgrade, no recurring jump, and €0.75 per 1,000 emails instead of $0.90.
When Resend is still worth paying for — and when to switch
**Stay on Resend** if you send under 3,000 emails/month without wanting card verification, rely heavily on its official multi-language SDKs or SMTP relay, or have React Email templates deeply wired into its dashboard. At $20/mo for 40k emails, the developer ergonomics easily pay for themselves.
**Switch** when your volume crosses 50k–100k/month and you are paying $90/mo+ mainly for a JSON POST wrapper over Amazon SES. Mailbase runs on Amazon SES in eu-west-1 (Ireland), exposes one clean endpoint (POST /api/v1/send with transactional: true, Idempotency-Key, and signed delivery/bounce webhooks), and keeps your monthly bill flat as you scale. See the side-by-side migration guide on Resend alternative or read the transactional email API overview.
Common mistakes
- Sending product-critical mail and marketing from the same domain/reputation.
- Skipping idempotency, so retries create duplicate sends.
- Ignoring bounce and complaint webhooks until suppression breaks.
- Treating an email API as “fire and forget” with no event logging.
Sources and further reading
Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.
Related guides
More on resend pricing and the surrounding transactional email workflow: