Log inTry the sandbox free

Deliverability

Provider sending limit checker

See Google Workspace's and Microsoft 365's own published sending limits side by side, each cited to the vendor's own page.

Free, no accountIn your browser

Try

Result

Google Workspace and Microsoft 365 sending limits

Both vendors' own published limits, side by side.

  • Info

    These are each vendor's published defaults, not a per-account ceiling

    An account's real sending ceiling can be lower than the figures above while it is new or on a trial plan, and neither vendor exposes a per-account figure to a tool outside their own admin console - nothing here is checked against any live account.

  • Info

    Microsoft's two rate limits can't be raised

    Microsoft states that the recipient rate limit and message rate limit "are hard limits enforced at the service level and can't be increased." Google's per-user limit, by contrast, can be worked around using its separate SMTP relay service, which publishes its own, different ceiling.

Google Workspace

LimitPublished value
Daily sending limit per user account2,000 (1,500 for mail merge, 500 for trial accounts)
Total recipients per day10,000 (1,500 for mail merge)
External recipients per day3,000
Recipients per message2,000 total, maximum 500 external

Google Workspace, "Gmail sending limits in Google Workspace" (knowledge.workspace.google.com), read 2026-10-13.

Microsoft 365

LimitPublished value
Recipient rate limit10,000 recipients per day, on a 24-hour sliding window
Message rate limit30 messages per minute
Recipient limit per message500 by default, customisable from 1 to 1000

Microsoft, "Troubleshoot outbound sending limits in Exchange Online" (learn.microsoft.com), read 2026-10-13.

SMTP relay and API limits are different

Google Workspace publishes separate, higher ceilings for sending through the SMTP relay service and through the Gmail API - neither is blended into the per-user mailbox limits above.

SMTP relay, per user: up to 10,000 messages and up to 10,000 unique recipients in a 24-hour period, with up to 100 recipients per SMTP transaction. SMTP relay, organisation-wide: up to 4.6 million recipients in a 24-hour period, or 319,444 in a 10-minute window - Google Workspace, "Route outgoing SMTP relay messages through Google", read 2026-10-13.

Gmail API: 500 recipients per message, 6,000 quota units per user per minute, 1,200,000 quota units per project per minute - a messages.send call costs 100 of those units. Google for Developers, "Usage limits | Gmail", read 2026-10-13.

  • These are each vendor's own published defaults, not a per-account ceiling - an account's real limit can be lower while it is new or on a trial plan, and neither vendor exposes a per-account figure to an outside tool.
  • Nothing here is checked against any live account; both tables above are static data taken from each vendor’s own page.

What this is

This gmail sending limit google workspace checker shows Google Workspace's and Microsoft 365's own published sending limits side by side, each cited to the vendor's own page and the date it was read, with SMTP-relay and API-based sending kept as a separate figure rather than blended into the per-user row.

A Google Workspace mailbox and a Microsoft 365 mailbox are each capped by their own vendor, not by a number either vendor expects a sender to look up before hitting it. Google Workspace caps a mailbox at 2,000 messages a day (1,500 for mail merge, 500 on a trial); Microsoft 365 caps a mailbox at 10,000 recipients on a rolling 24-hour window and 30 messages a minute. Both figures below come straight from each vendor's own documentation.

Sending through Google's SMTP relay service or the Gmail API is not the same thing as sending from a mailbox, and each has its own, different ceiling - the relay allows far more messages per user per day than a mailbox does on its own, and the API is metered in quota units rather than messages. This page keeps that figure separate so it is never read as the per-user limit.

How to read the result

Both vendors are ticked to begin with, which is the full comparison with nothing to type; untick one to read the other’s table on its own. Each table cites the vendor page it was read from, and the date, so the figures can be checked against the source directly.

The SMTP-relay and API text below Google Workspace's table is there on purpose, not folded into the mailbox row above it - those are higher, different ceilings that only apply if you are actually sending through the relay or the API rather than from a mailbox.

One of our guides, "What Google and Yahoo require from bulk senders, and how to prove you meet it," explains why these per-mailbox ceilings are a separate thing from Google's and Yahoo's own bulk-sender rules, not a stand-in for them.

Common mistakes

What goes wrong most often, and how to tell.

  • Reading the SMTP relay figure as the mailbox limitGoogle's SMTP relay service allows up to 10,000 messages per user in 24 hours, a very different number from the 2,000-a-day mailbox limit above it. Mixing the two up makes a working mailbox setup look like it should handle far more volume than it actually can.
  • Treating a published default as a guaranteed ceiling for every accountThese figures are each vendor's own published defaults. A brand-new domain or a trial account can be capped lower than the numbers shown here, and neither vendor exposes that per-account figure to an outside tool - only the admin console shows the real number for a specific account.
  • Assuming Microsoft's limits can be raised the way Google's relay works around its ownMicrosoft states its recipient rate limit and message rate limit are hard limits enforced at the service level and cannot be increased. Google's per-user mailbox limit, by contrast, can be worked around by sending through the separate SMTP relay service instead.

