Google Workspace SMTP caps at 2,000 messages per 24 hours per user (Google, 2026). Amazon SES production accounts start at 50,000 per 24 hours and scale into the millions (AWS, 2026). For any bulk marketing list or growing transactional system, Workspace SMTP is the wrong tool, not because the infrastructure is bad but because it was built for one-to-one mail. Workspace SMTP and SES are not competitors at the same volume tier.
The Actual Limits
Google caps a single Workspace user at 2,000 outbound messages per 24 hours via Gmail SMTP, or 10,000 via the org-wide SMTP relay, with 100 recipients per SMTP transaction in either case (Google, 2026). Amazon SES gives a new production account 50,000 per 24 hours at 14 messages per second and grows from there with usage (AWS, 2026). The numbers below are the full picture:
- Gmail per-user SMTP: 2,000 messages per 24 hours per user, with a hard ceiling of 100 recipients per SMTP transaction and 3,000 unique external recipients per day.
- Workspace SMTP relay (the org-wide relay configured in the Admin console): 10,000 messages per user per 24 hours, 100 recipients per SMTP transaction, and a 4.6 million recipient-per-day cap for the whole organization, with rate sublimits of 319,444 recipients per 10-minute window.
- Recipients per message: 2,000 total per Gmail-API message but only 500 external; 100 per SMTP message regardless of channel.
- Acceptable use: Workspace's terms explicitly prohibit using Gmail or the SMTP relay for unsolicited marketing email.
Amazon SES starts production accounts at:
- 50,000 emails per 24 hours (account-level daily quota).
- 14 emails per second (max send rate).
- Both scale with usage and reputation; experienced accounts run at millions per day and hundreds of messages per second (AWS, 2026).
| Constraint | Google Workspace SMTP | Amazon SES |
|---|---|---|
| Per-user daily cap | 2,000 (Gmail SMTP) or 10,000 (relay) | 50,000+ (scales to millions) |
| Org-wide daily cap | 4.6 million recipients (relay) | None; quota is account-level |
| Recipients per SMTP transaction | 100 | 50 destinations (SendBulkEmail batches up to 50) |
| Send rate | 319,444 recipients per 10 min (relay org cap) | 14/sec at start, scales to 1,000+/sec |
| Cost | Included with Workspace ($7-23/user/mo, 2026) | $0.10 per 1,000 emails |
| Marketing email allowed | No - prohibited by Workspace terms | Yes |
| Account suspension risk at bulk volume | High - Google suspends bulk-sending Workspace accounts | Low - SES is designed for bulk |
| Deliverability infrastructure | Gmail's shared sending pool | Dedicated SES infrastructure + optional dedicated IPs |
The per-user volume gap is 25x via the relay (2k vs 50k) and 5x at the relay's 10,000 ceiling. Stack additional Workspace users and the relay scales further, but the marketing-content prohibition means the limit you actually hit first is Google's acceptable-use enforcement, not the numerical cap.
What Happens When Workspace SMTP Hits Its Limit
Workspace SMTP does not queue messages above the limit. It rejects them, then suspends the user for up to 24 hours (Google, 2026). A sender past the per-user cap gets a 550 SMTP error with "User-rate limit exceeded" and the message is dropped. The org-wide relay returns similar errors and also flags the Workspace account for abuse review.
The user-visible effect:
- Mid-campaign, a percentage of messages start failing.
- The sending application sees SMTP errors but the recipients see nothing.
- Google may suspend the user account or the entire Workspace org for 24 hours.
- After suspension, the account is flagged - it can be re-suspended faster on the next offense.
The damage isn't just the failed messages. Repeated abuse moves the Workspace account into a tighter sending-limit tier and can affect normal Gmail behavior (delayed delivery, more spam folder placement) for weeks. Senders who treat Workspace SMTP as a free bulk channel often end up with a Gmail account that no longer works well for legitimate person-to-person mail.
Why Workspace SMTP Doesn't Scale
Workspace SMTP runs on the same Gmail sending infrastructure as regular person-to-person mail, with reputation pooled across every message the user account sends (Google, 2026). When a Workspace user pushes 1,800 emails to a marketing list, those messages compete for inbox placement against the same user's one-to-one business mail. The shared reputation means a single bad marketing campaign degrades every other email that user sends going forward.
Workspace also has no concept of:
- Per-recipient suppression list: bounced addresses don't get auto-suppressed; the next campaign hits them again.
- Per-campaign reputation isolation: every send affects every other send.
- Dedicated IP: Workspace mail goes through Gmail's shared sending IPs.
- Configuration sets: no way to tag campaigns separately for analytics.
- Bounce/complaint event publishing: no SNS or event-stream equivalent; you get SMTP error codes only.
Amazon SES has all of these as first-class features. Workspace SMTP intentionally doesn't, because they aren't needed for the workflow it's designed for.
When Workspace SMTP Is the Right Call
Workspace SMTP is the right tool when sending volume per Workspace user stays well under the 2,000-per-day Gmail cap and content is one-to-one rather than bulk marketing (Google, 2026). The convenience of sending through the user's existing Workspace identity outweighs the lack of SES-style features. Four workflows fit cleanly:
- Customer support replies sent from a real human's Workspace account.
- Sales outreach where each message is genuinely personalized and volume per rep is low (typically under 100/day).
- Small SaaS transactional email during early-stage prototyping (under 500 emails/day, where you'll move to SES or a transactional API later).
- Internal company automation where messages stay inside the Workspace org and don't count toward external limits.
For these workflows, Workspace SMTP is convenient (already authenticated via the user's Google login) and acceptable (well within the limits). The configuration is just SMTP credentials with the user's email and a Workspace-issued app password.
When Amazon SES Is the Right Call
Use Amazon SES whenever your sending pattern looks like bulk, marketing, or scaled transactional - the workflows Workspace SMTP refuses by design. SES production accounts start at 50,000 messages per 24 hours at 14 per second and grow into the millions with steady volume and a clean reputation (AWS, 2026). The fit cases:
- Any newsletter sending to a list larger than 1,000 subscribers.
- Any transactional system above a few hundred per day.
- Any marketing campaign with multiple sends.
- Any application where deliverability matters more than convenience.
- Any sender concerned about Workspace account suspension risk.
Amazon SES costs roughly $5 per month for 50,000 emails (AWS, 2026), or about the price of a single Workspace Business Standard seat ($14/month per user). At the volumes where Workspace SMTP starts breaking, SES is dramatically cheaper per useful unit of capacity.
See the SES vs SendGrid comparison for how SES compares to traditional email APIs, or the SES rate limits guide for how SES quotas grow with usage.
What This Means Practically
If you are already running bulk email through Workspace SMTP, migrate before Google enforces. AWS approves most SES production-access requests in 24 to 72 hours (AWS, 2026), so you can have a working SES path in less than the duration of a single Workspace suspension. The migration checklist:
- Switch before you hit the cap, not after. Once Google suspends the account, the recovery takes 24+ hours and damages the account's reputation. Migrate proactively.
- Use Workspace for what it's good at: person-to-person business email. Don't break it by piping bulk through it.
- Use Amazon SES for bulk: hosted via a management layer like Mailblast for marketing campaigns, or directly via the SES API for transactional integration.
The conversion path is straightforward. SES production access takes 24-72 hours to provision; once approved, your sending application changes from Gmail SMTP credentials to SES SMTP credentials or the SES API. The rest of the system (lists, templates, scheduling) doesn't need to change.
FAQ
Can I use Google Workspace SMTP for bulk email?
Not for marketing. Per-user Gmail SMTP caps at 2,000 messages per 24 hours with 100 recipients per SMTP transaction; the Workspace SMTP relay caps at 10,000 messages per user per 24 hours and 4.6 million recipients per organization (Google, 2026). Workspace also forbids using these channels for marketing email. Amazon SES starts at 50,000 per day and scales to millions, with no marketing-content restriction.
What is Google Workspace SMTP for?
Workspace SMTP is designed for legitimate person-to-person and small-scale system email: customer-facing transactional messages from a small SaaS, low-volume internal automation, and direct human-sent business email. It's an extension of Gmail, not a marketing platform. The limits are deliberate - they keep abusive senders from using Workspace as a spam channel.
Will Google suspend my Workspace account for sending too much?
Yes. Google enforces sending limits aggressively and suspends accounts that exceed them. Suspensions are typically 24 hours for first offenses but escalate quickly. A bulk-sending pattern on a Workspace account also flags the account for additional review, which can affect normal Gmail use even after the temporary block expires.
Is Google Workspace SMTP cheaper than Amazon SES?
Per email, Workspace SMTP is included with your Workspace subscription at no extra fee. Per useful unit of sending capacity, SES is dramatically cheaper. Workspace caps a single user at 2,000 messages per day via Gmail SMTP or 10,000 via relay; SES charges $0.10 per 1,000 emails, so 50,000 per day costs $5 per month. Workspace SMTP is only free up to limits that are too low for bulk.
When should I actually use Google Workspace SMTP?
For sending under 100 emails per day from a real person's Workspace account: customer support replies, sales outreach where each message is genuinely personalized, transactional emails for a small system. For anything above that volume threshold, use Amazon SES (or a hosted ESP like Mailblast on top of SES).
Disclosure: Mailblast is a hosted management layer for your own Amazon SES account. We have no commercial relationship with Google Workspace. This comparison reflects the publicly documented limits of both services as of June 2026.