The Brevo SMTP server is smtp-relay.brevo.com, and Brevo recommends port 587. The username is the Login shown on your account’s SMTP page, and the password is an SMTP key that you generate there. It is not your Brevo account password, and it is not an API key.
Those settings come from Brevo’s help centre as we read it on 11 November 2026. We did not send test messages for this guide, so everything below rests on Brevo’s documentation, the relevant mail standards and a few attributed user reports. Where Brevo’s own pages disagree with each other, we say so.
Connecting is only the first step. Before a password-reset email can go out, Brevo also needs a sender it accepts, an account that is activated for transactional email where Brevo requires it, and email credits that a newsletter has not already used. IP restrictions, rejection by the recipient’s mail server and service incidents can stop delivery too.
Brevo SMTP settings at a glance
Scroll horizontally to read all columns.
| Setting | Value | Notes |
|---|---|---|
| SMTP server (host) | smtp-relay.brevo.com | Brevo’s documented host |
| Port | 587 (recommended) | 2525 if your host blocks 587; 465 is also supported |
| Encryption | STARTTLS on 587; SSL/TLS on 465 | See the port section for 2525 |
| Username | The Login shown under Settings → SMTP & API → SMTP | Copy it; do not guess it |
| Password | An SMTP key | Not the account password, not an API key |
| From address | A verified sender or an address on an authenticated domain | Not the SMTP login |
Check two details in this table carefully, because Brevo documents errors involving both.
The first is the username. Depending on when the account was created, the Login is either the account email or a generated address ending in @smtp-brevo.com. Brevo’s help centre also says that changing your account email does not change this Login. Two third-party guides, from Emailchaser and Tajo, present one of the two formats as universal, which is wrong for part of their readers. Open the SMTP page and copy the field.
The second is the From address. The SMTP Login only authenticates the connection. Brevo’s troubleshooting page lists using it as the visible sender among the causes of an invalid-sender error.
Which port: 587, 465 or 2525?
Use 587 unless something stops you. Brevo recommends it, and its Supabase integration guide names the security mode explicitly as STARTTLS: the connection opens in plain text and upgrades to TLS before your credentials are sent.
Port 465 works differently. TLS starts as soon as the connection opens, which mail clients usually label “SSL” or “SSL/TLS”. Brevo’s port article describes 465 as deprecated, yet it still lists 465 as supported, and RFC 8314, the current standard for mail submission, defines implicit TLS on 465 as a valid option. If your application offers only “SSL” and port 465, that combination is supported.
Port 2525 exists for hosts and cloud providers that block 587. Brevo documents it as an alternative, but the official pages we read do not state which encryption mode it uses. Third-party guides say STARTTLS. Treat that as likely and unconfirmed, and check that your client reports a TLS session after it connects.
One caution about Brevo’s own wording. Its main SMTP setup article tells you to leave the encryption field empty except on port 465. How a mail client treats an empty encryption field varies, and in some it means no encryption at all. Choose STARTTLS or TLS explicitly on 587 where your software has such a setting.
How to create an SMTP key
- In Brevo, open Settings → SMTP & API and select the SMTP tab.
- Choose Generate a new SMTP key. Brevo asks you to verify your identity first.
- Name the key after the system that will use it, for example
shop-production. - Pick the format. Standard keys have 64 characters. Short keys have 15 and exist for older software that cuts long passwords off.
- Pick an expiry between 7 days and 1 year, or none.
- Generate the key and store it at once. Brevo shows the full value a single time.
You need to be the account owner or have the SMTP permission to do this. Use one key per application, so that revoking one does not break the others. We found no stated maximum number of keys.
A point that catches low-volume senders: a key with no successful send for 90 days can be deactivated, even if you chose no expiry. A contact form that receives one enquiry a quarter can lose its key this way. If your mail is that occasional, send a scheduled test message each month.
Brevo SMTP limits on the Free plan
The Free plan allows 300 email sends a day. The allowance resets daily and unused sends do not carry over. We found no documented reset time zone.
Marketing and transactional messages draw on the same email credits. There is no separate allowance for SMTP. If a newsletter goes to 250 subscribers in the morning, 50 sends remain for order confirmations and password resets for the rest of that day.
When the daily cap is reached, Brevo does not reject transactional email immediately. According to its Free plan FAQ, up to 1,000 further transactional emails are held in a retry queue, and messages beyond that queue are not delivered. A separate help article says queued messages begin to be discarded after 72 hours. A held password reset is of little use to the person waiting for it, so plan for the cap instead of relying on the queue.
The daily figure hides a second trap. Three hundred a day is 9,000 over a 30-day month, but that is arithmetic, not a balance you can spend freely. A shop that sends 6,000 emails a month fits under 9,000 on paper. If 600 of them go out on one busy day, about half of that day’s mail would be held in the retry queue instead of going out at once.
We found no documented hourly limit for SMTP sending today. Brevo states that it removed its former hourly quota for transactional email on 10 March 2023. That does not mean throughput is unlimited: we found no published figure for SMTP connections or messages per minute.
Per message, the help centre gives a total size of 20 MB, including the body and attachments. We found no documented maximum number of recipients for an ordinary SMTP message.
What the paid plans add
Brevo’s help centre lists these starting prices in dollars. We could not load the live pricing grid or a checkout, so treat them as the documented starting points, not a quote.
Scroll horizontally to read all columns.
| Plan | Starting price | Email sends included at that price |
|---|---|---|
| Free | $0 | 300 a day |
| Starter | From $9 a month | 5,000 a month |
| Standard | From $18 a month | 5,000 a month |
| Professional | From $499 a month | 150,000 a month |
| Enterprise | Custom | Custom |
Paid plans are listed with a monthly send allowance, which is the figure to compare against your busiest month. We did not find Brevo’s documentation of how paid plans treat a single heavy day, so check that before relying on it. Yearly billing is charged upfront and advertised at 10% off, prices exclude taxes, and unused monthly credits expire. Professional and Enterprise accounts can add a dedicated IP, documented at $251 a year; Enterprise already includes one. Our Brevo pricing guide works through the plan choice for a small business.
Sender and domain requirements
Brevo will not relay mail from an address it has not accepted. There are two routes.
Verify a single sender. If the sender’s domain is not authenticated, Brevo asks you to confirm the address with a six-digit code that it emails there. This suits one address, such as orders@yourshop.com.
Authenticate the domain. Brevo gives you DNS records to add: a Brevo code (a TXT record that proves ownership), DKIM (one TXT record or two CNAME records, depending on the account) and a DMARC TXT record. Copy the values from your own account; they are specific to it. Once the domain is authenticated, senders on it are verified automatically. You cannot authenticate a free-mail domain such as gmail.com, because you do not control its DNS.
Authenticate the domain even if single-sender verification would get you started. For mail sent to personal Gmail accounts, Google’s sender guidelines require SPF or DKIM, plus TLS. Senders of more than 5,000 messages a day to those accounts must also set up SPF, DKIM and DMARC with alignment. Brevo’s help centre adds that it may replace a free-mail From address with one of its own domains.
Brevo is rolling out a new domain setup screen gradually, so your account may not match older screenshots. Follow the records your account displays.
Common Brevo SMTP errors and their documented fixes
Scroll horizontally to read all columns.
| What you see | Likely cause | Fix from Brevo’s documentation |
|---|---|---|
535 5.7.8 Authentication failed | Wrong Login, wrong or expired key, stray spaces, a client that truncates the key, or a port and encryption mismatch | Copy the Login again, generate a new key, try a Short key in older software, and match STARTTLS to 587 or SSL/TLS to 465 |
| Invalid sender | The From address is unverified, or it is the SMTP Login | Send from a verified sender or an address on an authenticated domain |
450 Your SMTP account is not yet activated | Transactional sending has not been activated, or the account is suspended | Open a ticket with Brevo support from the account |
525 5.7.1 Unauthorized IP address | IP blocking is switched on and your server’s address is not on the list | Add the server’s real outbound IP under the security settings |
| Connection fails with no SMTP banner | A network or hosting restriction on the port | Try port 2525, which Brevo lists for hosts that block 587, or ask your host which ports are open |
| Mail is accepted but waits | Email credits are exhausted | Check the transactional usage and queue pages; wait for the reset or add credits |
Three of these deserve a comment.
Activation is a real step for some accounts. Brevo documents a separate activation for transactional email and sends inactive new senders to support. We found no published approval time, so set the account up some days before a launch.
The IP restriction behaves differently for SMTP than for the API. The authorized list is shared, but Brevo’s documentation says SMTP has no automatic learning phase. Add your server’s address before you enable blocking. On cloud hosting the outbound address can differ from the one in your dashboard.
Suspension is also documented. Brevo’s help centre says unusual signup patterns or poor transactional results can lead to a review by support, and that subscription billing continues while an account is suspended. In an October 2025 Brevo Community post, the user Nextwave reported a transactional suspension related to form security, and difficulty obtaining reactivation help after adding reCAPTCHA. That is a single account, not a measure of how often it happens. Protecting any form that triggers email is still cheap insurance.
Brevo SMTP relay or the transactional API?
Both routes deliver through the same service and the same allowance. The difference is how much control your code has.
Scroll horizontally to read all columns.
| SMTP relay | Transactional API | |
|---|---|---|
| Works with | Almost any application, plugin or device with SMTP settings | Code that can make HTTPS requests |
| Authentication | SMTP Login and SMTP key | API key in the api-key header |
| Stored Brevo templates | Mentioned in Brevo’s examples, but we found no clear documented syntax | templateId with params |
| Batch sending | Not supported, per Brevo’s relay guide | Up to 1,000 message versions and 2,000 recipients per request, 99 recipients per version |
| Opens, clicks, logs, webhooks | Yes | Yes |
| Counts against the email allowance | Yes | Yes |
Stay with SMTP when the software already speaks it: WordPress, a contact-form plugin, a CRM, a printer or a monitoring tool. You enter Brevo’s connection settings, then confirm the sender, the transactional activation and any IP restriction. No code changes are needed. For WordPress specifically, see our guide to the Brevo SMTP plugin for WordPress.
Use the API when you write the sending code yourself and want its documented templateId and params fields, tags set in the request, or one request that produces many personalised messages. The batch limits apply together and also include 6,000 calls an hour and 100 a minute.
Do not move to the API expecting to escape limits or outages. The daily and monthly allowances, sender rules and account reviews apply to both. Brevo’s status page records an incident on 16 June 2026 in which both API and SMTP submissions were accepted while delivery was halted.
Tracking is not a reason to switch either. Brevo’s transactional logs cover SMTP, API and automation messages alike and can be exported as CSV, up to 200,000 entries at a time. Webhook events state which of the three sources a message came from.
Checklist before you rely on it
- Authenticate your domain and wait for Brevo to show the records as verified.
- Create one SMTP key per application and store each in a password manager.
- Copy the Login from the SMTP page. Set port 587 with STARTTLS.
- Set the From address to a verified sender on that domain.
- Send a test to an address on another provider and read the transactional log entry for it.
- Work out your busiest realistic day, not your monthly total, and compare it with 300 if you are on the Free plan.
- Protect every public form that sends mail with a CAPTCHA or rate limit.
- If you enable IP blocking, add the server’s outbound IP first.
Who Brevo SMTP suits
Brevo’s Free plan is a reasonable fit for a site whose transactional mail stays well under 300 a day on its busiest day, counting any campaigns sent from the same account. Contact forms, account emails for a small membership site and order mail for a low-volume shop are typical cases.
It fits badly when volume arrives in bursts, or when a late password reset costs you a customer. A paid plan is measured against a monthly allowance instead, which suits bursty volume better on paper, but confirm how Brevo treats a heavy day before relying on it. If you are still deciding between free relays, our comparison of free SMTP options for WordPress sets Brevo’s allowance beside the alternatives.
Frequently asked questions
What is the Brevo SMTP server address?
smtp-relay.brevo.com, on port 587 with STARTTLS. Ports 465 and 2525 are also supported.
Is my Brevo SMTP password the same as my account password?
No. The SMTP password is an SMTP key generated under Settings → SMTP & API → SMTP. An API key will not work for SMTP either.
How many emails can I send through Brevo SMTP for free?
Up to 300 a day on the Free plan. Marketing and transactional emails share that allowance, and unused sends do not carry over to the next day.
Why does Brevo say my SMTP account is not yet activated?
This error can mean transactional sending has not been activated for the account or that the account has been suspended. Brevo’s documentation directs you to open a support ticket.
Does Brevo SMTP support templates?
Brevo’s documentation shows personalisation over SMTP, but we found no clear documented way to call a stored template through SMTP. The API documents it with templateId and params.
The Free plan's 300 sends a day are shared between marketing and transactional email, and unused sends do not carry over.
Sources and checking
Product terms can change. These are the sources checked for this article; follow the links to verify current details before you buy.
- Brevo Help: Send transactional emails using Brevo SMTP (checked 2026-11-11)
- Brevo Help: Which SMTP port should I use? (checked 2026-11-11)
- Brevo Help: Create and manage your SMTP keys (checked 2026-11-11)
- Brevo Help: Troubleshooting issues with Brevo SMTP (checked 2026-11-11)
- Brevo Help: Authorize and block IP addresses for API and SMTP security (checked 2026-11-11)
- Brevo Help: What are the limits of the Free plan? (checked 2026-11-11)
- Brevo Help: Add or remove emails from your plan (checked 2026-11-11)
- Brevo Help: Why are emails added to a queue? (checked 2026-11-11)
- Brevo Help: About Brevo's pricing plans (checked 2026-11-11)
- Brevo Help: Customize your plan with add-ons (checked 2026-11-11)
- Brevo Help: Create a new sender (checked 2026-11-11)
- Brevo Help: Authenticate your domain with Brevo (checked 2026-11-11)
- Google: Email sender guidelines (checked 2026-11-11)
- Brevo Developers: Send a transactional email (checked 2026-11-11)
- Brevo Developers: Batch send transactional emails (checked 2026-11-11)
- Brevo Developers: SMTP relay integration (checked 2026-11-11)
- Brevo Developers: Connect Brevo SMTP to Supabase (checked 2026-11-11)
- Brevo Help: Add an attachment to a transactional email (checked 2026-11-11)
- Brevo Help: Manage your transactional logs and email previews (checked 2026-11-11)
- Brevo Developers: Transactional webhooks (checked 2026-11-11)
- Brevo Help: Why have my account or email campaigns been suspended? (checked 2026-11-11)
- Brevo Status: Transactional email sending halted (16 June 2026) (checked 2026-11-11)
- IETF RFC 8314: Use of TLS for email submission and access (checked 2026-11-11)
- Brevo Community: Can't get a response (Nextwave, 14 October 2025) (checked 2026-11-11)
- Brevo Help: Set up your domain in Brevo (checked 2026-11-11)
- Brevo Help: Comply with Gmail, Yahoo, and Microsoft's requirements for email senders (checked 2026-11-11)
- Brevo Developers: Node.js SMTP example (checked 2026-11-11)
- Emailchaser: Brevo SMTP settings (checked 2026-11-11)
- Tajo: Brevo SMTP guide (checked 2026-11-11)
