Free SMTP for WordPress: check the busiest day

A WordPress SMTP plugin connects your site to a mail delivery service; installing the plugin alone does not give you a sending account. If your site needs to send password resets, account notices and form messages at no subscription cost, compare the service’s limits first, then choose a connector it documents. For the workload below, only SendPulse’s published free daily allowance covers a 350-message day. Its 50-message hourly limit still means you cannot send all 350 at once. Brevo, SMTP2GO and Resend each have a lower free daily cap.

This comparison uses public provider terms checked on October 4, 2026. It addresses operational email created by WordPress or its plugins, rather than a newsletter to a marketing list. A plan that fits today’s count still needs a working sender identity, an approved account where required, and a tested path for the particular WordPress messages you rely on.

First separate the connector from the delivery service

WordPress and installed plugins create messages: a password-reset link, a contact-form notification, an order update. A mail connector then takes the message from WordPress and submits it to a provider. The provider accepts or rejects the submission and attempts delivery. Those are separate jobs even when one provider supplies both its own WordPress plugin and the mail service behind it.

For example, Post SMTP’s WordPress.org listing describes a plugin that connects WordPress to several SMTP or API mailers. It does not grant a free allowance with every one of those providers. SMTP2GO’s own plugin documentation says its plugin replaces WordPress’s normal mail route and sends through SMTP2GO’s servers; an SMTP2GO account remains necessary. The useful question is therefore not simply “Which plugin is free?” It is “Which provider and connector together can send my site’s real workload?”

An SMTP connector usually asks for a server, port and credentials. A provider-specific plugin may instead connect through an API key while still solving the same WordPress mail-routing problem. Brevo’s official plugin is one such route: its setup guide asks for an API v3 account key and describes its transactional mail setting. That does not make the plugin itself a separate email allowance. The Brevo WordPress setup guide covers that particular connection in more detail; this page compares provider capacity.

Use the busiest day to test the free tier

Suppose a small site expects 500 intended operational emails in one month, including a launch or account event that puts 350 on one day. The other 150 are spread across the rest of the month. A form may also produce a 50-message hour during that busy day. Count intended recipient messages, not merely WordPress events: a form submission that notifies two staff addresses creates two intended deliveries. This is a planning example, so replace the numbers with your site’s event history and calendar.

The table does not identify a universal winner. A site with no day above 100 might find Resend’s cap adequate; one that depends on a password reset arriving promptly during a 350-message day cannot select a service from monthly totals alone. SMTP2GO explicitly says excess daily messages are queued and delivered as its quota permits, while attempts after its monthly cap are rejected rather than held for the next month. Those two behaviors have different consequences for an account-recovery email. For the other providers, check the live account’s response when its limit is reached before assuming messages will wait or retry.

The optional 50-message hour is a second constraint. SendPulse’s free SMTP limit is 50 per hour, so an hour with exactly 50 leaves no room in that hour for a test, another form notification or a retry. A 350-message day can fit its 400/day allowance and still be delayed by an uneven hourly pattern. SMTP2GO’s Free-plan help adds a 25-per-hour account limit if no sender domain is verified. Confirming only a single sender address does not remove that stated condition, so it would constrain even the modeled 50-message hour. SendPulse’s limit page also specifies a 1 MB maximum message size on the free service and two authenticated domains. An attachment-heavy form notification or several unrelated sites may change the decision before the send count does.

If 350 operational messages really must leave within one hour, none of the documented free allowances in this table establishes that requirement. SendPulse’s hourly cap is too low; the other three publish daily caps below 350. That is the point to price a suitable paid tier or redesign the event schedule, with the sender’s acceptable delay stated explicitly. It would be a mistake to present a daily total as a speed commitment.

What each WordPress path actually requires

Brevo has an official WordPress plugin path for mail generated by WordPress. Its account connection uses an API v3 key, while the plugin’s transactional option routes the mail through Brevo. The Free plan includes transactional email in its stated features and 300 daily sends, with unused daily capacity not carried forward. Before moving password resets to it, confirm the account’s transactional sending state and the sender address or domain. The existing Brevo guide explains why an API key for the plugin and an SMTP credential for a manually configured mailer are not interchangeable.

