Gmail Sending Limits, and the Day Your Desk Hits One

A paid Google Workspace account can send 2,000 messages a day. A personal Gmail account can send 500. Go past either and Gmail stops you sending for up to 24 hours, while everything else about the account carries on working perfectly normally. That is the whole answer, and it is almost never the limit that stops a support desk.

The one that stops you is usually a smaller number sitting somewhere you were not looking, and you find it on a morning when you can least afford to, generally the morning after something went wrong and the queue doubled overnight. Nobody plans for it. There is no point in the growing of a support team where somebody sits down and works out the ceiling, on account of the ceiling being invisible right up until the hour it is not, and then it is the only thing in the room, and that is the size of the thing.

We sell help desk software, so you may take the rest of this with whatever salt you think it wants. Fair is fair though, a good half of this page is about a ceiling that our own product does not lift for you, and we would sooner have that said early than have you find it out on us.

What Gmail actually counts when it counts a message

Not what you would think, truth be told, and most of the trouble lives down inside the gap between the two of them.

It counts recipients, not conversations. A reply to one customer is one message against your daily total. A reply to one customer with their colleague copied in is still one message, but it is two against your recipient total, and those are two different ceilings running at the same time in the background with no dashboard anywhere showing you either of them. Then the automatic acknowledgement that goes out when the mail lands, that is another one. The notification to the person you assigned it to, if that goes out as mail, another again. So a single ticket that a customer would describe as one conversation is quite comfortably four or five against a number you have never once looked at, and the rest of it goes the very same way.

And the counting is per user, not per company. This is the part worth sitting with, because it works backwards to how people assume it works. Buying more seats does not divide a company ceiling between more people, it gives every one of them their own 2,000, so on paper the ceiling goes up every time you hire. What actually happens is that the sending does not spread out the way the seats do. One person answers most of the mail, on account of one person always answers most of the mail, and that person meets the ceiling on their own while four colleagues sit well underneath theirs with capacity to spare that cannot be lent out. Nobody designed that. It falls out of the arithmetic every time, and no amount of paying for more seats sorts it out its self.

How many messages a day you actually get

Here is the whole documented set, pulled from Google’s own pages on 26 August 2026 rather than from anybody’s blog about them. Google moves these occasionally and the date is on it for that reason.

Two rows in that table do work the other eight do not, and neither of them is the 2,000.

Why the limit that stops you is rarely the one you read about

Because the 2,000 is the one written for a person sending mail, and a support desk is not a person sending mail, it is a system sending mail on a person’s behalf, and systems trip different wires.

Take the third row. Over SMTP, POP or IMAP the ceiling is 100 recipients on a single message, not 2,000, and that is a twentieth of the headline number. A great many desks are connected exactly that way without anybody having decided to, on account of SMTP being what the setup guide said to use, and it works flawlessly for a year and a half while every mail goes to one person. Then somebody sends the outage note. Or the seasonal one, the we-are-closed-for-the-bank-holiday one, and it goes to a list, and the list went and grew past a hundred sometime in the spring without a single soul noticing it happen. That is the wire. The mail does not go, and it does not go and tell you why either. And the error you get back does not say your list is too long for the protocol you happen to be connected over, it says something short and unhelpful about the sending limit, and so half the internet then tells you that you have hit your 2,000, which you have not, and you go looking in the wrong place for the rest of the afternoon.

The other row is the 40. Forty filters on an account, and filters are how a support@ address gets sorted before anybody looks at it, one filter per sender or per subject or per label, which is a system that runs its self beautifully until the day it quietly stops being able to. Forty sounds enormous when you set the fourth one up. It is not enormous two years in, with a filter for each of your bigger customers and each of the standing tickets and each of the addresses that ought to skip the inbox entirely, and the fortieth one is added by somebody in a hurry and the forty-first quietly does not exist. Nothing announces that either, mind you. Mail simply stops being sorted the way you thought it was, and it keeps arriving, and it looks for all the world like nothing whatsoever has changed, which is the worst half of it.

There is a third one nobody quotes and it is the auto-forward row, though this one is good news for once. Automatic forwards run to 10,000 messages and Google does not count them against your daily sending total. So a desk that forwards from one address into another is not eating its send quota to do it, which is genuinely useful to know and which almost no guide on this subject mentions at all.

