Gmail's sending limits in 2026 depend on the account. A personal Gmail account can send up to 500 emails a day, and to no more than 500 recipients in one email. A paid Google Workspace account can send 2,000 messages a day per user, to at most 10,000 recipients in total, 3,000 of them external, with 500 messages a day on a trial. Workspace daily limits run over a rolling 24 hours, and an account that hits one cannot send for up to 24 hours. The Gmail API adds its own quotas on top, measured in quota units per minute, and they changed on 1 May 2026.
For cold email, the number that stops a mailbox is rarely the 2,000 a day. A mailbox sending 150 cold emails a day uses 7.5 percent of its Workspace allowance, yet if those emails go to personal Gmail inboxes, a single spam complaint that day puts its rate above Google's 0.3 percent line. We read every figure below on Google's own help and developer pages on 8 October 2026, and worked through what they mean for a mailbox that sends outreach.
What are Gmail's sending limits in 2026?
Google publishes different limits for each way you send. The figures that matter:
| How you send | Daily limit | Recipients per message | Source |
|---|---|---|---|
| Personal Gmail account | Up to 500 emails a day | 500 | Gmail Help |
| Google Workspace user | 2,000 messages a day; 1,500 for mail merge | 2,000 total, 500 external | Workspace Admin Help |
| Google Workspace trial | 500 messages a day, 500 external unique recipients | Not published separately | Workspace Admin Help |
| Gmail API | The account's own daily limits, plus API quotas | 500 | Gmail API usage limits |
| SMTP by POP or IMAP users | The Workspace user limits | 100 | Workspace Admin Help |
| SMTP relay service | 10,000 messages per user | 100 per SMTP transaction | Workspace Admin Help |
Three rules apply to Google Workspace accounts. Daily limits run over a rolling 24-hour period, not a calendar day. Google states that sending limits can change without notice. And once an account hits a limit, it cannot send new messages for up to 24 hours, although it still receives mail and works normally otherwise.
What are the Google Workspace sending limits?
Google Workspace accounts get higher limits than personal Gmail, with several counters running at once. Google's Workspace help lists these per user:
| Limit | Value |
|---|---|
| Messages per day | 2,000, or 1,500 for mail merge, 500 on a trial account |
| Recipients per message | 2,000 total, with a maximum of 500 external |
| Recipients per message over SMTP by POP or IMAP users | 100 |
| Recipients per message with the Gmail API | 500 |
| Total recipients per day | 10,000, or 1,500 for mail merge |
| External recipients per day | 3,000 |
| Unique recipients per day | 3,000, of which 2,000 external, 500 external on a trial |
| Messages auto-forwarded per day | 10,000, not counted in the daily sending limit |
| Auto-forward filters | 40 |
Recipients are counted each time a message goes out: five messages sent to ten addresses count as 50 total recipients but 10 unique recipients. Messages sent from aliases, by delegated users and by the vacation responder all count toward the user's limits.
Trial accounts. A new Workspace account starts on lower trial limits that do not rise during the trial. After you convert to a paid subscription, limits increase automatically once the domain has paid at least $100 in total, and Google says the increase can take up to 75 days after that threshold.
What are the Gmail API limits?
The Gmail API has two layers of limits. The first is the same per-user sending limits as any Workspace or Gmail account, plus a hard limit of 500 recipients per message. Google's Gmail API error guide states that the API enforces the standard daily sending limits, shared by all of a user's clients, so sending through the API gives you no extra daily volume. The second layer is the API's own usage quotas, counted in quota units.
Google updated those quotas on 1 May 2026. Cloud projects that used the API between November 2025 and April 2026 keep their previous quotas; projects created on or after 1 May 2026 get the new ones:
| Gmail API quota | Limit |
|---|---|
| Per minute, per project | 1,200,000 quota units |
| Per minute, per user, per project | 6,000 quota units |
| Daily billing threshold, per project | 80,000,000 quota units |
Each method costs a set number of units. Sending a message with messages.send or drafts.send costs 100 units, reading a message with messages.get costs 20, or 60 when you ask for the full, raw or html format, listing messages costs 5 and setting up push notifications with watch costs 100. At 6,000 units per user per minute, one user of a new project can make up to 60 send calls a minute if it makes no other calls, far faster than the daily sending limit allows anyway. When you do hit a time-based quota, Google recommends retrying with truncated exponential backoff rather than hammering the endpoint.
How much does the Gmail API cost?
Nothing today. Google's usage limits page says all standard use of the Gmail API is available at no additional cost, defines a per-project threshold of 80 million quota units per day below which usage is not billed, and plans to charge for usage beyond its quota limits later in 2026, with full billing details and at least 90 days' notice before any change takes effect. That threshold cannot be raised. 80 million units a day is 800,000 sends or 4 million messages.get calls per project, which a large inbox product can approach, so anyone building a high-volume email product on the Gmail API should watch that announcement.
Connecting other people's Gmail accounts brings a separate cost that has nothing to do with quotas. Apps that read mail use scopes Google classifies as restricted, and a public app using them must pass Google's verification, plus an annual security assessment when mail data passes through its servers. Our EmailEngine review covers what that involves for a self-hosted mailbox API, and our breakdown of Nylas pricing covers the managed alternative, where you verify your own Google app unless you pay for Nylas's pre-verified Google Shared App, an add-on to the annual Pro or Enterprise plan.
How do you send an email with the Gmail API?
You call users.messages.send with the whole email, headers included, as an RFC 2822 MIME message encoded in base64url in the raw field. The app needs the member's consent through OAuth, and Google's own samples request the gmail.send scope for it. Each call costs 100 quota units and counts against the account's daily sending limit like a message sent from Gmail itself. This is Google's Python sample from its sending guide, trimmed to the call:
import base64
from email.message import EmailMessage
import google.auth
from googleapiclient.discovery import build
creds, _ = google.auth.default()
service = build("gmail", "v1", credentials=creds)
message = EmailMessage()
message.set_content("This is automated draft mail")
message["To"] = "gduser1@workspacesamples.dev"
message["From"] = "gduser2@workspacesamples.dev"
message["Subject"] = "Automated draft"
encoded_message = base64.urlsafe_b64encode(message.as_bytes()).decode()
send_message = (
service.users()
.messages()
.send(userId="me", body={"raw": encoded_message})
.execute()
)
print(f'Message Id: {send_message["id"]}')A reply only joins the original conversation when its Subject matches and its References and In-Reply-To headers follow RFC 2822, so a follow-up sequence has to carry the Message-ID of the first email forward. The returned id proves Gmail accepted the request, not that the email reached the inbox, which is why the 200 response warning in the FAQ below matters for any automated sender. The threadId rule, the scopes and push notifications for replies are covered in our Gmail API guide.
Tools that send from a connected Gmail account make this call, or its SMTP equivalent, on your behalf. Swarmhit's Raw API, in early access, connects Gmail and Microsoft 365 mailboxes through your own OAuth app, sends with an Idempotency-Key so a retried call never sends twice, and threads replies with reply_to. Its email pricing starts at $39 for the first 125,000 emails a month. The daily limits above still apply to every mailbox, whichever API sends through it.
What are the Google Workspace SMTP relay limits?
The SMTP relay service routes mail from your own servers and applications through Google, and it has its own, higher limits. Each user can send up to 10,000 messages in 24 hours to no more than 10,000 unique recipients, with up to 100 recipients per SMTP transaction. Across the whole organization, Google allows up to 4.6 million non-unique recipients in 24 hours and 319,444 in any 10-minute window, and it may lower those limits based on your sending practices. For application mail at higher volume, our guide to email APIs compares the transactional senders built for it.
The relay is meant for on-premise devices and applications that generate outbound mail, such as ticketing systems and notifications. Using it to push cold email past the mailbox limits does not avoid the sender rules below, and it puts your whole organization's sending reputation at stake.
How do you know which Gmail limit you hit?
From the error, and each one calls for a different response. In the Gmail web interface, the account shows "You have reached a limit for sending mail" and cannot send new messages for up to 24 hours; personal accounts can usually send again within 1 to 24 hours. Code that sends over SMTP or the Gmail API gets a status instead. These are the codes Google documents on its Gmail API errors page and its Workspace SMTP error list:
| What your code receives | Limit you hit | What to do |
|---|---|---|
| SMTP 550 5.4.5 Daily user sending limit exceeded. | The Workspace user's daily sending limit | Stop sending from that mailbox until the rolling 24 hours clear |
| SMTP 550 5.4.5 Daily SMTP relay limit exceeded for user. | The SMTP relay limit for one user | Same, for that relay user |
| SMTP 550 5.7.1 Daily SMTP relay sending limit exceeded for this customer. | The relay limit for the whole organization | Stop relay traffic; every user on the domain is affected |
| API 429 Too many requests: User-rate limit exceeded (Mail sending) | The account's daily sending limit, shared with web and SMTP | Do not retry in a loop; Google says the error can last multiple hours |
| API 429 Too many requests: Too many concurrent requests for user | Parallel requests on one mailbox | Send fewer calls at once, then retry with backoff |
| API 403 userRateLimitExceeded | The per-user rate limit | Retry with exponential backoff |
| API 403 rateLimitExceeded | The project's rate limit | Retry with backoff, request a quota increase if it persists |
| API 403 dailyLimitExceeded | The project's daily API quota | Raise the quota in the Google Cloud project |
Two lines on Google's errors page matter more than the table. There can be a delay of several minutes before the API starts returning 429 errors once a mailbox passes its sending limit, and Google warns that a 200 response does not prove the email was sent. A sender that trusts the status code alone can keep queuing mail into a mailbox that has already stopped delivering it, so count your own sends per mailbox and stop well before the limit instead of waiting for the error.
In code, the rule is to back off on rate limits and park the mailbox on a sending limit:
import random, time
from googleapiclient.errors import HttpError
def send(service, message, max_attempts=5):
for attempt in range(max_attempts):
try:
return service.users().messages().send(userId="me", body=message).execute()
except HttpError as err:
body = err.content.decode(errors="ignore")
if err.resp.status == 429 and "Mail sending" in body:
raise # daily sending limit: park this mailbox, retrying extends nothing
if err.resp.status == 403 and "dailyLimitExceeded" in body:
raise # project quota: a backoff will not fix it
if err.resp.status in (403, 429):
time.sleep(min(2 ** attempt + random.random(), 64)) # truncated exponential backoff
continue
raiseExceeding the limits can carry heavier consequences. Google's Workspace help warns that an account exceeding its sending limits might be suspended, and that accounts that send spam might be permanently restricted from sending email. If a large number of your emails bounce because the addresses are invalid, a personal Gmail account can also be blocked from sending, and Google says you may be able to send again after 24 hours. That is why cold email lists get verified before they are sent.
Which rules apply when you send to Gmail users at volume?
Sending limits cap what a mailbox can send. Google's email sender guidelines decide whether that mail is delivered. Since February 2024, every sender to personal Gmail accounts must set up SPF or DKIM, have valid forward and reverse DNS, use TLS and keep the spam rate reported in Postmaster Tools below 0.3 percent. Senders of 5,000 or more messages a day to personal Gmail accounts, counted across the whole primary domain, must also authenticate with SPF, DKIM and DMARC, make it easy to unsubscribe, with one-click unsubscribe on marketing messages, and honour unsubscribe requests within 48 hours.
Google recommends keeping the spam rate below 0.10 percent and never reaching 0.30 percent. Since November 2025, Gmail has been ramping up enforcement, with temporary and permanent rejections for mail that does not meet the requirements. These formal requirements apply to mail sent to personal Gmail accounts, and most B2B cold email lands in Workspace-hosted inboxes instead, but spam complaints hurt a domain's reputation either way: a mailbox can stay well inside its 2,000 daily messages and still lose its deliverability if recipients mark its mail as spam.
What do Gmail's limits mean for cold email?
Take one paid Workspace mailbox that adds 50 new prospects a day to a three-step sequence. Once the sequence is running, each day carries 50 first emails, 50 second emails and 50 third emails, so 150 messages to 150 different external people. Against Google's counters, that is 7.5 percent of the 2,000 daily messages and 7.5 percent of the 2,000 unique external recipients. The same mailbox on a Workspace trial would use 30 percent of its 500 messages, and the trial limits do not rise until the domain has paid $100 and Google has applied the increase.
The spam rate is where that mailbox is fragile. Google computes it daily, as the share of messages delivered to the inbox of personal Gmail accounts that recipients mark as spam. If all 150 messages land in personal Gmail inboxes, the 0.3 percent ceiling works out to 0.45 complaints a day, about one complaint every two days, and the 0.10 percent recommendation allows roughly one a week. Doubling the volume to 300 a day doubles the complaints the same list produces. There is a catch for small senders: Postmaster Tools says data might be missing when a day's volume is too low, so a mailbox at this volume may never see the rate it is judged on. That arithmetic is why teams that run cold email at volume add mailboxes instead of volume: ten mailboxes at 150 a day send 1,500 messages with each one far from every Google counter, on separate registered domains so a reputation problem stays away from invoices and support mail. Mailboxes on the same domain still share its reputation, and new ones start with none, which is why Google's guidelines advise against sudden volume spikes.
Microsoft 365 mailboxes follow a different logic, with a daily cap on external recipients shared by the whole tenant, which our guide to Outlook sending limits works through. The rest is hygiene that every mailbox needs from the first send: SPF, DKIM and DMARC, a working unsubscribe, verified lists to keep bounces down, and a sequence that stops the moment someone replies or asks to stop. Setting up each of those pieces yourself, from the DNS records to reply detection, is covered step by step in how to build cold email infrastructure.
This is the layer cold email tools exist to run, and a part that is easy to underestimate when you build on the Gmail API directly. Our comparison of cold email software and our guide to Instantly alternatives cover the tools, and our outreach API comparison covers the APIs you can build on. AI-driven outreach multiplies the same risk, as our guide to AI SDRs explains.
On Swarmhit, the cold email API, in beta and opened workspace by workspace, runs that layer for you. One campaign spreads its volume across a mailbox pool, with one mailbox per lead for the whole thread, per-mailbox daily caps and today's usage readable in the API, sending windows, and bounce and complaint suppression. You can connect your own Google, Microsoft or IMAP mailboxes, or buy a domain and Google Workspace or Microsoft 365 mailboxes that arrive connected and already warming, and join campaigns once their warmup hold ends.
Spread cold email across mailboxes, not onto one
Swarmhit's cold email API runs mailbox pools, per-mailbox daily caps, sending windows and bounce suppression in the same campaigns as LinkedIn.
Cold email in beta from $59 a month for 125,000 sends, unlimited mailboxes; pricing may change during the beta.
FAQ
How many emails can I send per day with Gmail?
A personal Gmail account can send up to 500 emails a day, and to no more than 500 recipients in a single message. Google does not say exactly when the counter resets for personal accounts. If you hit the limit, Gmail shows an error, and Google says you should be able to send again within 1 to 24 hours. Workspace accounts get higher limits, counted over a rolling 24 hours.
How many emails can Google Workspace send per day?
A paid Google Workspace user can send 2,000 messages a day, or 1,500 through mail merge, to at most 10,000 total recipients, 3,000 external recipients and 3,000 unique recipients, 2,000 of them external. Trial accounts are limited to 500 messages a day. Limits rise after conversion once the domain has paid at least $100, which Google says can take up to 75 days.
What is the Gmail API rate limit?
Since 1 May 2026, the Gmail API allows 1,200,000 quota units per minute per Cloud project and 6,000 quota units per minute per user. Sending a message costs 100 units, so one user of a new project can make up to 60 send calls a minute. Projects that used the API between November 2025 and April 2026 keep their previous quotas. API sends still count against the account's daily sending limit.
Does sending through the Gmail API raise the daily limit?
No. Google's Gmail API error guide says the API enforces the standard daily sending limits, shared by all of a user's clients: API, web or SMTP. The API adds its own per-minute quotas and a 500-recipient cap per message, but it does not lift the 2,000 messages a day on Workspace or the 500 emails a day on personal Gmail.
How long does a Gmail sending limit last?
Up to 24 hours. Once an account hits a sending limit, it cannot send new messages for up to 24 hours, then the limit resets. Personal Gmail accounts can often send again within 1 to 24 hours. Workspace users can still receive mail and use other Google services meanwhile. Accounts that exceed their limits risk suspension, and accounts that send spam can be permanently restricted.
Does a 200 response from the Gmail API mean the email was sent?
No. Google's Gmail API errors page warns that a 200 response does not prove the email was sent, and that there can be a delay of several minutes before the API starts returning 429 errors after a mailbox passes its daily sending limit. Code that relies on status codes alone can keep sending into a mailbox that has stopped delivering. Keep your own count of sends per mailbox over a rolling 24 hours and stop well below the limit.
What is the Google Workspace SMTP relay limit?
The SMTP relay service allows each user up to 10,000 messages in 24 hours, to at most 10,000 unique recipients, with no more than 100 recipients per SMTP transaction. Across an organization, Google caps relay traffic at 4.6 million non-unique recipients in 24 hours and 319,444 in any 10-minute window, and can lower those limits based on your sending practices.




