You built a broadcast list, added your customers, and hit send. WhatsApp let you add 256 people, then stopped. And of the 256 who made the list, a chunk never got the message at all, with no error and no warning.
That is the WhatsApp broadcast limit doing two different jobs at once. There is a hard cap on list size, and there is a silent delivery filter that most people never notice until a campaign underperforms. This guide covers both: where the 256 number comes from, why broadcasts fail to land, and the legitimate ways to send to more than 256 contacts in 2026 without getting your account flagged.
What is the WhatsApp broadcast limit (and why does it exist)?
The WhatsApp broadcast limit is 256 contacts per broadcast list in the WhatsApp Business app and the standard app. A broadcast sends one message to many people as separate one-to-one chats, so each recipient sees a private message and replies only to you. The 256 cap exists to keep broadcasts a personal-messaging feature, not a mass-marketing channel.
A broadcast list is not a group. When you send to a list, every recipient gets the message in their own chat thread, as if you messaged them directly. They cannot see who else received it, and their replies come back to you alone. That privacy model is the whole point, and it is also why WhatsApp treats broadcasts as conversational rather than promotional.
The cap is consistent across both apps. Per WhatsApp's Help Center guide on broadcast lists, a single list holds a maximum of 256 contacts. The WhatsApp Business app adds label-based selection on top, so you can build a list by filtering contacts tagged "VIP" or "New customers," but the ceiling does not move. Label filtering changes how you pick the 256, not how many you get.
Why 256 specifically? It is a deliberate friction point. WhatsApp built broadcasts for the corner shop messaging its regulars, not for a brand blasting a list of 50,000. The moment you need real scale, the platform wants you on the Business Platform (the API), where sending is metered, priced, and quality-controlled. The 256 wall is the nudge.
How does the 256-contact cap work on WhatsApp Business app vs the API?
The WhatsApp business broadcast limit of 256 applies only to the WhatsApp Business app, the free app you install on a phone. The WhatsApp Business Platform (Cloud API) has no 256-contact list concept at all. Instead it limits how many unique people you can message in a rolling 24 hours, starting at 250 and scaling to unlimited as your account earns trust.
These are two completely different products with two completely different limit models. Confusing them is the single most common mistake in this space.
| WhatsApp Business app | WhatsApp Business Platform (Cloud API) | |
|---|---|---|
| Limit type | 256 contacts per broadcast list | Unique customers per rolling 24h |
| Starting limit | 256 per list, unlimited lists | 250 unique customers/day |
| Recipient must save your number | Yes | No |
| Opt-in required | Best practice | Mandatory |
| Scales to | Manual, list by list | 1K, 10K, 100K, unlimited |
| Per-message billing | Free | Yes, since July 1, 2025 |
| Setup | Install and go | Business verification + a provider |
On the app, the 256 cap is per list, and you can create more than one list. So "how many contacts in whatsapp broadcast" has a two-part answer: 256 per list, unlimited lists, but you send to each list separately and manually. Nothing pools them into one send.
On the API, there is no list object that caps at 256. According to Meta's messaging limits documentation, a new phone number starts at 250 unique recipients per 24-hour window, then climbs through defined tiers: 1,000, then 10,000, then 100,000, then unlimited. The constraint is how many distinct people you reach in a day, not how many fit in a list.
One detail that trips up teams scaling on the API: as of October 2025, messaging limits are calculated at the business portfolio level and shared across every phone number in that portfolio. Adding a second number does not double your daily capacity. Both numbers draw from the same tier. Plan your number architecture around the shared pool, not around per-number math.
Why is your WhatsApp broadcast not delivering to everyone?
The most common reason a WhatsApp broadcast is not delivering is that recipients have not saved your phone number. On the Business app, broadcast messages only reach contacts who have your number saved in their address book. If they have not saved you, the message is silently dropped. No error appears on your end.
This is the rule that surprises everyone. You can add someone to a broadcast list and send to them, and WhatsApp will show the send as going out, but the recipient receives nothing because your number is not in their contacts. The list does not validate this. It will happily include 256 people and quietly deliver to only the subset who saved you.
For a typical business list, that subset is often a minority. If you imported customers from a CRM and most of them never saved your business number, your effective reach can be a fraction of 256, even though the app reports a clean send. This is why "whatsapp broadcast not delivering" is almost always a contacts problem on the app, not a bug.
There are a few other delivery killers worth knowing:
- Number not saved (app). The big one. No save, no delivery. There is no workaround inside the Business app.
- Not opted in (API). On the API, you can reach people who have not saved you, but only if they opted in. Messaging non-consenting numbers tanks your quality rating fast.
- Per-user marketing cap (API). Meta limits each user to roughly two marketing template messages per day across all businesses combined. Exceed it and the send fails with error 131049, "not delivered to maintain a healthy ecosystem." The cause is the recipient's daily ceiling, not your account.
- US marketing pause (API). Marketing template messages to US numbers (+1 country code) have been paused since April 1, 2025. Utility and authentication templates still deliver; marketing simply does not arrive, with no clear error.
- Quality rating throttling (API). A "Low" quality rating from blocks and reports can cap or freeze your sends regardless of your tier.
If you are running broadcasts off the app and seeing weak numbers, audit the saved-number issue first. It explains more failed broadcasts than every other cause combined. For the consent side of the equation, our WhatsApp opt-in collection guide covers the channels and wording Meta now requires before any API send is allowed.
How do you send a WhatsApp broadcast to more than 256 contacts?
To send a WhatsApp broadcast to more than 256 contacts, you have two legitimate paths. On the free Business app, create multiple broadcast lists of 256 and send to each one separately. For genuine scale and reliable delivery, move to the WhatsApp Business Platform (the API), which removes the 256 list cap and delivers to people who have not saved your number, provided they opted in.
The multiple-list workaround is real, but understand what it actually buys you. You are not bypassing the limit. You are repeating a manual send across however many lists you build. Three lists of 256 is three separate send actions, three sets of recipients who still need to have saved your number, and zero analytics tying it together.
| Approach | Reach | Delivery reliability | Effort |
|---|---|---|---|
| Single broadcast list | Up to 256 | Only saved contacts | Low |
| Multiple lists (app) | 256 x N lists | Only saved contacts | Linear, manual |
| WhatsApp Business Platform (API) | 250 to unlimited per 24h | Opted-in, no save needed | Setup, then automated |
The multiple-list path suits a small operation reaching a few hundred regulars who already have its number. The moment you need to reach thousands, or reach people who have not manually saved you, the app stops being the right tool. That is the threshold where the API earns its setup cost.
There is a middle ground worth naming. If you are running off WhatsApp Web rather than the API, a scheduling layer can queue and stagger your sends across lists so you are not babysitting the app, and it can keep your campaigns organized instead of scattered across manual broadcasts. Blueticks campaigns handle scheduled and recurring sends from your existing WhatsApp account, which fits teams that have outgrown manual broadcasts but are not ready to stand up a full API integration.
What is the WhatsApp broadcast message limit per day?
On the WhatsApp Business app, there is no published per-day broadcast message limit, but sending to many lists in quick succession can trigger temporary throttling or a ban if it looks like spam. On the WhatsApp Business Platform, the daily limit is explicit: a tiered number of unique customers per rolling 24 hours, from 250 up to unlimited.
The app has no official daily counter, which leads people to assume there is no limit. There is, it is just behavioral. WhatsApp's automated systems watch for spike patterns, high block rates, and messages to people who never saved you. Hit those signals and you risk a temporary block or, repeated, a permanent ban. The absence of a published number is not permission to blast.
The API is where the daily limit is concrete and worth memorizing. Per Meta's messaging limits documentation, the tiers are:
- 250 unique customers per 24 hours (new, unverified numbers)
- 1,000 unique customers
- 10,000 unique customers
- 100,000 unique customers
- Unlimited
Movement up the tiers is automatic and trust-based. Meta evaluates your eligibility on a recurring cycle (every six hours in the current system) and promotes you when your sending volume and quality rating clear the bar. In 2026, a business that completes verification can jump straight to the 100,000 tier rather than crawling up from 250, which materially shortens the ramp for legitimate senders.
Two things gate that climb. Your quality rating has to stay healthy, and the daily limit is shared across your whole portfolio of numbers, not granted per number. A throughput ceiling also applies on top of the daily limit (80 messages per second by default on the Cloud API), which matters only at high volume but is real. For how per-message pricing layers onto all of this, our WhatsApp Business API pricing guide for 2026 breaks down what each delivered template actually costs.
WhatsApp broadcast vs group: which one should you actually use?
For one-way business messaging, use a broadcast list, not a group. A broadcast sends private one-to-one messages where recipients cannot see each other and replies come back only to you. A group is a shared thread where up to 1,024 members see every message and reply, and everyone can see who else is in it. Groups are for community, broadcasts are for announcements.
The two get confused because both let you message many people at once. The difference is privacy and direction.
| Broadcast list | Group | |
|---|---|---|
| Max members | 256 | Up to 1,024 |
| Message style | Private one-to-one | Shared thread |
| Recipients see each other | No | Yes |
| Replies go to | You only | Everyone |
| Recipient must save your number | Yes | No |
| Best for | Announcements, offers, updates | Communities, team chat |
For a promotional send, a group is usually the wrong choice. Members see each other's numbers, anyone can reply to all, and one annoyed customer can spam the whole list or, worse, harvest your other customers' phone numbers. A group also has no real way to keep messaging one-directional. It is a conversation space, not a broadcast channel.
The broadcast list keeps every recipient siloed, which is what you want for an offer or an update. The tradeoff is the 256 cap and the saved-number requirement. The group dodges the saved-number rule (people in a group receive messages without having saved you) and reaches up to 1,024, but you pay for that with zero privacy and an uncontrollable thread.
For most "whatsapp broadcast vs group" decisions in a business context, the honest answer is neither at scale. Both are personal-messaging tools stretched past their design. Real audience messaging at volume belongs on the API, where consent, delivery, and analytics are first-class. Use broadcasts and groups for what they are good at: small, genuine, relationship-driven sends.
What best practices keep your broadcast account in good standing?
The core WhatsApp broadcast best practices are simple: only message people who saved your number or explicitly opted in, keep your block and report rate low, send relevant and infrequent messages, and never import scraped or purchased numbers. WhatsApp's enforcement keys on recipient behavior, blocks and reports, not on raw volume. Stay below the irritation threshold and you stay in good standing.
The platform does not punish you for sending a lot. It punishes you for sending to people who do not want it. Every block and every "report spam" is a signal, and enough of them throttle or freeze your account regardless of which product you use.
A practical checklist:
- Save-then-send on the app. Build lists from people who already have your number saved. If they do not, your message will not arrive anyway, so chasing reach you cannot deliver is wasted effort.
- Opt-in is mandatory on the API. Document a consent timestamp and source for every contact. This is not optional; it is the deliverability floor.
- Respect the two-marketing-message daily cap. Each user can receive roughly two marketing templates per day across all brands. Over-send and you eat error 131049 and burn goodwill.
- Segment US numbers out of marketing. Since April 1, 2025, marketing templates to +1 numbers do not deliver. Route them to utility or authentication content, or leave them out of marketing sends.
- Throttle and stagger. Sudden spikes look like spam to WhatsApp's systems. Steady, relevant sending builds trust and moves you up the API tiers.
- Never use scraped or purchased lists. This is the fastest route to a quality-rating downgrade and a ban. No exceptions.
"We stopped trying to beat the 256 limit on the app and just fixed who we were messaging. Half our list had never saved our number. Once we cleaned that up and moved the real audience to a proper opted-in setup, delivery went from a guess to a number we could trust." (Synthetic operator quote, representative of the saved-number and consent issues this guide documents.)
The pattern across every limit in this article is the same. WhatsApp is not trying to stop you from reaching customers. It is trying to stop you from reaching people who did not ask to hear from you. Build your list around genuine consent and the limits stop being a wall and start being a guardrail.
If you are ready to run real campaigns from a clean, opted-in list instead of fighting the broadcast cap, start free with Blueticks and schedule your first managed send in under ten minutes. For the message copy itself, our library of WhatsApp campaign templates that convert covers offer, reminder, and win-back wording that stays compliant.
FAQ
How many contacts can I add to a WhatsApp broadcast list?
Up to 256 contacts per broadcast list, in both the WhatsApp Business app and the standard app. You can create more than one list, but each list sends separately, and there is no way to pool multiple lists into a single send. To reach more than 256 people in one managed send, you need the WhatsApp Business Platform (the API), which has no 256-contact list cap.
Why is my WhatsApp broadcast not delivering to everyone?
On the Business app, broadcast messages only reach contacts who have saved your phone number in their address book. If a recipient has not saved you, the message is silently dropped with no error shown to you. This is the most common cause of low broadcast delivery. On the API, the usual causes are missing opt-in, the per-user two-marketing-message daily cap (error 131049), the US marketing pause, or a low quality rating.
What is the WhatsApp broadcast message limit per day?
The Business app has no published daily limit, but sending heavily can trigger spam throttling or a ban based on recipient blocks and reports. The WhatsApp Business Platform has explicit daily limits: 250 unique customers per 24 hours to start, scaling through 1,000, 10,000, 100,000, and unlimited as your quality rating and volume earn each tier. Since October 2025, that limit is shared across all numbers in your business portfolio.
Should I use a WhatsApp broadcast or a group for my business?
Use a broadcast for one-way announcements and offers. Recipients get private one-to-one messages, cannot see each other, and their replies come only to you. Use a group only for genuine community or team interaction, where everyone seeing and replying to each other is the point. Groups hold up to 1,024 members but expose every member's number and let anyone reply to all, which makes them a poor fit for promotions.
Is it against WhatsApp's rules to send to more than 256 contacts?
No. Sending to more than 256 contacts is allowed through legitimate means: multiple broadcast lists on the app, or the WhatsApp Business Platform for scale. What violates the rules is messaging people who never opted in or never saved your number, using scraped or purchased lists, or using unofficial third-party apps that claim to bypass the limit. Those carry real ban risk. Stay on official products with consenting recipients and you stay compliant.
Sources: WhatsApp Help Center (broadcast lists), Meta's WhatsApp Business Platform messaging-limits documentation, and Meta's pricing documentation. Limit and tier figures (256 per list, 250 to unlimited API tiers, portfolio-level pooling since October 2025), the per-user two-marketing-message daily cap with error 131049, the US (+1) marketing pause from April 1, 2025, and per-message billing live July 1, 2025 reference Meta's published documentation current as of June 2026. Platform behavior changes; verify against Meta's docs before building around a specific figure.
