Gmail Sending Limits in 2026: Daily Caps for Gmail and Workspace

Personal Gmail accounts can send to up to 500 recipients per email and 500 emails per day. Google Workspace users get 2,000 messages per day (500 on a trial account). Cross a limit and Gmail blocks new sends, and Google says you should be able to send again within 1 to 24 hours. Workspace adds a second layer: caps on recipients, external recipients, and unique recipients, which change by channel (web, SMTP, relay, API). The numbers below come only from Google’s own help, admin, and developer pages, checked in October 2026.

Gmail sending limits at a glance (as of October 2026)

Google publishes personal-account limits in Gmail Help and Workspace limits on its Workspace sending limits page. Gmail Help gives only two numbers for personal accounts, so the other cells say so instead of guessing.

Limit	Personal Gmail	Google Workspace
Messages per day	500 emails in a day	2,000 (1,500 for mail merge, 500 for trial accounts)
Recipients per message	500	2,000 total, of which at most 500 external
Recipients per message over SMTP, POP, or IMAP	Not published	100
Recipients per message through the Gmail API	Not published	500
Total recipients per day	Not published	10,000 (1,500 for mail merge)
External recipients per day	Not published	3,000
Unique recipients per day	Not published	3,000 total, 2,000 external (500 external for trial accounts)
Auto-forwarded messages	Not published	10,000, not counted toward the daily sending limit
Auto-forward filters	Not published	40

Two details trip people up. Google states that “Limits aren’t increased during the free trial period,” and that Workspace limits apply over a rolling 24-hour period rather than at a fixed time of day. Personal Gmail Help does not say how its window works.

How the limits change by sending channel

The same mailbox can hit different ceilings depending on how the message leaves it. Here is what Google documents for each route.

Channel	What Google documents
Gmail web and mobile app	Per-user limits from the table above
smtp.gmail.com (see Gmail SMTP settings)	“The sending limit is 2,000 messages per day,” and 100 recipients per message for SMTP users
smtp-relay.gmail.com (an SMTP relay)	Each user “can relay messages up to 10,000 recipients per day,” with a 100-recipient limit per SMTP transaction
Gmail API	500 recipients per message; messages.send costs 100 quota units
Restricted server (aspmx.l.google.com)	“Google Workspace per-user limits apply”

The SMTP and relay figures come from Google’s article on sending email from a printer, scanner, or app and the SMTP relay error messages page. To send more than 100 recipients through the relay, Google says to “start another transaction (new SMTP connection or RSET command)”. That is normal batching, not a workaround for the daily cap.

Gmail API quota units

The API has its own budget on top of the mailbox limits. Google’s Gmail API usage limits list 1,200,000 quota units per minute per project and 6,000 quota units per minute per user per project. Each messages.send call consumes 100 quota units. These are rate limits for API calls, so they sit alongside the 2,000 messages per day Workspace cap, not in place of it. The page does not state a message size limit for messages.send, so this guide does not either.

Attachments

For personal accounts, Gmail Help says “the limit is 25 MB.” If the total is larger, “Gmail automatically removes the attachment and adds it as a Google Drive link in the email.” For work and school accounts, the Workspace administrator sets attachment sending and receiving limits, and Google’s Workspace limits page notes that Enterprise Plus allows up to 50 MB (web only).

What happens when you hit the limit

In the Gmail web app, you see “You have reached a limit for sending mail,” or bounce messages saying “Messages you sent couldn’t be delivered.” Google says you should be able to send again within 1 to 24 hours. For Workspace, “users can’t send new messages for up to 24 hours” but they can still receive mail and use other services.

In an app or script, you get an SMTP reply instead. Google’s SMTP error reference documents these:

Code	Google’s message (shortened)	Meaning
550 5.4.5	“Daily user sending limit exceeded.”	The mailbox used its daily quota
550 5.4.5 (relay)	“Daily SMTP relay limit exceeded for user.”	The relay user used its daily quota
421 4.7.28	“Gmail has detected an unusual rate of email… temporarily rate limited.”	Sending speed or volume looks abnormal
421 4.7.0	“…email sent from your IP address has been temporarily rate limited.”	Sending IP has no PTR record or a mismatched forward DNS entry
450 4.2.1	“The user you are trying to contact is receiving email too quickly.”	The recipient is being throttled, not you
452 4.5.3	“Domain policy size per transaction exceeded…”	Too many recipients in one transaction

Treat 5xx replies as a stop signal and 4xx replies as “retry later with backoff.” Retrying a 550 5.4.5 in a loop will not shorten the block, and Google does not document any way to end it early. If a message is accepted and later returned, the problem shows up as a bounce-back message instead of an SMTP reply.

Google also does not document a way to raise the personal-account cap. Workspace limits are the published ceiling for paid accounts, so teams that need more volume should change channel, not mailbox.

The daily cap is not the only ceiling

Staying under 500 or 2,000 messages does not guarantee delivery to Gmail inboxes. Google’s email sender guidelines apply separately, starting February 1, 2024, to every sender writing to Gmail accounts:

• Set up SPF or DKIM for your sending domains, keep valid forward and reverse DNS records, and use a TLS connection.
• Keep the spam rate below 0.3% in Postmaster Tools.
• If you send “more than 5,000 messages per day to Gmail accounts,” you are a bulk sender and must set up SPF, DKIM, and DMARC, align the From domain with SPF or DKIM, and support one-click unsubscribe for marketing and subscribed messages.

Google’s page does not say that a new account sending near its cap will be suspended, so treat that as a risk to manage rather than a rule. A fresh domain that jumps straight to hundreds of messages a day has no history behind it, which is why you should warm up a new domain and watch sender reputation from the first send. Authentication basics are covered in SPF, DKIM, and DMARC, and the wider picture is in email deliverability best practices.

When Gmail is the wrong tool

A mailbox is built for a person writing messages. It is a poor base for anything that must keep running, because a hit limit means up to 24 hours without sending. Microsoft 365 mailboxes have the same problem, with their own caps listed in the Office 365 SMTP settings guide.

Option	Built for	Limits model
Gmail or Workspace mailbox	Individual and small-team correspondence	Per-user daily messages and recipients
Workspace SMTP relay	Devices and internal apps in a Workspace domain	Per-user recipients per day, 100 per transaction
Dedicated email API or sending service	Product, lifecycle, and bulk email	Set by the provider and your plan, with deliverability tooling

Move transactional mail, product notifications, and newsletters off personal inboxes. An email API or a transactional email service is designed for that volume, and Coldletter is one option in that category. Cold outbound from a real mailbox is a legitimate channel at low volume. Spreading sends across more inboxes to dodge the caps is not, and Google’s guidelines apply to every one of them.

Frequently Asked Questions