What happens on the morning it stops

You find out from a person, not from a system, and that is most of the problem with it.

Somebody says a mail did not go. You check and it is sitting there looking sent, or it is sitting there looking not sent, and either way the account is fine, the mail is coming in perfectly normally, the calendar works, everything works, it is only the sending that has gone. Which is the worst possible shape for a fault to have, seeing as it looks less like a fault than anything else that could go wrong with you that morning. Nothing is down. Nothing is broken. The account is not the least bit ill. One person cannot reply to customers for the rest of the day and the rest of the team can, and it takes a while for anybody to join those two facts up.

The lock lasts up to 24 hours and it clears on its own, and there is no button anywhere to make it clear sooner. That is the honest state of it. The account keeps working for everything else the whole time, which is the detail that sends people off diagnosing the wrong thing for an hour or two before somebody thinks to check the quota, and by then the queue has done what queues do.

And it lands on your best person first. Not randomly, and not on the newest either, but on whoever has been answering the most mail all along, which is of course the one person you can least afford to have go quiet on you for a day. That is not bad luck, mind you, it is just what a per-user ceiling goes and does to a team where the work is not spread evenly, and the work is never spread evenly, and that is the shape of it on most desks we have ever looked at.

A Tuesday, walked through properly

Say a payment integration goes wrong on a Monday evening. Not catastrophically, it just starts declining a fair share of cards, and by half eight the following morning you have nineteen mails about it and they keep coming.

Your senior person takes them, on account of them being the one who knows what the payment integration even is. Each customer gets a first reply. That is nineteen messages before anything is fixed. Six of those customers have their finance person copied in, so the recipient count is running ahead of the message count already. The desk sends an automatic acknowledgement on arrival, so double the nineteen. Somebody sensibly decides to get ahead of it and mails everybody who transacted that morning, which is a list of two hundred and forty, and if that goes over SMTP it does not go at all, it stops at the hundred.

By eleven the integration is fixed and now every one of those conversations wants a second reply saying so. By two in the afternoon your senior person has personally sent somewhere north of 400 messages on a day that felt, to them, like one incident and about forty conversations. They are nowhere near 2,000, mind you, not the least bit near it. They may well be past the external recipient number, depending on how the copies fell, and if they went and hit the hundred on that bulk mail they have already lost an hour to a message that never left.

None of that is a big day by the standards of a support desk. That is one bad Tuesday, and the arithmetic gets there on its own, without anybody going and doing a single thing wrong.

Why delegation looks like the fix and is not quite

The obvious answer, once you have met the ceiling the once, is to spread the sending over more accounts than the one, and Gmail does have delegation built into it for something fairly close to that very purpose.

The numbers on it are more generous than most people think, and here a figure you will read everywhere turns out to be simply out of date, mind you. Guides all over this subject quote a limit of 25 delegates. Google’s own documentation on 26 August 2026 says 10 delegates on a personal account and 1,000 on a work or school account, with about 40 able to be in the mailbox at the same time under typical use. So the delegate count is not your problem and it was probably never going to be.

The problem is what the customer sees. When a delegate sends from a delegated mailbox, Google shows the recipient the delegate’s own address, not the shared one. Which is fine, arguably better than fine, right up until you are trying to keep one address as the thing customers reply to, and now the replies come back to five different people’s personal mailboxes and the shared one goes quiet and nobody can find the thread from last March without asking three colleagues who is holding it. You have not moved the ceiling. You have gone and moved the record instead, which is the very thing you were trying to protect, and that is the trap in the whole of it.

That is the seam, and it is the same seam a shared inbox is for. If you are weighing whether Gmail’s own shared tooling covers you, the Collaborative Inbox guide walks the setup and the five places it stops, and this page will not re-run that argument here.

Where we come into this, and it is a smaller part than you would like

We make Maxdesk, which turns a support@ address into a proper queue, with a shared inbox that shows who has got what, an audit trail on every change so the question of who replied has an answer, and no-code rules that route and tag without a filter slot being spent on it. That last one is the honest overlap with this page, truth be told. Routing that lives in the desk rather than in Gmail’s 40 filters is routing that does not run out at forty, and it is visible to the whole team instead of living inside one person’s account settings where nobody else can see it or fix it.

