Gmail Daily Sending Limits: Free vs Google Workspace

The Gmail daily sending limit that trips most people is not really one number. It is four numbers Google applies at the same time, on a rolling 24-hour window, and the one that catches you depends on which account you send from and which path the message takes. A free @gmail.com address runs different ceilings than a paid Google Workspace seat, and a message sent from the web hits a different per-message cap than the same message sent through SMTP or the Gmail API.

This post separates those four limits, lists the exact figures from Google's own current limits pages, and shows which account fits which job. All numbers below are verified against Google's live documentation as of August 2026 — Google has moved these thresholds before and will move them again, so verify against the source before quoting one.

The verdict, up front#

If your account is a paid Google Workspace seat, you have 2,000 messages per day per user. If it is a free @gmail.com address, you have 500 per day and about 500 recipients per any single message. Neither number is really "per day" in the calendar sense — both roll on a 24-hour window, so the counter releases one message at a time as each send you made ages past its 24-hour mark, rather than resetting all at once at midnight.

Neither number is a Gmail-the-client limit either. It is a limit on the underlying Google account, so the same cap applies whether you send from mail.google.com, from the Gmail mobile app, from Apple Mail over IMAP, from Outlook over SMTP, or from any third-party client connected to your Gmail box. Switching apps does not raise your ceiling. Only paying for Workspace or moving to a purpose-built sending platform does.

The four limits people conflate — and which one actually stops you — are:

• Messages per day: how many separate sends you can queue in a rolling 24 hours.
• Recipients per message: how wide any one send can go across To, Cc and Bcc combined.
• Unique recipients per day: how many distinct addresses you can touch in a rolling day, even across many sends.
• External recipients per day: how many of those unique addresses can sit outside your own domain.

The one that catches you first is usually not the one you were counting. A user sending small newsletters trips on unique-recipients-per-day well before messages-per-day. A user sending long personal replies to a handful of people almost never trips anything at all. And a user running mail-merge templates from a Workspace account hits a fifth, separate ceiling — 1,500 recipients per day for merge, not the 10,000 the normal Send flow allows.

Gmail free vs Google Workspace: the numbers side by side#

The table below is the whole comparison in one screen. Every number comes from Google's own limits pages as at August 2026 — the free-Gmail figures from the consumer help doc, the Workspace figures from the Workspace Admin knowledge base — and each one is subject to change on Google's side without notice. Recheck before you plan a campaign against a specific ceiling.

Where a free Gmail address wins#

Free Gmail wins on one dimension, and it is worth naming plainly: it costs nothing. For a person who sends a modest volume of one-to-one mail — replies, receipts, the occasional group thread with friends — the 500-message ceiling is far more than they will ever touch in a rolling day, and the storage that comes with the account is enough for years of ordinary correspondence. Paying for a Workspace seat to move the daily limit from 500 to 2,000 buys nothing if you never went past 200.

Free Gmail also wins on setup. There is no admin console, no MX record change, no domain-verification checklist. You have an address the moment you sign up, and it works from every client that speaks IMAP or SMTP with an app-specific password. For a personal address, that is often the whole requirement.

What free Gmail does not win on — and this is the honest version — is anything that involves send volume, a custom domain, or admin control. As soon as you need to send from [email protected], or you need to reach more than 500 unique addresses across a day, or your team needs shared calendars and audit logs, the free tier is the wrong answer. Not slightly wrong; wrong in a way that cannot be tuned around.

Where a Google Workspace seat wins#

Workspace wins on send capacity, unique-recipient reach, and per-message width, all in one move. The daily cap goes from 500 to 2,000 messages, the recipients-per-message ceiling goes from 500 to 2,000 (with the "no more than 500 external" caveat), and the total recipients across the day goes from 500 to 10,000. That last number is the one that matters for anyone running scheduled campaigns or heavy sales outreach: a small newsletter list of 3,000 subscribers can be sent to in a single day on Workspace and never on free Gmail.

Workspace also wins on the paths those messages can travel. The Gmail API accepts up to 500 recipients per single message. A POP, IMAP or SMTP client caps at 100 per message — the number most people miss, because their client happily lets them type 200 addresses into the To field and only Google enforces the cut. The Workspace SMTP relay service, which is a separate thing from a user sending their own mail, caps at 10,000 messages per user per day, up to 4.6 million recipients daily across the whole organization, with a per-transaction limit of 100 recipients. Those are the numbers to plan against if you are wiring a CRM, an application, or a transactional service to Google's infrastructure rather than sending mail by hand.

The last thing Workspace wins on is admin visibility. On free Gmail, "did I hit a limit today?" is a question only the sender can answer, and the answer arrives as a delivery failure. On Workspace, that is a report a domain admin can run — which matters the day one seat quietly exceeds a threshold and the whole team's ability to send starts to look flaky.

Pricing shape — verify the current number before you buy#

We do not print live prices for Google Workspace in this post because Google moves them, publishes different tiers in different regions, and adds Gemini and other AI features on top — every third-party number goes stale within a quarter. What we can describe honestly is the packaging shape.

Free Gmail is exactly that: free, funded by the rest of Google's business, with no paid tier that exists for a personal @gmail.com address. Google Workspace is per-user-per-month with a choice of monthly or annual commitment, sold in tiers (Business Starter, Business Standard, Business Plus, Enterprise) that step storage, Meet capacity and admin controls rather than the send limits — the ceilings in the table above apply from the entry-level paid seat upward, unchanged across tiers. There is a separate Google Workspace Individual plan aimed at solo users with a custom domain, and Education and Nonprofit tiers with their own pricing.

