Comparison
Both plugins fix the same problem the same way: they route WordPress email through an authenticated provider. The difference is the model. Every claim about WP Mail SMTP below comes from their own listing, pricing page or documentation, checked on 30 July 2026 and linked at the bottom.
01 · Common ground
A comparison that opens with the differences is hiding something. These points are settled and equal, and none of them should decide your choice.
02 · The split
Not the quality of either codebase: the decision of what sits in the free plugin and what sits behind a licence.
WP Mail SMTP is the free tier of a commercial product. The features that tell you whether your email actually works, the email log, the failure alerts, the resend button, and the Amazon SES, Microsoft 365 and Zoho mailers, are in the paid version, from $49 to $399 a year depending on the licence. That is a legitimate business, run well, at very large scale.
Custom SMTP has one version. The log, the alerts, the resend, the notification switches and the Amazon SES support are all in the free plugin, and there is no paid edition for them to move to. The trade-off is honest too: a solo maintainer, a smaller install base, and no add-on catalogue.
03 · Side by side
“Pro” means WP Mail SMTP’s paid licence, from $49 a year. Sources for every row are at the bottom of the page.
| WP Mail SMTP | Custom SMTP | |
|---|---|---|
| Send through your SMTP provider | Free, 12 mailers | Free, 12 presets + any SMTP server |
| Amazon SES | Pro | Free, API with IAM role, no stored keys |
| Outlook / Microsoft 365 | Pro, via the Microsoft API | Free preset, via SMTP |
| Zoho Mail | Pro | Free preset |
| Email log, preview, resend, CSV export | Pro | Free |
| Failure & volume alerts | Pro · email, Slack, Teams, Discord, SMS, webhook | Free · email, webhook, admin notice |
| WordPress notification switches | Pro, “Email Controls” | Free |
| Open & click tracking | Pro | Not offered, by design |
| Backup connection, routing, rate limiting | Pro | Not offered |
| Setup wizard, migration from other plugins | Free | No wizard: presets fill the settings |
| Settings locked in code | PHP constants | PHP constants and environment variables, every setting |
| Price | Free, then $49 to $399 / year | Free, no paid version |
One nuance worth knowing on Outlook: our preset uses SMTP authentication, which Microsoft is retiring in stages for Exchange Online; their Pro mailer uses the Microsoft API and is not affected. The Outlook guide documents the timeline and what it means for a small site.
04 · Credit where due
An honest comparison has this section, and not as a formality. If these points decide it for you, take their plugin.
05 · The other side
The same standard applies in this direction: each point is verifiable, in the code or on the screen.
06 · The short version
Two sentences each, no hedging.
Take WP Mail SMTP if you want open and click tracking, backup connections and routing, a proprietary API mailer like SendLayer or SparkPost, or a vendor with a support contract behind it, and the licence cost is fine. The free version will route your mail, but the features that answer “did it arrive?” are paid.
Take Custom SMTP if you want the sending, the log, the alerts and the switches complete and free, Amazon SES without stored keys, configuration that lives in code, and a plugin that sends nothing anywhere except your email. That is the whole offer, and it stays free.
Install, pick your provider from the preset list, send yourself a test. The twelve guides carry the exact values, provider by provider.
Same method, same standard: against FluentSMTP and against Post SMTP, every claim sourced on their own pages and dated.
Sources, all checked on 30 July 2026: the WP Mail SMTP listing on WordPress.org (installations, reviews, free mailers, Pro feature list), their pricing page (licences from $49 to $399 a year, feature gating), their constants documentation and their Email Controls documentation (“You will need the WP Mail SMTP Pro license to unlock the Email Controls option”). Facts about Custom SMTP are verifiable in its public code. Found something outdated? Say so on the support forum and this page gets fixed.