Billing is per workspace rather than per agent, which is the thing we are actually different about. Free is $0 with unlimited agents and unlimited tickets, and it carries supporting ads, our branding on outbound mail and a 3-month rolling history. Pro is $20 a month on the workspace and Elite is $99. Nobody counts your agents at any point, so putting the warehouse and the accounts person on the desk costs you nothing at all, and that matters here a good deal more than it looks like it does on a first reading of it. The ceiling is per user. So the cheapest way to stop concentrating your sending is to stop concentrating the people doing it, and a per-agent bill is the thing that quietly stops you.

What this does not do for you, said plainly

It does not lift Google’s ceiling. Nothing does, and nothing is going to.

If your desk sends through your own Google Workspace account, every number in that table up above still applies exactly as written, and any tool telling you otherwise is telling you something about Google’s infrastructure that is not theirs to tell. What software can do is make you meet the ceiling later, and see it coming before you get there. It spreads who does the sending. It keeps your routing out of those 40 filter slots. And it stops a person sending four mails on an occasion where the system could have sent the one. That is a real difference and it is a smaller one than the marketing on this subject generally suggests, truth be told.

It also does not make leaving Gmail the right answer. Plenty of desks should stay exactly where they are. If one person handles the mail and the volume is genuinely small, and nobody has ever had to prove who said what to a customer, then Gmail with a few filters is doing a perfectly good job of it. Moving would cost you a fortnight and buy you very little. We have written the leaving argument properly elsewhere and it is not the argument on this page.

And the thing this page cannot do at all is tell you where you currently are against any of those numbers, on account of Google not publishing a running total anywhere you can go and read it. There is no gauge. You find out you were near the limit by not being near it any more, which is a poor way to run anything and is nonetheless how it works at present.

Where to start, if any of that sounded familiar

Pick one address to start with, whichever one your customers actually write to, and leave the rest of them alone for the minute.

Count what leaves it in a normal week and be honest about what counts, meaning every reply, every acknowledgement, every notification that goes out as mail, and every copied-in colleague as a separate recipient. Then look at two things and only two. How you are connected, on account of SMTP quietly capping you at 100 recipients on a message where the web ceiling is 2,000. And how many filters that account is carrying, on account of 40 being the end of it and nothing warning you at 39.

If both of those come back comfortable, you are grand and you can put this page down and think no more of it. If either one is close, you have found the thing that is going to stop you, and you have found it on an ordinary week rather than on the Tuesday the payments broke, which is a considerably better day to find it on.

Common questions about Gmail sending limits

How many emails can I send from Gmail in one day?
A paid Google Workspace account can send 2,000 messages a day. Personal Gmail accounts and Workspace trial accounts are both capped at 500. Mail merge is separately capped at 1,500. These are Google’s published figures as of 26 August 2026.

What happens when you hit the Gmail sending limit?
Gmail returns an error and stops you sending new messages for up to 24 hours. Everything else keeps working normally, so incoming mail still arrives and the rest of the account is unaffected. The limit resets its self and there is no way to clear it early.

Is the Gmail sending limit per user or per organisation?
Per user. Every account gets its own allowance, so the company ceiling rises as you add people. That sounds helpful and often is not, because sending concentrates on whoever answers the most mail, and that person can hit their own ceiling while colleagues sit well under theirs.

Why did I hit a limit at 100 recipients rather than 2,000?
Because the message went over SMTP, POP or IMAP, where the cap is 100 recipients per message rather than the 2,000 that applies in the Gmail web interface. The Gmail API allows 500. The error message does not name the protocol, which is why this one gets misdiagnosed so often.

How many delegates can a Gmail mailbox have?
Ten on a personal account and 1,000 on a work or school account, with around 40 able to use it at the same time under typical use. The commonly quoted figure of 25 does not match Google’s current documentation. Note that recipients see the delegate’s own address on anything they send.

Do automatic forwards count against the daily sending limit?
No. Google allows 10,000 automatic forwards and does not count them against the daily sending total. Mail filters on a single account are capped at 40, which is the limit far more likely to affect a support address.