{"id":508,"date":"2026-10-22T01:02:57","date_gmt":"2026-10-22T06:32:57","guid":{"rendered":"https:\/\/photonconsole.com\/blog\/?p=508"},"modified":"2026-10-22T06:35:29","modified_gmt":"2026-10-22T12:05:29","slug":"gmail-and-google-workspace-smtp-sending-limits-for-applications","status":"publish","type":"post","link":"https:\/\/photonconsole.com\/blog\/gmail-and-google-workspace-smtp-sending-limits-for-applications\/","title":{"rendered":"Gmail and Google Workspace SMTP Sending Limits for Applications"},"content":{"rendered":"\n

Your application sends from noreply@yourcompany.com<\/code>. So when sending stops, the puzzling part is which account Google says has hit its limit \u2014 because it is not the one in your From header.<\/p>\n\n\n\n

That single detail explains most Gmail sending mysteries, and it follows from how Google counts. There is no one Gmail limit. There are three different sending paths, each with different caps, and the caps are measured in recipients rather than messages.<\/p>\n\n\n\n

Work out which path you are on and the arithmetic stops being mysterious. Until then, the number you planned around is probably the wrong one.<\/p>\n\n\n\n

Quick Answer: What Are the Gmail SMTP Sending Limits?<\/h2>\n\n\n\n

It depends entirely on which of Google’s three paths your application uses.<\/p>\n\n\n\n

Path<\/th>Endpoint<\/th>Who it is for<\/th>Headline limit<\/th><\/tr><\/thead>
Consumer Gmail<\/td>smtp.gmail.com<\/code><\/td>Personal accounts<\/td>500 emails per day<\/td><\/tr>
Workspace Gmail<\/td>smtp.gmail.com<\/code><\/td>Paid Workspace mailboxes<\/td>Per-user daily limit, 2,000 published<\/td><\/tr>
Workspace SMTP relay<\/td>smtp-relay.gmail.com<\/code><\/td>On-premise devices and applications<\/td>10,000 messages per user per 24 hours<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Most application developers are on the first or second path and assume they are on the third. The relay service is the only one Google describes as intended for devices and applications, and it has to be switched on and configured by an administrator \u2014 it is not what you get by default.<\/p>\n\n\n\n

Figures differ by account type and change over time. Confirm yours against Google’s own pages, linked throughout, rather than any article.<\/p>\n\n\n\n

Which Path Are You Actually On?<\/h2>\n\n\n\n
\"Three
The endpoint in your configuration tells you which limits apply to you.<\/figcaption><\/figure>\n\n\n\n

Open your application’s mail configuration and read the host. That one line settles it.<\/p>\n\n\n\n

If it says smtp.gmail.com<\/code>, you are authenticating as a mailbox and you are subject to that mailbox’s per-user limits. Whether those are consumer or Workspace limits depends on the account, not the endpoint.<\/p>\n\n\n\n

If it says smtp-relay.gmail.com<\/code>, you are using the Workspace SMTP relay service, which an administrator has deliberately enabled for your domain.<\/p>\n\n\n\n

Consumer Gmail<\/h3>\n\n\n\n

Google’s limits for sending and getting mail<\/a> page sets the thresholds at more than 500 emails sent in a day, and more than 500 recipients in a single email. It also notes that work and school accounts can have different limits.<\/p>\n\n\n\n

A personal Gmail account was never intended to carry application traffic, and nothing about 500 a day makes it viable for a product with users.<\/p>\n\n\n\n

Workspace Gmail<\/h3>\n\n\n\n

For paid Workspace mailboxes, Google’s Gmail sending limits<\/a> page publishes a daily sending limit per user account of 2,000, with trial accounts limited lower. Two details on that page matter more than the headline:<\/p>\n\n\n\n