WhatsApp Broadcast Limits & How to Work Within Them
You built a list, wrote a good message, hit send — and only half of it seemed to land. Or worse, your number got slowed down, flagged, or restricted right when a campaign mattered most. If that sounds familiar, the culprit is almost always the WhatsApp broadcast limit: a set of caps, some of them written down and some of them invisible, that decide how many people you can reach and how fast.
This guide is for anyone sending to a list — D2C founders, agencies, clinics, brokers, support teams. We'll cover the limits that actually exist (and the ones that are myths), why WhatsApp enforces them, and the pacing playbook that lets you reach a big audience without tripping a filter. The goal isn't to "beat" the limit — it's to work with it so your message gets delivered and your number stays healthy.
The two kinds of broadcast limits
Most confusion comes from treating WhatsApp as one thing. It isn't. There are two very different worlds, with two very different sets of limits.
The broadcast-list limit (the WhatsApp app). On the regular WhatsApp Business app, a "broadcast list" sends an individual message to each saved contact. The hard cap is 256 recipients per list, and there's a catch most people miss: a contact only receives your broadcast if they have saved your number. If they haven't, the message silently doesn't arrive. So the real-world reach of an app broadcast is far smaller than the 256 number suggests.
The messaging limit (the WhatsApp Business API). API tools (WATI, AiSensy, Interakt and similar) don't use broadcast lists at all. They send template messages, and Meta governs volume with messaging tiers — typically starting around 250 or 1,000 unique business-initiated conversations per 24 hours and scaling up to 10K, 100K and unlimited as your quality stays high. Here the cap isn't a fixed number; it's earned, and it can be cut back if your quality rating drops.
The takeaway: "the broadcast limit" depends entirely on how you're sending. A 256-contact list cap and a tiered API quota are not the same problem, and the workarounds are different too. Our complete guide to WhatsApp broadcasts walks through which method suits which use case.
Why these limits exist
WhatsApp's limits aren't arbitrary friction. They exist to keep the platform from turning into an SMS-blast channel users learn to ignore. Understanding the why makes the how obvious.
- Spam control. A sudden spike of identical messages from one number is the single clearest signal of bulk-sending. Caps and tiers force volume to ramp gradually, which is exactly what a legitimate business does and a spammer doesn't.
- User trust. WhatsApp is a personal-feeling channel. If broadcasts were unlimited, inboxes would fill with promos and people would mute or block businesses en masse. The limits protect the inbox so your messages stay welcome.
- Quality enforcement. On the API, your tier rises and falls with how people react — blocks, reports and "not interested" feedback drag it down. The cap is really a proxy for are people glad to hear from you.
This is why the smart framing isn't "how do I get past the limit" — it's "how do I send like a business people want to hear from." Do that, and the limits stop being a ceiling. For the daily side of this question, see how many WhatsApp messages you can send a day.
The limits that are real vs the myths
A lot of "limit" advice online is outdated or invented. Here's what to actually plan around.
| Claim | Reality |
|---|---|
| "256 contacts per broadcast list" | True on the WhatsApp app — but recipients must have saved your number, or they don't receive it. |
| "You can broadcast to unlimited people if you make enough lists" | Technically you can create multiple 256-lists, but sending the same blast across many lists in minutes is exactly the burst pattern that gets numbers flagged. |
| "The API lets you send to anyone instantly" | False. API sends are gated by messaging tiers and require opt-in plus approved templates. |
| "There's a fixed daily message number for everyone" | False. On the app it's about pacing and recipient saves; on the API it's your earned tier, which varies per number. |
| "Hitting the limit once gets you banned" | Mostly false — but repeated burst sends, high block rates and unsolicited messaging absolutely raise ban risk. |
The honest summary: the recipient-must-save rule and the burst-pattern risk are the two real constraints most senders underestimate. The exact numbers matter less than the shape of how you send.
How to work within the limits (the pacing playbook)
You don't need to fight the caps. You need to send in a pattern that looks human and earns trust. Here's the playbook most teams we talk to converge on.
1. Send to people who opted in
Every limit gets easier when your list wants to hear from you. Opt-in keeps block and report rates low, which is what protects your reach (and your API tier) over time. Build the list deliberately rather than scraping contacts — our guide to building a WhatsApp opt-in list the right way covers consent that holds up.
2. Segment instead of blasting everyone
A 5,000-person identical blast is the worst possible pattern. Break the audience into relevant segments and send each a message that fits — fewer recipients per send, higher relevance, lower block rate. Segmenting your WhatsApp audience turns one risky blast into several safe, better-performing sends.
3. Pace the send — don't fire it all at once
This is the heart of it. Whether you're on the app or a workspace, the difference between "safe" and "flagged" is rhythm. That means:
- Spread the send over time rather than hammering hundreds of messages in a minute.
- Add variation — randomized gaps between messages, not a robotic fixed cadence.
- Personalize so messages aren't byte-for-byte identical, which softens the duplicate signal.
- Warm up new numbers gradually instead of debuting them with a 1,000-person campaign.
Doing this by hand is tedious and error-prone, which is exactly why pacing is something to automate rather than babysit. If you'd rather schedule the send than sit there spacing it out, see scheduled WhatsApp messages.
4. Watch your quality signals
After every campaign, look at delivery, blocks and replies. Rising blocks or "stop" replies are an early warning that your content, frequency or list quality needs work — long before WhatsApp restricts you. Trim unengaged contacts; don't keep messaging people who've gone quiet.
5. Reaching 1,000+? Plan the structure
Big lists need a deliberate approach — not one giant send, but paced batches to opted-in, segmented recipients. We break down the mechanics in how to send a WhatsApp broadcast to 1,000+ people so the volume doesn't become a liability.
Where Tenashi fits
The limits above are really two problems: the app caps reach at 256 saved contacts, and doing large sends safely means pacing every message by hand. Tenashi is the WhatsApp workspace for teams that solves both — on your existing number, linked with a QR scan (no new SIM, no porting, no template approvals, no per-message fees).
Because you broadcast from your own number through a workspace, you're not boxed into the app's 256-saved-contact list or stuck earning your way up API messaging tiers. And crucially, sends are ban-protected: Tenashi paces messages at a human rhythm, adds jitter between them, shows typing presence, warms up newer numbers, and guards against duplicate and burst patterns — with a safety log so you can see what shipped. That's risk reduction, not a guarantee — WhatsApp's policies can change and no tool can promise immunity — but it's the difference between blasting and sending like a business people trust.
You also get a real CRM under every broadcast: contacts, custom fields and segments, so you send the right message to the right list instead of one big blast. On Growth and Scale, AI can help draft and translate broadcast copy and summarize replies (AI is a Growth & Scale feature only). Plans start at $18/mo, with a 3-day Growth trial, no card.
Start your free trial → · See every feature
FAQ
What is the WhatsApp broadcast limit?
On the WhatsApp Business app, a broadcast list caps at 256 recipients, and contacts only receive it if they've saved your number. The WhatsApp Business API has no fixed list — it uses messaging tiers (e.g. 250, 1K, 10K+ conversations per day) that scale with your quality rating.
How many people can I broadcast to on WhatsApp at once?
Up to 256 per broadcast list on the app, but only those who saved your number actually get it. For larger reach you need either the API's tiered messaging or a WhatsApp workspace that sends from your own number — paced safely rather than blasted all at once.
Can I send a WhatsApp broadcast to 1,000 people?
Yes, but not as a single instant blast. Reach 1,000+ by sending to an opted-in, segmented list in paced batches with randomized gaps, so the pattern looks human. Sending all 1,000 identical messages in minutes is the fastest way to get flagged or restricted.
Will hitting the broadcast limit get my number banned?
Hitting a cap once usually won't. What raises ban risk is the pattern — burst sends, identical messages, high block and report rates, and messaging people who never opted in. Pacing, opt-in and segmentation reduce that risk, though no method can guarantee against WhatsApp's policies.
Why do recipients not receive my WhatsApp broadcast?
On the app, a broadcast only reaches contacts who have saved your number in their phone. If they haven't, the message silently fails to arrive. This is the single biggest reason app broadcasts underperform their 256-contact promise — and why opt-in lists matter so much.
How do I send a large broadcast without getting flagged?
Send only to people who opted in, segment the audience, and pace the messages — spread them over time with randomized gaps and personalization instead of one burst. Warm up newer numbers first, and watch your block and reply rates after each send to catch problems early.
The WhatsApp broadcast limit isn't a wall — it's a request to send like a business worth hearing from. Do that, and reach takes care of itself. Start a free trial to broadcast from your own number with pacing built in.