How to Set Up SendGrid SMTP on WordPress (2026 Guide)

WordPress sends email through your hosting provider's mail server by default. Most of those emails land in spam, get throttled, or never arrive. SendGrid SMTP fixes that.

Here is the exact 5-step setup I run for every WordPress client. It takes about fifteen minutes and works for newsletters, contact forms, WooCommerce confirmations, and password resets.

Step 1: Create a SendGrid Account

Go to SendGrid and sign up. Their free tier handles 100 emails a day, which covers most small business sites for the first six months. Paid plans start around $20 a month if you need more volume.

The signup flow asks about email volume and use case. Be honest about your numbers. SendGrid's free tier flags inflated volume claims and slows account approval.

Step 2: Generate an API Key

Once your account is verified, generate the API key WordPress will use to authenticate.

Inside SendGrid, go to Settings > API Keys > Create API Key. Name it something obvious like "WordPress SMTP - sitename." Set permissions to "Full Access" for the initial setup. You can narrow them later once everything is working.

Copy the key the moment SendGrid shows it. You only see it once. If you miss it, delete the key and generate a new one.

Step 3: Install a WordPress SMTP Plugin

WP Mail SMTP by WPForms is the standard choice. SendGrid's own plugin works too but has fewer integrations.

In your WordPress admin, go to Plugins > Add New > Search "WP Mail SMTP". Install and activate.

In the plugin settings, set the Mailer to "SendGrid". Paste your API key in the SendGrid API Key field. Set your "From Email" to an email address on a domain you control. Save.

Step 4: Authenticate Your Sending Domain

This is the step most people skip, and it is the difference between "occasionally lands in inbox" and "lands in inbox every time."

Inside SendGrid, go to Settings > Sender Authentication > Authenticate Your Domain. Pick your DNS provider from the list. SendGrid generates a handful of DNS records.

Add those records to your domain's DNS. If you use Cloudflare, GoDaddy, Namecheap, or Vercel, the steps are similar: log in, find the DNS records section, add the new entries from SendGrid as CNAMEs.

Wait 5 to 15 minutes for DNS propagation, then return to SendGrid and click "Verify." Once the records show green, your domain is authenticated.

Step 5: Send a Test Email

Inside WP Mail SMTP, go to the "Email Test" tab. Send a test email to an inbox you can check.

Look for the email to arrive in the inbox. If it landed in spam, something in the setup is still wrong. Check the email headers (in Gmail: "Show original") for "spf=pass" and "dkim=pass." If you see "softfail" or "fail," your domain authentication did not complete. Go back to step 4.

A Few Alternatives Worth Knowing About

SendGrid is the default for a reason. A few other transactional email providers are worth considering depending on your situation.

Amazon SES is the cheapest option at scale. About $0.10 per thousand emails. The catch: setup is more technical, deliverability is good but not best-in-class out of the box, and you need to request "out of sandbox" mode before you can send to addresses outside your test domain.

Postmark has the best deliverability reputation in the industry. The downside is no free tier. Pricing starts at $15 a month for 10,000 emails.

Resend is the newer entrant. Clean API, good developer experience, free tier covers 100 emails a day. Good fit if you also have a Next.js or other modern stack project on the same domain.

For most WordPress clients I work with, SendGrid is still the right call. The free tier handles initial volume, the WordPress plugin is mature, and once your domain is authenticated, deliverability is reliable.

If you build WordPress sites for clients, set this up on every new project before launch. It is a fifteen minute job that prevents a thousand "I never got the email" support tickets.