Using Gmail SMTP to Send Emails: 2,000 Emails/Day Cap (and What to Do When You Hit It)

Gmail handles billions of emails daily, which is why its SMTP server is a common starting point for small-scale sending. It’s free, it’s familiar, and it works out of the box.

But there’s a ceiling. And if you’re doing any kind of outreach, you’ll hit it fast.

I’ve watched teams burn through Gmail’s daily quota by noon, then wonder why their sending account got throttled for 24 hours. The fix isn’t hacking Gmail’s limits. It’s understanding them, then deciding if Gmail SMTP is still the right tool for the job.

In this post, I’ll walk you through how Gmail SMTP actually works in 2026, the two authentication methods Google now requires, the sending limits you’ll run into, and when it makes sense to move to something built for volume.

What is SMTP?

Simple Mail Transfer Protocol is, by far, the most widely used protocol for sending emails.

SMTP comes into action when you click the send button in your email client. Hitting that button connects your email client to the SMTP server.

SMTP then functions as a postman, taking your email to the receiving server (typically an IMAP server), to which the recipient’s email client can connect to check their email.

Gmail SMTP settings quick reference

Before you configure anything, here are the settings you’ll need. I’m putting them up front because this is what most people are actually searching for.

Port 587 with STARTTLS is the recommended option. Port 465 with SSL still works but is considered legacy. Port 25 sends unencrypted, so avoid it entirely for anything involving credentials or personal data.

Using Gmail’s SMTP with third-party apps or services

As of 2026, Google has fully retired password-only SMTP access. Google originally told Workspace users that password-only access from less secure apps would stop on September 30, 2024, but later paused the rollout, resumed it in January 2025, and completed the final shutdown on May 1, 2025. (Gmail App Access Password Deadline: What Changed?)

If you’re connecting a third-party app to Gmail’s SMTP server, you now have two options:

1. 1.

   OAuth 2.0 (Sign in with Google) — this is the modern path. Starting March 14, 2025, users must use OAuth with third-party apps to access Gmail. (Transition from less secure apps to OAuth - Google Workspace Admin Help) If the app supports it, use it. No passwords are stored or transmitted.

2. 2.

   App Passwords — for apps and scripts that can’t handle OAuth, Google still allows you to generate a 16-character App Password from your Google Account settings. You must use OAuth, usually displayed as Sign in with Google, or use an App Password where the account and application support it. (Gmail App Access Password Deadline: What Changed?) You’ll need 2-Step Verification enabled on your account first.

This transition is complete. Manual username/password connections to Gmail’s SMTP server no longer work at all. Starting May 1, 2025, Google Workspace accounts no longer support less secure apps, third-party apps, or devices that ask you to sign in with your username and password. (Control access to less secure apps | Apps & integrations  | Google Workspace Help)

For full details, see Google’s OAuth transition timeline and Google’s less secure apps policy.

The good news: connecting via OAuth is actually easier for most apps. No need to manually enter server information. Just log in, grant permission, done.

Gmail SMTP sending limits

This is the part most people skip until it’s too late.

A free Gmail account allows sending to up to 500 recipients per day, while a Google Workspace account supports up to 2,000 recipients per day. (Gmail SMTP 2026: Sending Limits, Restrictions & Auth Changes) Because the quota is recipient-based, sending one message to 20 people counts as 20 toward your daily limit. (Gmail SMTP 2026: Sending Limits, Restrictions & Auth Changes)

Here’s the breakdown:

Free Gmail accounts can send 500 emails per day via the browser interface or 100 per day via SMTP. (Email Sending Limits in 2026: Gmail, Outlook & 8 Providers Compared) That SMTP cap is the one that bites you when you’re piping mail through third-party tools.

A few things worth knowing:

• •

  Limits reset on a rolling 24-hour window, not at midnight. (Email Sending Limits in 2026: Gmail, Outlook & 8 Providers Compared)

• •

  If you exceed the limit, your account is blocked from sending for 1–24 hours. (Email Sending Limits in 2026: Gmail, Outlook & 8 Providers Compared) Repeat violations lead to longer suspensions and can permanently damage your domain reputation. (Email Sending Limits in 2026: Gmail, Outlook & 8 Providers Compared)

• •

  Gmail SMTP works reliably for personal communication and low-volume sending, but it was not designed as high-volume email delivery infrastructure. (Gmail SMTP 2026: Sending Limits, Restrictions & Auth Changes)

