⚖️ In short: I have worked with both services on different projects. SendGrid sent order emails for an online store, and Resend has been sending new articles to my blog subscribers for over a year. There were no problems with either, so this is not a "bad vs good" story, but an analysis of where each is stronger.
📬 Choosing between more than just these two? Start with my review of 7 email sending services: prices, limits, and when to use each — it includes Amazon SES, Postmark, Mailgun, and Brevo.
⚡ Verdict in 30 seconds
- ✅ Resend — if a developer is integrating email, and a simple API, free start, and convenient analytics are important.
- ✅ SendGrid — if you need a mature all-in-one solution: transactional emails, marketing campaigns, dedicated IP, and the Twilio ecosystem.
- 💰 For 50,000 and 100,000 emails, prices are almost the same — the deciding factor is not the price, but the free plan, log history, and ease of use.
- ⚠️ SendGrid no longer has a free plan — only a 60-day trial.
- ⚠️ Resend's free plan is limited to 100 emails per day — for sending to a database, you'll need a paid plan or Broadcasts.
📑 Table of Contents:
🧭 My experience with both services
I integrated SendGrid into an online store: after a purchase, the customer received an email with order details. This is a classic transactional scenario, and SendGrid handled it without problems. However, the service itself is more geared towards e-commerce and businesses with marketing campaigns — for my own tasks, like blog newsletters, it was less suitable for me.
I have been using Resend for over a year to send articles to blog subscribers. I switched to it for three reasons:
- Simple integration — minimal code and setup required before sending the first email.
- Deliverability and reliability — it is critical for me that emails reach their destination and don't end up in spam.
- Favorable free tier at the start.
There is one more thing that makes Resend convenient specifically for a blog: I decide when and which article to send to subscribers. In the store, there is no such freedom — an order email must always be sent immediately, it is unacceptable to miss it. This means the tasks in these projects are fundamentally different.
👉 Important: I am comparing the services not in a single lab test, but based on experience from two different projects plus current tariffs and documentation. The figures below are as of October 2026.
💰 Prices at three volumes
| Volume per month |
Resend |
SendGrid |
| 3,000 emails |
$0 (Free, up to 100 per day) |
60-day trial (100 per day), then from $19.95 |
| 50,000 emails |
$20 (Pro) |
$19.95 (Essentials) |
| 100,000 emails |
$35 (Pro 100K) |
$34.95 (Essentials 100K) |
| Dedicated IP |
$30/mo on Scale plan (from $90) |
1 IP included in Pro (from $89.95) |
At medium volumes, there is practically no difference — 5 cents. The real difference is at small volumes: with Resend, you can stay on the free plan, while with SendGrid, after the trial, you will have to pay at least $19.95 per month, even if you send only 500 emails.
👨💻 API and the first email
The difference is most evident in the code. Here is the same email in Java using official SDKs.
Resend:
Resend resend = new Resend(System.getenv("RESEND_API_KEY"));
CreateEmailOptions params = CreateEmailOptions.builder()
.from("WebCraft <[email protected]>")
.to("[email protected]")
.subject("New blog post")
.html("<p>Hello! A new article has been published...</p>")
.build();
CreateEmailResponse response = resend.emails().send(params);
SendGrid:
Email from = new Email("[email protected]");
Email to = new Email("[email protected]");
Content content = new Content("text/html", "<p>Your order №1024</p>");
Mail mail = new Mail(from, "Order №1024", to, content);
SendGrid sg = new SendGrid(System.getenv("SENDGRID_API_KEY"));
Request request = new Request();
request.setMethod(Method.POST);
request.setEndpoint("mail/send");
request.setBody(mail.build());
Response response = sg.api(request);
Both options work, but Resend reads like "send an email," while SendGrid reads like "build an HTTP request to the API." The difference is small for one email and noticeable when email sending is scattered throughout the project.
I will cover how to correctly integrate both services with Spring Boot — with configuration, retries, and queues — separately in the article Email Sending in Spring Boot: 8 Solutions to Ensure Emails Are Not Lost.
🧩 Templates
- SendGrid — Dynamic Templates. Templates are stored in SendGrid, variables are substituted using Handlebars syntax. There is a visual editor, so a template can be edited by someone other than a developer.
- Resend — Templates and React Email. Templates are also stored in the service, created in a visual editor or via API, support up to 20 variables and versioning. For those who write frontend, there is React Email — templates as React components.
Both options allow sending only the template ID and variables, not the entire HTML. In a Java project without React, a convenient alternative is to keep HTML in a templating engine on your side (e.g., Thymeleaf): then templates live with the code and work with any provider.
📣 Mailings: Broadcasts vs Marketing Campaigns
Both services offer marketing mailings, but they are separate products with separate payments — and different payment models:
- Resend Broadcasts — pay per number of contacts, no limit on the number of emails. Free up to 1,000 contacts, then from $40 per month for 5,000. Resend handles unsubscribes automatically.
- SendGrid Marketing Campaigns — a separate product with its own pricing, with a visual editor, segmentation, A/B testing, and automations. Functionally broader, but it's already a full-fledged marketing platform.
👉 What this means for you: for sending articles to a few hundred subscribers, Resend Broadcasts fits within the free plan. For a store with customer segments and automated email sequences, the more functional SendGrid Marketing Campaigns is suitable.
📊 Logs, Webhooks, and Analytics
Here, in my opinion, is the most noticeable practical difference. When a client writes "the email didn't arrive," you open the sending history — and it's important how far back it goes.
|
Resend |
SendGrid |
| Email History |
about 30 days |
3 days (Essentials), 7 days (Pro), longer — for an additional fee |
| Event Webhooks |
available on all plans |
1 (trial), 2 (Essentials), 5 (Pro) |
| Analytics |
delivery statuses, opens, clicks |
detailed statistics, address validation on Pro |
With Resend, I like how the delivered email analytics are presented — you can immediately see what arrived, what bounced, and who opened it. With SendGrid on Essentials, the history is only stored for 3 days: if a client complains about an email from a week ago, you won't find it anymore.
🛡️ Delivery and IP Addresses
On basic plans, both services send from shared IPs — you share the address reputation with other provider clients. This is fine for most projects.
- SendGrid provides a dedicated IP with automatic "warm-up" on the Pro plan. On Essentials, it cannot be added even for money.
- Resend sells a dedicated IP for $30 per month on the Scale plan.
A dedicated IP only makes sense with stable large volumes: at a few thousand emails per month, it won't have time to build reputation and may deliver worse than a shared one.
⚠️ Limitations and Pitfalls
Resend:
- Free plan — 100 emails per day. You can't send a mailing to 2,000 subscribers via the transactional API at once.
- API limit — a few requests per second, shared by the entire team. For mailings, use the Batch API: up to 100 emails per request.
- Transactional emails and mailings — separate pricing, you need to account for both.
SendGrid:
- No permanent free plan — after 61 days, only paid.
- Short email history on Essentials — 3 days.
- According to reviews, from March 2026, Essentials and Pro have a strict ceiling: no more than 10 times the plan volume per month.
- More complex interface and settings — a price for the breadth of features.
🔄 SendGrid → Resend Migration: Checklist
If you decide to switch, the most important thing is not to lose your domain's reputation. Here's the order I would follow:
- Export blocklists from SendGrid — unsubscribes, bounces, spam complaints. This is the most crucial step: if you skip it, after migrating, emails will go to people who have already unsubscribed, and complaints will flood in.
- Add your domain to Resend and set up new DNS records for SPF and DKIM. Don't delete SendGrid's records yet — both services can run in parallel.
- Migrate templates: SendGrid Handlebars templates will need to be rewritten for Resend Templates or custom HTML.
- Reconfigure webhooks: map SendGrid events (delivered, bounce, spamreport, open, click) to Resend events.
- Gradually shift traffic: start with one type of email, then the rest. Monitor bounces and complaints for the first few days.
- Remove the old: after stable operation, remove SendGrid API keys and its DNS records. DMARC should remain.
🎯 What to Choose
| Scenario |
My Choice |
Why |
| Blog, article newsletter |
Resend |
Free start, Broadcasts up to 1,000 contacts, convenient analytics |
| Transactional emails in a small application |
Resend |
Simple API, free 3,000 emails per month |
| Online store with marketing campaigns |
SendGrid |
Transactional emails and campaigns with segmentation in one platform |
| High volumes with own IP |
SendGrid Pro |
Dedicated IP with automatic warm-up is included in the plan |
| Project already on Twilio (SMS, calls) |
SendGrid |
One ecosystem and one billing |
For a broader comparison with Amazon SES, Postmark, Mailgun, and Brevo, see my article Email Sending Services: Comparison of 7 Providers.
❓ FAQ
Which is cheaper — Resend or SendGrid?
For 50,000 and 100,000 emails per month, the prices are almost the same: $20 vs $19.95 and $35 vs $34.95. The difference is in small volumes: Resend is free up to 3,000 emails, while SendGrid costs a minimum of $19.95 after a 60-day trial.
Does SendGrid have a free plan?
Not a permanent one. From 2025, new accounts receive a 60-day trial of 100 emails per day, after which a paid plan is required.
Can I send articles via Resend for free?
Yes, through Broadcasts — up to 1,000 contacts without a limit on the number of emails. Through the transactional API on the free plan — no more than 100 emails per day.
Where is the history of sent emails stored longer?
In Resend — about 30 days. In SendGrid — 3 days on Essentials and 7 days on Pro; longer history is at an additional cost.
Is it difficult to switch from SendGrid to Resend?
Technically, no: new API, DNS records, and templates. The main thing is to transfer unsubscribe and bounce lists to avoid damaging your domain's reputation.
✅ Conclusions
- Both services are good — it's just a matter of the task. SendGrid reliably sent orders in my store, and Resend sends blog articles.
- Prices for medium volumes are almost the same — the free plan, log history, and API convenience are deciding factors.
- Resend is simpler and more convenient for developers, with a free start and longer email history.
- SendGrid is more feature-rich, with marketing campaigns and a dedicated IP on Pro.
- During migration, the most important thing is to transfer unsubscribe and bounce lists.
📚 Sources