Check the current per-seat number on Google's own pricing page before you commit — that is the only source we would trust for a figure this fluid, and it is the source Google is most incentivized to keep current.

Who each account is genuinely for#

Free Gmail is for a person, and a person only. That includes freelancers early in their career who have not yet needed a business address, students, and anyone whose email life is a mix of personal correspondence and occasional inquiries. If your calendar is a personal Google Calendar and your address ends in @gmail.com, you are the reader for whom Workspace is not yet worth the money.

Google Workspace is for anything with a domain. A single-person business that sends invoices from [email protected] is already the customer, not because their volume is high but because a personal-looking address at that stage is a conversion tax on every proposal. A startup with two engineers is the customer because a shared calendar, shared drive and a directory that a third engineer can be added to is worth the seat price on the first month it saves an hour. A support team is the customer because the 10,000-recipient daily cap and the SMTP relay are what make outbound at reasonable scale work at all.

The reader who should stop here and go buy something else entirely is anyone whose real job is bulk send: a newsletter operator with 20,000 subscribers, a transactional-mail team wiring a receipt on every checkout, or a marketing team sending a campaign that will breach 10,000 recipients in one day. Workspace is a mail server for humans, not an ESP; SendGrid, Postmark, Amazon SES and Mailgun exist because sending at scale is a domain of its own with deliverability, warm-up, bounce handling and unsubscribe hygiene concerns Google is not designed to solve. Use Workspace for the mail your humans write. Use a real ESP for the mail your systems send.

This is the dimension we concede without hedging: neither Gmail account will beat a dedicated sending platform on published volume, deliverability tooling or per-message cost at scale. The honest sequence is to pair Workspace with an ESP rather than argue the two.

How the rolling 24-hour window actually works#

Almost every write-up of Gmail's limit describes it as a daily cap that resets at midnight. That is wrong, and it is the source of most of the confusion around this topic. Google's counter is not a calendar; it is a rolling 24-hour window. If you sent your 500th message at 3 p.m. yesterday, you cannot send again until 3 p.m. today — waiting until midnight does nothing at all.

The corollary matters more. If you spread your sends across the day instead of firing them in one batch, the counter is releasing headroom the whole time as older messages age out of the window. A user who sends 400 replies steadily between 9 a.m. and 5 p.m. rarely trips anything, because by the time they are approaching the ceiling their earlier sends are already dropping off. A user who sends 500 replies in a single hour hits the cap and stays hit for hours, because nothing ages out during a batch.

That is why the recovery instruction Google publishes for the limit-exceeded error is "try again in 1 to 24 hours" rather than "wait until midnight." A user who hit the cap at 10 a.m. can send again by 10 a.m. the next day — one message at a time, as the head of the queue crosses the 24-hour mark. And the practical upshot: pacing is a real defense against ever seeing the limit. Front-loading is what triggers it.

A third option: the client sitting on top of the account#

The comparison above is between two Google accounts, and no email client changes the numbers on either. Every limit is enforced on the underlying Google account, not on the app you happen to be typing into — that is why switching from mail.google.com to Apple Mail, Outlook, Thunderbird, Superhuman Mail or Shortwave does not raise the ceiling by a single message. So the third position on this page is not another account type. It is the client sitting on top of whichever account you already have.

That is what we do, and we build AI Emaily so we should say so plainly. It is an AI-native email client that connects to Gmail and Google Workspace over the OAuth Google publishes, and to Outlook and any IMAP account too. It reads and drafts and helps you triage mail. It does not change what Google will let a message do once you press send. If you were hitting the 500-message-per-day ceiling before installing AI Emaily, you will still hit it — the account is the account.

Where a good client does help is upstream of the limit, in the shape of your sending pattern. The behaviour that trips a personal Gmail account most often is not a genuine 500-send day; it is 300 near-identical replies typed and fired through the same address in one afternoon, at which point Google's abuse detection tightens the ceiling below the published number. A client that drafts on your side, batches nothing, and holds each reply for approval spreads the send pattern naturally and keeps you in the shape Google's reputation systems reward. Copilot mode in AI Emaily is exactly that — one-tap approval on every draft — and Autopilot only sends within rules you set, so a rule that caps auto-sends per hour is a real safety belt against tripping a daily limit by accident.

We are not the right answer if your job is sending 20,000 marketing emails a day. A dedicated ESP is. We are the right answer if you live inside one Gmail or Workspace inbox and the limit only becomes visible on the day you have an unusually large stack of individual replies to write — which is the situation the daily-limit search almost always describes. If you want to see the shape of it, there is a 7-day free trial on Pro or Autopilot; the current numbers sit on the AI Emaily pricing page and are the only source we would trust to be current.

Putting the four limits into one rule of thumb#

The distinction that decides which limit matters is what the send actually is. One-to-one replies are constrained almost exclusively by messages-per-day, because each send has one recipient. Small campaigns of 50 to 500 people are constrained by unique-recipients-per-day, because a handful of sends can burn through the 3,000-unique ceiling on Workspace or the 500 on free Gmail. Anything scripted or API-driven is constrained first by recipients-per-message, because the Gmail API caps a single request at 500 recipients and SMTP at 100.

In practice, plan against the specific limit that fits the send, not against the biggest number you can find on the page. "2,000 per day" is real, but so is "3,000 unique recipients per day," "500 external recipients per single message," and "1,500 total for mail merge." The one you hit first is the one that matters, and the one you hit first depends on the shape of your day.