Questions

What people ask about this tool.

  • 2,000 messages a day for a standard account, 1,500 for mail merge (previously called multi-send), and 500 for a trial account - Google Workspace's own published figure, read 2026-10-13.

  • 10,000 recipients per day on a 24-hour sliding window, 30 messages per minute, and a recipient limit of 500 per message by default, customisable from 1 to 1000 - Microsoft's own published figure, read 2026-10-13.

  • No. Google Workspace’s SMTP relay service allows up to 10,000 messages per user and up to 10,000 unique recipients in a 24-hour period, a different and higher ceiling than the 2,000-a-day mailbox limit, and it is organisation-wide as well as per-user.

  • No. Microsoft states its recipient rate limit and message rate limit are hard limits enforced at the service level and can't be increased, unlike Google's mailbox limit, which can be worked around using the separate SMTP relay service.

Sources

Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.

Use it from the API

The same check, as one request.

Request
curl -X POST https://resellerhq.com/api/tools/provider-sending-limit-checker \
  -H "Content-Type: application/json" \
  -d '{"providers":["google","microsoft"]}'
Response
{
  "tool": "provider-sending-limit-checker",
  "input": {
    "providers": [
      "google",
      "microsoft"
    ]
  },
  "result": {
    "verdict": {
      "tone": "neutral",
      "headline": "Google Workspace and Microsoft 365 sending limits",
      "summary": "Both vendors' own published limits, side by side."
    },
    "findings": [
      {
        "id": "published-defaults-not-a-ceiling",
        "severity": "info",
        "title": "These are each vendor's published defaults, not a per-account ceiling",
        "detail": "An account's real sending ceiling can be lower than the figures above while it is new or on a trial plan, and neither vendor exposes a per-account figure to a tool outside their own admin console - nothing here is checked against any live account."
      },
      {
        "id": "microsoft-limits-cannot-be-raised",
        "severity": "info",
        "title": "Microsoft's two rate limits can't be raised",
        "detail": "Microsoft states that the recipient rate limit and message rate limit \"are hard limits enforced at the service level and can't be increased.\" Google's per-user limit, by contrast, can be worked around using its separate SMTP relay service, which publishes its own, different ceiling."
      }
    ],
    "parts": [
      {
        "kind": "table",
        "title": "Google Workspace",
        "columns": [
          "Limit",
          "Published value"
        ],
        "rows": [
          [
            "Daily sending limit per user account",
            "2,000 (1,500 for mail merge, 500 for trial accounts)"
          ],
          [
            "Total recipients per day",
            "10,000 (1,500 for mail merge)"
          ],
          [
            "External recipients per day",
            "3,000"
          ],
          [
            "Recipients per message",
            "2,000 total, maximum 500 external"
          ]
        ],
        "note": "Google Workspace, \"Gmail sending limits in Google Workspace\" (knowledge.workspace.google.com), read 2026-10-13."
      },
      {
        "kind": "table",
        "title": "Microsoft 365",
        "columns": [
          "Limit",
          "Published value"
        ],
        "rows": [
          [
            "Recipient rate limit",
            "10,000 recipients per day, on a 24-hour sliding window"
          ],
          [
            "Message rate limit",
            "30 messages per minute"
          ],
          [
            "Recipient limit per message",
            "500 by default, customisable from 1 to 1000"
          ]
        ],
        "note": "Microsoft, \"Troubleshoot outbound sending limits in Exchange Online\" (learn.microsoft.com), read 2026-10-13."
      },
      {
        "kind": "text",
        "title": "SMTP relay and API limits are different",
        "body": "Google Workspace publishes separate, higher ceilings for sending through the SMTP relay service and through the Gmail API - neither is blended into the per-user mailbox limits above.\n\nSMTP relay, per user: up to 10,000 messages and up to 10,000 unique recipients in a 24-hour period, with up to 100 recipients per SMTP transaction. SMTP relay, organisation-wide: up to 4.6 million recipients in a 24-hour period, or 319,444 in a 10-minute window - Google Workspace, \"Route outgoing SMTP relay messages through Google\", read 2026-10-13.\n\nGmail API: 500 recipients per message, 6,000 quota units per user per minute, 1,200,000 quota units per project per minute - a messages.send call costs 100 of those units. Google for Developers, \"Usage limits | Gmail\", read 2026-10-13."
      }
    ],
    "limits": [
      "These are each vendor's own published defaults, not a per-account ceiling - an account's real limit can be lower while it is new or on a trial plan, and neither vendor exposes a per-account figure to an outside tool.",
      "Nothing here is checked against any live account; both tables above are static data taken from each vendor’s own page."
    ]
  }
}

Sell the mailboxes behind the mail you are getting delivered, under your own brand.

Get started

Company names and logos are trademarks of their owners, shown only to identify each service.