Gmail SMTP: Settings, Setup & When to Move Past It

Published November 1, 2024 · Updated August 27, 2026 · SMTP & Deliverability

Using Gmail's SMTP server is the quickest way to send email from an app, website, or script — the settings are free and already tied to your account. It works well for low volume, but Gmail's caps make it a starting point, not a destination. Here are the Gmail SMTP settings, when relaying through Gmail makes sense, and when it will hold you back.

Gmail SMTP settings

Setting	Value
SMTP server	`smtp.gmail.com`
Port	587 (STARTTLS) or 465 (SSL)
Username	your full Gmail address
Password	an app password (if 2-step verification is on)

With 2-step verification enabled, your normal password will not work for SMTP — generate an app password in your Google account security settings instead.

When relaying through Gmail makes sense

Low volume — a contact form, a personal project, a handful of notifications a day.
You already have a Gmail or Workspace account and want the fastest setup.
You are testing before committing to real infrastructure.

When it will let you down

You send more than a few hundred a day — Gmail's caps stop you cold (roughly 500/day on free Gmail, 2,000/day on Workspace).
You need a dedicated IP and full control over deliverability — on Gmail, the reputation is Gmail's, not yours.
You are running marketing campaigns — Gmail is not built for them, and heavy use risks your account.

Tip: The moment your sending outgrows a few hundred a day or starts driving revenue, relaying through Gmail costs you more in caps and deliverability risk than a dedicated SMTP would.

Checking your current usage
Google Account settings show recent security activity, including recent app-password use — a quick way to confirm whether your Gmail SMTP credentials are being used only where you expect, especially useful if you have connected multiple apps over time.
Note: If you rely on Gmail SMTP for a script or app, set a calendar reminder to review your usage before it approaches the daily cap as your project grows.
If you ever revoke an app password for Gmail SMTP, remember to generate and update a new one wherever it was in use — a revoked password breaks sending silently until updated.
Related reading: What is SMTP relay · What is an SMTP server · Free SMTP relay options

Dedicated SMTP

Send at any volume, inbox-first

Dedicated IP, unlimited sending, and SPF/DKIM/DMARC configured on signup. From $39.99/mo, cancel anytime.

See the unlimited SMTP server →Get started now

Frequently asked questions

What is Gmail's SMTP server and port?

smtp.gmail.com on port 587 (STARTTLS) or 465 (SSL), using your Gmail address and an app password.

Why won't my Gmail password work for SMTP?

With 2-step verification enabled, you must use an app password generated in your Google security settings, not your account password.

How many emails can Gmail SMTP send?

About 500 a day on free Gmail and 2,000 on Workspace. For more, use a dedicated SMTP with no cap.

Can I relay email through Gmail SMTP for an app or website?

Yes, for low volume — point your app at smtp.gmail.com on port 587 with an app password. For higher volume or marketing, use a dedicated SMTP instead.