For the full data, see serversmtp.com’s breakdown of Gmail’s daily sending limits.

If you’re running cold outreach through Gmail SMTP, that 100-email SMTP cap on a free account (or even 2,000 on Workspace) won’t get you far. And you risk nuking your sender reputation long before you hit the numerical ceiling. The real cold email limit is reputation, not Google’s cap: sending near 2,000 cold from one mailbox will wreck deliverability long before you hit the ceiling. (Gmail & Workspace Sending Limits 2026 | HotHawk)

This is where you need to think about dedicated sending infrastructure. More on that below.

Adding SMTP servers to Gmail

Using Gmail SMTP server with third-party apps is one side of the equation. It’s also possible to add non-Gmail SMTP servers to your Gmail interface.

The most likely scenario: you want to add another sending email account to Gmail. Here’s how.

Step 1: Collect SMTP server info from your email service provider or domain. You need:

• •

  ➡️ Your email’s username and password (or App Password)

• •

  ➡️ The server’s address, which usually follows this syntax: subdomain.domain.com (for example, smtp.gmail.com)

• •

  ➡️ The port number the server uses

• •

  ➡️ The encryption type: STARTTLS (port 587), SSL (port 465), or none (port 25)

Step 2: Go to your Gmail account and click the settings icon. Then click Accounts and Import.

Step 3: Scroll down to Send mail as, and in that section, click Add another email address.

Step 4: A window will pop up where you must give a name to this email account and add your email address. Click next when done.

(Note: Gmail’s settings UI has changed over time. If these screenshots don’t match what you see, look for the same options under Settings → Accounts and Import.)

Step 5: Add the SMTP server and your username and password, and select the correct port. Hit Add Account when done.

Step 6: If all went well, the sending account should now be active. If it’s not, double-check that the port number and encryption method match the details your ESP gave you. A mismatch between port and encryption type is the most common failure here.

Even if Google confirms the account has been successfully added, send a few test emails to verify everything works. Don’t skip this.

When Gmail SMTP isn’t enough: SMTP relay alternatives

I want to be honest about this. Gmail’s SMTP server is fine for personal sending and light transactional email. Once you need volume, reliability at scale, or outbound sales infrastructure, it’s the wrong tool.

Here are the legitimate alternatives, depending on your use case:

For transactional and application email:

• •

  SendGrid, Mailgun, and Amazon SES are three of the most widely used SMTP providers. SendGrid offers the most complete feature set for marketing and transactional email, Mailgun provides developer-friendly APIs with excellent logging, and Amazon SES delivers the lowest per-email cost for high-volume senders willing to manage more infrastructure. (Comparing Email Providers: SendGrid vs Mailgun vs Amazon SES)

• •

  Postmark focuses exclusively on transactional email with strong delivery speed. (6 Best SendGrid Alternatives Tested & Compared [2026])

These services exist for a reason. If you’re sending order confirmations, password resets, or notifications at any real volume, pick one of them over Gmail SMTP.

For cold outreach and sales email:

Transactional SMTP relays solve the volume problem, but they’re not built for cold outreach workflows. You need sequence logic, reply detection, deliverability monitoring, and multichannel follow-ups.

That’s where a purpose-built outbound platform comes in. With lemlist, you can run outbound across email, LinkedIn, and calls from a single sequence, use cold email templates tested on real campaigns, and warm up your sending domain so your emails actually land in the inbox instead of spam.

The difference between Gmail SMTP and dedicated outbound infra isn’t just about limits. It’s about deliverability monitoring, domain reputation management, and knowing when a sending account is trending toward spam before it gets there. That’s what lemlist’s deliverability tools are built to do: protect deliverability at scale.

Final thoughts

Gmail’s SMTP server works. For personal email, for a handful of transactional messages, for quick tests, it’s perfectly fine. The authentication rules changed (OAuth or App Passwords, nothing else), but the core setup is still straightforward.

The real question isn’t can you use Gmail SMTP. It’s whether you should, given what you’re trying to do.

If you’re sending beyond a handful of emails a day, Gmail’s limits will catch up with you. The 100-email SMTP cap on free accounts is genuinely restrictive, and even Workspace’s 2,000/day ceiling isn’t built for outbound at any real scale.

For teams doing cold outreach, the move is to dedicated sending infrastructure with proper warm-up and deliverability monitoring. Start a 14-day free trial of lemlist to see how it works with domains built for outreach volume.

To learn more about SMTP servers in general, read: What is an SMTP server? A simple explanation.