Zoho Mail Sending Limits: What They Are and How to Stay Under

The short answer
Zoho Mail has no flat daily number. It caps external sends to roughly 50–500 emails per hour, dynamically, based on sender reputation, plus a per-message recipient cap (100 free, 150 paid). Internal mail allows up to 1,000/hour. Exceed either limit and sending pauses for about an hour; receiving keeps working throughout.
Zoho Mail sending limits explained: hourly caps, recipient limits, and how to avoid a blocked outbox.
On this page
Zoho Mail doesn't cap you at a fixed number of emails per day. It caps you at a rolling hourly rate — roughly 50 to 500 external emails an hour — and that number moves depending on your account's sender reputation, not your plan.
A brand-new mailbox with no sending history sits at the low end of that range. An established account with clean bounce rates and engaged recipients can send toward the high end. Layered on top is a per-message recipient limit — 100 combined to/cc/bcc addresses on a free account, 150 on a paid one — and a separate, much roomier allowance for mail that stays inside your own domain.
This post covers what actually throttles you, why the number isn't fixed, and what to do the moment Zoho stops accepting your outgoing mail.
It matters because the search for a fixed number sends people down the wrong path. Forums are full of old threads quoting "1,000 a day" or "500 a day," and those numbers were true for someone, on some plan, on some date — but treating them as a rule you can plan around is how a legitimate sender ends up blocked mid-campaign with no warning.
Before you start#
A few things worth knowing before you go looking for a setting to change, because the honest answer is that there usually isn't one.
- Zoho Mail's outgoing limits are reputation-based, not a number stored in your account settings — there's no dial in the admin console that raises it on request.
- Personal Mail (free and paid individual plans) and Workplace/business plans share the same reputation-based logic. Paying more doesn't buy a higher ceiling by itself.
- If you're an org admin, you're managing this at the domain level — one flagged user's sending behavior can affect how the whole domain is perceived.
- If what you actually need is to send newsletters, drip campaigns, or transactional mail at volume, Zoho's own policy says to use Zoho Campaigns or ZeptoMail instead of a mailbox — more on why below.
Steps: how to stay under the limit#
- 1
Know which ceiling you're actually testing
There are two separate limits: a rolling hourly send-rate cap and a per-message recipient cap. A blocked send from one bulk email to 200 people is a recipient-limit problem, not a rate problem — the fix is different.
- 2
Spread sends out instead of batching them
Sending 300 emails in one burst reads very differently to a reputation system than sending 300 emails across three hours. If you're sending to a list, stagger it — most list tools and even a simple scheduled-send habit will do this for you.
- 3
Warm a new account up gradually
A mailbox created this week has no sending history, so it starts near the bottom of the 50–500/hour range. Send a modest, steady volume for the first couple of weeks rather than importing an old contact list and mailing all of it on day one.
- 4
Split large recipient lists into batches under the cap
If a single message needs to reach more than 100–150 people, break it into batches under your account's recipient cap rather than one oversized send — or move it to a tool built for lists in the first place (see the next step).
- 5
Route anything list-shaped to Campaigns or ZeptoMail
Newsletters, marketing sends, and automated transactional mail are explicitly against Zoho Mail's usage policy for a personal or team mailbox. Zoho Campaigns (marketing) and ZeptoMail (transactional) are built for that volume and won't put your regular mailbox's reputation at risk.
- 6
Watch bounce rate and spam complaints, not just volume
Reputation scoring weighs bounces and complaints heavily. A cleaner, smaller list that doesn't bounce protects your sending rate more than staying just under a recipient count on a stale list.
How the limits differ by account type#
The table below is the shape of it as of September 2026, drawn from Zoho's own rates-and-limits documentation. Treat the exact numbers as directional — Zoho adjusts reputation thresholds without a changelog, so verify against the live page before you rely on a specific figure for something business-critical.
| Account type | External send rate | Recipients per message | Notes |
|---|---|---|---|
| Free personal Mail | Low end of 50–500/hour | Up to 100 (to+cc+bcc) | Reputation starts unproven; builds with clean sending history |
| Paid personal Mail | Same 50–500/hour range | Up to 150 (to+cc+bcc) | Higher recipient cap; hourly rate still reputation-based, not fixed by price |
| Workplace / business | Same 50–500/hour range per user | Up to 150 (to+cc+bcc) | Admin can see per-user standing across the whole domain |
| Internal, same-domain mail | Up to 1,000/hour | Up to 500 (to+cc+bcc) | Applies regardless of plan — internal mail is trusted differently than external |
| Brand-new account (any plan) | Bottom of the 50–500/hour range | Same caps as above | No sending history yet; ramps up with consistent, low-complaint use |
What to do when your outgoing mail is blocked#
You'll typically see something like a sending-limit or daily-quota notice, and new outgoing mail will stop going out. Nothing else breaks: incoming mail keeps arriving, you can still read and search your inbox, and the block is not the same as a suspended account.
The practical fix is to stop sending and wait — Zoho's own documentation describes a block of up to about an hour before sending resumes. Retrying immediately, or worse, spinning up a second account to route around it, tends to make a reputation problem worse rather than better, because it looks like exactly the abuse pattern the system is designed to catch.
Once sending resumes, don't pick up where you left off at the same pace. Send a smaller batch first, confirm it delivers cleanly, and only then work back up toward your usual volume. A second block within the same day or two reads as a pattern rather than a one-off, and patterns are what actually move your reputation score down.

Don't try to route around a block
A faster way than watching the clock#
Manually staggering sends and tracking a recipient count in your head works, but it's a chore that grows with every list you send to. AI Emaily's approve-before-send workflow drafts and queues outgoing mail through your connected Zoho mailbox, so batching a large list into sends that respect your account's caps is something you set up once rather than remember every time.
It doesn't get you a higher limit than Zoho allows — nobody can, since it's reputation-based on Zoho's side, not a setting. What it removes is the manual math: staggering timing, tracking recipient counts across drafts, and catching a block before it happens instead of after. We build AI Emaily, and it connects to Zoho Mail alongside Gmail, Outlook and any IMAP account from one inbox.
Frequently asked
See it in AI Emaily
Keep reading

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.