SMTP2GO provides a WordPress plugin as well as the sending service. Its Free-plan arithmetic is simple for a quiet site: 500 intended messages are below 1,000/month. The 200/day cap is the practical obstacle in this example, and the conditional 25/hour limit matters if the sender domain remains unverified. Its Free-plan help describes five days of Activity reporting for free accounts, another detail to consider when an intermittent message failure is reported a week later. SMTP2GO’s sender guide gives separate routes for a verified domain and a confirmed individual address. A plugin connection alone completes neither.

SendPulse documents a WordPress route through SMTP settings in common mail plugins. Its instructions show where to obtain the SMTP server address, port, login and password, and say the account profile must be approved before those SMTP settings are available. This is the most relevant free allowance for the model’s 350-message day, provided the hour-by-hour pattern works. Its US transactional pricing calls the free tier Basic and lists 12,000 monthly emails; the SMTP limits impose 400/day and 50/hour. Confirm that the site’s actual message bodies fit the documented size rule before treating the quotas as a firm capacity plan.

Resend publishes 3,000 monthly and 100 daily emails on Free. Its SMTP documentation gives a host, ports and credentials and names WordPress among integrations. A standard SMTP-capable WordPress connector can be evaluated against those settings, but choose a current, maintained connector and verify its exact compatibility before switching live mail. The available official evidence establishes an SMTP path; it does not establish that every WordPress plugin offers a dedicated Resend button or that an API-only configuration behaves like SMTP.

Personal Gmail and Google Workspace belong outside this free-service comparison. Consumer Gmail sending limits and Workspace SMTP relay rules govern different account types and configurations. A personal mailbox may be acceptable for a separate low-volume task, but “Gmail allows X messages” is not enough to conclude that a WordPress site can use it as a transactional relay with the same conditions as these four providers. Check the account, authentication and applicable policies if that is your intended route.

Make the connection test represent real site mail

Before choosing a provider, record the messages your site actually creates and their likely peak. Include password resets, account and order notices, forms, admin alerts and any plugin-generated messages. Mark which are urgent. A delayed weekly report is different from a one-time login link that expires before a provider’s daily allowance resets. Keep marketing campaigns in their own forecast; the monthly-send worksheet helps if your account also sends them.

For domain authentication, start with the From address those messages actually use. Its domain must match the identity you set up with the chosen provider; a WordPress admin address or a separate form plugin may use a different one. In the provider dashboard, request the current records for that sending domain. Add those exact records at the domain’s authoritative DNS host, then wait until the provider marks the domain verified. SMTP2GO’s domain guide, for example, issues three CNAME records and shows a Verified status. It also offers an individual-address route confirmed by an email link when DNS cannot be changed. That confirms one sender address, not its domain, and SMTP2GO’s 25/hour condition still applies without a verified sender domain. Other providers can issue different records and checks; copy their current instructions rather than using SMTP2GO’s values for them.

Then follow one controlled connector check. Confirm the provider account is approved for sending and enter the credential type that that connector asks for. Note the old route before changing it so you can restore it if a critical mail type fails. Trigger a plugin test message, a real password-reset request and one form or order notice that matters to the site, using the configured From identity. Use safe test recipients and keep credentials out of screenshots and notes. Check whether WordPress generated each message, whether the connector submitted it, what the provider recorded, and what the recipient received.

One successful test email proves that one message traversed the configured path at that moment. It does not prove that every form, sender address or future peak will behave the same way, and a provider’s “accepted” event is not a guarantee of inbox placement. A failure can originate before submission, at account or sender authorization, at a quota, or later in delivery. The Post SMTP listing describes logs and failure alerts as connector features; provider activity records may show additional events, subject to the selected plan. Match the evidence to the stage that failed instead of changing plugins at random.

For the modeled site, the practical next step is to map the 350-message day by hour. If it can be spread over at least seven hours, SendPulse’s documented free caps are worth checking in a live account with its approval and sender setup completed. If those messages must leave quickly, compare paid capacity and failure behavior before routing critical WordPress mail. Whatever service you select, keep the actual WordPress connector, provider account, verified sender and rollback route together in one configuration record.