How to Get Past WhatsApp's 256 Broadcast Limit
Anyone who tries to send announcements with WhatsApp's broadcast list feature hits the same two walls: a list holds at most 256 contacts, and the message only reaches people who have saved your number. This article explains why the 256 limit exists, what the contact requirement really means, and how you get past both with a QR-based bulk messaging system — while being honest that the real ceiling you meet next is not headcount but sending speed.
1. What exactly is a broadcast list?
A broadcast list is a bulk-send feature built into the WhatsApp app. You create a list, add contacts, and when you write one message it is delivered to everyone on the list as a separate one-to-one chat. The recipient sees it in their normal chat window, not in a group; they cannot see the other recipients, and any reply comes only to you.
On paper it looks ideal: no group noise, privacy preserved. But two structural constraints keep broadcast from being a serious bulk-notification tool.
2. The two big constraints: 256 and the save-first rule
2.1 At most 256 contacts per list
WhatsApp caps every broadcast list at a hard 256 contacts. If you need to reach 300 customers you have to split the list, create multiple lists, and send to each one separately. This cap is not a setting you can raise; it is baked into the broadcast feature.
2.2 Recipients who haven't saved you get nothing
This is the real killer. A broadcast message only reaches people who have saved your number in their contacts. If someone you added hasn't saved you, they simply never see it — and you get no delivery-failure notice. So you can't tell how many of your 200-person list actually received anything. For the details of this rule and how the QR system gets around it, see messaging without saving contacts.
In short: broadcast gives you a 256-contact, mutually-saved audience. It's useless for a new customer, a form lead, or a member who hasn't saved you yet.
3. Why does this limit exist?
The 256 cap and the save-first rule aren't arbitrary; both exist to slow down spam. WhatsApp doesn't want one account reaching tens of thousands of strangers with a single tap. The save-first rule enforces "there must be a mutual relationship," and the 256 cap keeps the reachable audience per send small. Together these two brakes make abuse harder — and, as a side effect, throttle legitimate bulk notifications too.
An important distinction: the 256 cap is a limit of the product feature (the broadcast tool is designed that way), while ban risk is a separate matter of your sending behavior. Keeping the two apart helps you look for the fix in the right place.
4. How the limit is bypassed with a QR-based system
You can't lift the 256 cap inside the broadcast feature. The fix is to not use broadcast lists at all. A QR-based bulk messaging system (this project uses whatsapp-web.js, not the official Business API) pairs the account on your phone via a QR code and sends a separate, normal one-to-one message to each person on the list. As far as WhatsApp is concerned this is no different from you typing each message by hand — it's just done automatically and in sequence.
Two natural consequences follow:
- The 256 cap disappears: because no broadcast list is used, there is no 256 ceiling. The list can be 50 people or 5,000.
- The save-first rule disappears: since each message goes as a normal one-to-one chat, recipients don't need to have saved you first. As long as the number is formatted correctly, the message arrives.
If you want that sending to become automatic, schedulable and API-triggerable, the flow in sending automated WhatsApp messages does exactly this.
5. But the real limit isn't headcount — it's speed
Time to be honest. Saying "I got past 256, so there's no limit anymore" is misleading. When you remove the headcount cap, a different limit appears: WhatsApp's spam algorithm. Fire hundreds of messages back to back in seconds and your number is banned fast. That's why the QR system deliberately slows sending down:
| Rule | Value |
|---|---|
| Random wait between messages | 45–90 s (67–135 s for media) |
| Burst break | 8–12 min every 15 messages |
| Time window | 05:00–23:00 (local time) |
| Effective rate | ~25–30 messages/hour, ~450–500/day |
So you get past 256 — but not "everyone instantly." A 2,000-person list is spread across a few days at a safe pace. That isn't a flaw; that discipline is exactly what keeps your number alive. For the ban signals and how to avoid them, look at the automated sending flow and its anti-ban regime.
Ethics and law: getting past the 256 limit is not permission to message people who never asked to hear from you. Use this system only for recipients who have consented. Unsolicited bulk messaging violates WhatsApp's terms and data-protection law (GDPR, and KVKK/electronic-communication rules in Turkey); every marketing message must carry an opt-out line. For more, see the consent and ethics notes in messaging without saving contacts.
6. Broadcast list vs. a QR-based bulk system
| Feature | Broadcast list | QR-based system |
|---|---|---|
| Contact limit | 256 per list | Unlimited (spread by speed) |
| Save-first rule | Recipient must have saved you | Not required |
| Setup | In-app, ready to use | Needs deploying on your server |
| Scheduling / automation | None (manual) | Yes (scheduling + API) |
| Delivery reporting | Unclear (silently drops) | Message status is tracked |
| Sending speed | Instant, but to a saved audience | Deliberately slow, ban-safe |
In short, broadcast is a quick, free route if you already have a small audience that has saved you (say, 100 loyal customers). But once the audience passes 256, or recipients haven't saved you, broadcast stalls in practice. If you also want to weigh WhatsApp against SMS as a channel, our WhatsApp vs SMS comparison helps. To see the whole system and its alternatives, visit the WhatsApp bulk messaging main guide.
Frequently asked questions
Why is a WhatsApp broadcast list limited to 256 contacts?
256 is a built-in cap WhatsApp places on broadcast lists. The goal is to curb spam by stopping a single message from reaching tens of thousands of people uncontrolled at once. So you can add at most 256 contacts to one list.
Must recipients save my number for a broadcast to reach them?
Yes. A broadcast message only reaches people who have saved your number. If someone on the list hasn't saved you, they never receive it — and you get no failure notice.
Is there really a way to get past the 256 limit?
You can't lift the cap inside the broadcast feature. But a QR-based system doesn't use broadcast lists; it sends a normal message to each person separately. That removes both the 256 cap and the save-first rule. The limit becomes safe daily speed, not headcount.
If there is no headcount limit, can I send as fast as I want?
No. Even without a contact cap, the speed limit is real. To avoid bans the system waits 45–90 seconds between messages and sends ~450–500 per day. You get past 256 by spreading the list over time at a safe pace, not by blasting everyone at once.
Send in bulk without the 256 limit
No broadcast-list ceiling, no save-first rule, and your number protected from bans. On your own server, free and open source.
Open the panel →