Gmail Mail Merge Limit: 1,500 a Day, Not Your Full 2,000
The Gmail mail merge limit is 1,500 messages a day, and that number is not carved out of your 2,000-message allowance — it replaces it. Google's own documentation says the cap covers "both your regular and mail merge emails," so the ordinary mail you sent that morning is already spending the same 1,500.
The second half of the answer is the one almost nobody prints: multi-send also drops your daily recipient budget from 10,000 to 1,500. That is the number that actually stops a merge, and it stops it in a way the message cap never would.
The Gmail mail merge limit is really three counters, not one
Google's sending limits page tracks several separate quotas against a Workspace seat. Three of them decide whether a merge finishes:
| Counter | Ordinary sending | Mail merge (multi-send) |
|---|---|---|
| Messages per day | 2,000 | 1,500 |
| Total recipients per day | 10,000 | 1,500 |
| External recipients per day | 3,000 | 3,000 (not lowered, rarely reached) |
| Recipients per message | 2,000, of which 500 external | 1,500 in the To line |
Trial accounts sit far below all of this at 500 messages a day, and a consumer gmail.com address has no multi-send at all — mail merge is a Workspace feature, available on Workspace Individual, Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Standard and Education Plus. A Business Starter seat does not get the button.
The two counters that drop are the two that matter. The external-recipient limit and the per-message limit are wide enough that a normal merge never touches them.
The arithmetic: 500 messages and 8,500 recipient slots you paid for
Line up what a Business Standard seat is entitled to against what multi-send will let it spend:
- Messages: 2,000 entitled, 1,500 usable. 500 lost.
- Total recipients: 10,000 entitled, 1,500 usable. 8,500 lost.
The message gap is 25%. The recipient gap is 85%. Every roundup post you have read quotes the first number and ignores the second, which is why the advice "just split it over two days" keeps failing for people with lists over three thousand rows.
Why the recipient cap bites harder than the message cap
In ordinary Gmail, messages and recipients are cheap in different ways. One announcement addressed to 400 people costs you one message and 400 recipients. With 2,000 messages and 10,000 recipients to spend, the recipient pool is what you burn through, and the message pool is nearly impossible to exhaust.
Multi-send inverts that. The whole point of the feature is that every row becomes its own message with its own copy, so each recipient costs one message and one recipient. The two counters move in lockstep. Set both ceilings to 1,500 and they collapse into a single wall:
- 1,500 rows sent = 1,500 messages used and 1,500 recipients used. Both counters hit zero on the same send.
- Put one address in Cc or Bcc — multi-send allows exactly one — and that address costs a recipient slot on every single copy. A 1,400-row merge with your own address in Bcc spends 2,800 recipient slots against a 1,500 budget and stops roughly 750 rows in.
That last case is the one that generates the confused support threads. The merge did not fail at 1,500. It failed at about half of that, and the person had no idea a Bcc line was being multiplied by the row count.
Apps Script is not the escape hatch people think it is
The standard workaround on forums is to drop multi-send and drive Gmail from Apps Script instead. Check the quota page before you build it. Apps Script's documented "email recipients per day" is 1,500 for Google Workspace accounts and 100 for consumer accounts.
That is the identical ceiling. Rewriting a merge as a MailApp.sendEmail loop buys you scheduling, merge tags in the subject line, and real attachments — all things multi-send refuses — but it buys you exactly zero extra sends. Apps Script adds its own constraints on top: 50 recipients per message, 400 KB of body, 25 MB of attachments per message.
Which sending route draws from which pool
| Route | Ceiling that applies | Reaches the full 10,000? |
|---|---|---|
| Gmail multi-send (mail merge) | 1,500 messages / 1,500 recipients | No |
Apps Script (MailApp / GmailApp) |
1,500 recipients per day | No |
| Ordinary Gmail compose | 2,000 messages / 10,000 recipients | Yes, but not personalized |
| Gmail API | Account limits: 2,000 messages, 10,000 recipients, 500 recipients per message | Yes |
| SMTP relay | Separate relay quota; 100 recipients per SMTP transaction | Separate pool |
| An external sending platform on your own domain | The platform's limits, not Gmail's | Not applicable |
Only two routes actually unlock the 10,000-recipient budget you are paying for: the Gmail API, and moving the send off Gmail entirely. The API keeps your Workspace seat as the sender and spends from the ordinary pool, which is why it is the answer for anyone who needs personalized mail above 1,500 a day and wants it to keep coming from their own mailbox.
A 4,000-row list on one seat, day by day
Take a single Business Standard seat and a 4,000-row spreadsheet. No Cc, no Bcc.
Multi-send: 1,500 on day one, 1,500 on day two, 1,000 on day three. Three calendar days, and days one and two leave you unable to send ordinary mail from that address once the merge has run, because the merge already spent the shared 1,500.
Gmail API: 2,000 on day one, 2,000 on day two. Two days, and the recipient counter barely registers it — 4,000 against a 10,000 daily budget across the two days.
Ordinary compose: the list finishes in two days but nobody gets a personalized email, which was the reason for the merge.
The three-versus-two-day difference is not the interesting part. The interesting part is that on the multi-send path your mailbox is effectively out of service for normal correspondence on merge days, and on the API path it is not.
The restrictions that cost more than the cap does
Several multi-send rules bite before any counter does:
- No merge tags in the subject line. Personalization is body-only.
- No merge tags in hyperlinked text, and none in plain-text composition — multi-send does not work in plain text at all.
- No Schedule send and no Confidential mode. A merge goes now or not at all.
- No replies or forwards. Multi-send only works from a fresh compose window.
- One Cc or Bcc recipient maximum, and you cannot combine spreadsheet recipients with Cc/Bcc addressing.
- No sending from an alias or a second domain. The merge goes from the account you are signed into.
- Attachments are duplicated per recipient and charged to your storage, which is why Google tells you to link from Drive instead.
- An unsubscribe link is added automatically to the bottom of every merge email. You cannot remove it, and colleagues inside your organization cannot use it.
If any of those rules is a dealbreaker, the 1,500 cap is academic — you were leaving multi-send regardless.
Telling which limit you actually hit
When a send stops, the counter that stopped it is usually identifiable from the shape of the failure:
- It stopped at almost exactly 1,500 rows, first send of the day. The message cap. Split across days or change route.
- It stopped well short of 1,500 and you had a Cc or Bcc address. The recipient cap, multiplied by your row count. Remove the Bcc and re-run the remainder.
- It stopped short and you sent ordinary mail earlier. The shared counter. Whatever you sent that morning came out of the same 1,500.
- It stopped around 500. You are on a trial account, or a consumer address with no multi-send at all.
- The multi-send toggle is missing entirely. Edition problem, not a limit problem — Business Starter and personal Gmail do not have the feature.
Counters reset on a rolling 24-hour basis rather than at midnight, so an account that hit the wall at 3pm is not clear again at 9am the next morning. It is clear 24 hours after the sends that spent the quota.
Sources
- Gmail sending limits in Google Workspace — the 2,000 / 10,000 / 3,000 figures and the mail merge exceptions
- Send personalized emails with mail merge — the 1,500 cap, eligible editions and the multi-send restrictions
- Apps Script quotas for Google Services — email recipients per day for consumer and Workspace accounts
- SMTP relay service error messages — the 100-recipient limit per SMTP transaction
Frequently asked questions
What is the Gmail mail merge limit per day?
Gmail's mail merge (multi-send) is capped at 1,500 emails per day on eligible Google Workspace accounts. Google states that the 1,500 includes both your regular and your mail merge emails, so ordinary mail sent from the same address that day comes out of the same allowance.
Why is my mail merge limit 1,500 when my account allows 2,000 emails a day?
The 2,000-message figure is the ordinary Gmail sending limit for a Workspace account, and multi-send runs under a separate, lower ceiling of 1,500. Multi-send also cuts the daily total-recipient budget from 10,000 to 1,500, so you lose 500 messages and 8,500 recipient slots compared with ordinary sending.
Does using Apps Script get around the Gmail mail merge limit?
No. Apps Script's documented quota is 1,500 email recipients per day for Google Workspace accounts and 100 per day for consumer accounts, which is the same ceiling as multi-send. Apps Script gives you scheduling, subject-line merge tags and real attachments, but no extra sending volume.
Which Google Workspace editions include mail merge?
Mail merge is available on Workspace Individual, Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Standard and Education Plus. Business Starter and free consumer gmail.com accounts do not have the multi-send feature at all.
Why did my mail merge stop well before 1,500 emails?
The most common cause is a Cc or Bcc address, which is duplicated on every copy and charged against the 1,500 daily recipient budget once per row. A 1,400-row merge with one address in Bcc spends about 2,800 recipient slots and stops roughly halfway through.
Do Gmail sending limits reset at midnight?
No, they reset on a rolling 24-hour basis rather than at a fixed clock time. An account that hit the wall in the afternoon becomes clear 24 hours after the sends that spent the quota, not first thing the next morning.