SendGrid pricing: Essentials from $19.95, Pro from $89.95, and a trial that ends

Read the table as two plans, not one ladder

The selector's range text says Essentials covers 50,000 to 100,000 emails a month, Pro covers 100,000 to 2,500,000, and Premier starts above 2,500,000 at custom pricing. So the two plans overlap in exactly one place, 100,000 emails, and that is where the gap is easiest to see: $34.95 on Essentials against $89.95 on Pro, a difference of $55 a month for the same volume. Whether that $55 is worth paying depends on the features that come with it, not on volume, which is why most of this page is about them. The page's own summary is blunt about it: exact pricing depends on email volume and features, and Pro and Premier include dedicated IPs, with the option to buy more.

Pro's per-thousand cost is highest at its entry point, about $0.90 at 100,000, and falls to about $0.44 at 2,500,000. A team just over the Essentials ceiling therefore pays a visible premium for moving up, while one at 1,500,000 emails is paying less per email than an Essentials customer does at 50,000. The page adds that taxes and overages may apply, and its FAQ says that if you regularly push past your limit, upgrading to the next tier usually beats paying overages. It does not publish an overage rate in the text I read, so I give no estimate for a month that lands between two selector stops.

What Pro adds, row by row

The feature comparison on the same page separates the plans along a few lines that affect real teams more than the price does.

Notice how little of that is about sending capacity. A single teammate on Essentials means one person logs into the dashboard, which matters if a marketer wants to adjust a template while a developer owns the API key. Two event webhooks versus five decides how many separate systems can listen for bounces and opens. Three days of searchable activity on Essentials is short if a customer writes in a week after a send; the page lists extra activity history as something you can buy. Pro also lists email content testing at 60 credits a month, with more for purchase.

Marketing Campaigns: a second price list

SendGrid sells campaign sending as a separate product, and its prices follow contacts rather than emails. The free plan stores up to 2,000 contacts and sends 6,000 emails a month. The paid selector readouts from the Marketing Campaigns pricing page are below.

If you buy both products, the list prices simply stack: 50,000 transactional emails on Essentials at $19.95 plus a 10,000-contact newsletter on Basic at $25 comes to $44.95, though neither page says whether Twilio invoices them together. The practical point is that a team using an assistant to write weekly campaigns and an API for receipts has two meters to watch, one by contact count and one by emails.

The free offers need careful reading. The Email API trial is stated as $0 a month for 60 days. The Marketing Campaigns page uses the same "Free Trial, $0 a month for 60 days" label in its plan row, and separately says it also offers a Free Marketing Campaigns Plan for 2,000 contacts and 6,000 emails a month. I cannot tell from those lines how the two relate, and the Email API text I read does not say what happens after day 60 beyond the option to upgrade, so confirm the terms with Twilio before you build a production sender on a trial.

From assistant draft to Mail Send payload

Say a writer produces an order-update email in MailMaestro or a chatbot and a developer wants it sent through the API. The Mail Send reference describes one endpoint, v3/mail/send, whose personalizations array accepts up to 1,000 items. Each item acts like an envelope with its own recipients. A template_id starting with d- selects a dynamic template, and dynamic_template_data supplies the values, up to 10,000 properties. The same page says send_at can schedule a message but not more than 72 hours ahead, and that a batch_id lets you cancel or pause a batch. I found no idempotency key described on that page, so duplicate protection after a retry is your own job.

The dynamic templates guide explains how to build the template side. You create a template, add a version in either the Design Editor or the Code Editor, give the version a subject and optional preheader, and mark one version active. Personalization uses Handlebars in the text, HTML and subject. The guide's own examples are short:

{{#if name}}
<div>Hello {{name}}!</div>
{{/if}}

That conditional renders the greeting only when the data contains a name. The same guide shows a loop for line items in a receipt and a template ID that is d- followed by 62 hexadecimal characters, and it points to a GitHub repository of sample templates for receipts, password resets, account activations, newsletters and sale notifications. For an assistant-drafted message, the safe route is to paste approved copy into the Code Editor, replace the personal details with Handlebars variables, and send test data before the real list. The guide also tells you to drag in an Unsubscribe module and pick an unsubscribe group, which a promotional draft needs.

If you would rather not use templates, the Mail Send page offers a substitutions property, but it says not to combine it with a dynamic template.

What the vendor says about AI

The Email API pricing page lists no feature that drafts or rewrites email content. Its feature tables name dynamic templates, email content testing, deliverability insights and similar items. The page does carry an AI assistant widget that helps visitors pick a plan, and a disclaimer that a product recommendation tool is powered by a hybrid system of Twilio and OpenAI and may produce inaccurate information. Both are aimed at choosing Twilio products, not at writing your email. On the docs side, the dynamic templates guide has a page-tools menu that offers to copy the page as markdown and open it in ChatGPT, Claude, Cursor or Perplexity, plus a "Build with AI" menu with options to connect an AI agent and install Twilio Skills. Those help developers use the documentation with an assistant; they are not email-writing features.

Who should choose SendGrid

It fits teams that want transactional and campaign email from one vendor, and teams that need Pro-level controls such as subusers and SSO for several brands or clients. Essentials at $19.95 for 50,000 emails is a modest entry if one developer does everything.

It fits less well if you want a free tier that never expires for API sending; Postmark lists a free plan of 100 emails a month that does not expire, and Mailgun lists a Free plan of 100 emails a day with no end date stated. If you mostly want per-email pricing without feature tiers, compare Resend. For list-based campaign tools, the Brevo guide is the closer sibling, and the pricing index shows the other vendors side by side.

FAQ