The short version: the free WhatsApp Business app caps broadcast lists at 256 contacts each, and only people who have your number saved in their own phone will ever receive that message. Anyone serious about scale eventually moves to the WhatsApp Business Platform (the paid API), which uses rolling 24-hour messaging tiers of 1,000, 10,000, 100,000 or unlimited unique contacts instead of a flat number. The limit most people hit first isn’t the 256, it’s the invisible one nobody talks about, and I’ll get to that in a minute.
The number everyone quotes, and what it covers
If you’re using the standard WhatsApp Business app on your phone, the free one anyone can download, a broadcast list can hold a maximum of 256 recipients. You can create as many lists as you like, so if you have 2,000 contacts you’d need eight separate lists to cover them all, sent one at a time, each one manually.
That’s the headline number and it’s correct. But it’s also the least useful piece of information in this whole topic, because the 256 cap is not what stops small businesses reaching their audience through WhatsApp. I’ve watched clients get so fixated on that figure they miss the two conditions that determine whether a broadcast message lands at all.
- The recipient must have your business number saved as a contact on their phone. If they haven’t, your broadcast goes nowhere near their WhatsApp, even though your app happily shows the message as “sent.”
- You cannot have added them from a purchased list or scraped database. WhatsApp’s terms require that people have opted in and given you their number directly, not that you found it somewhere.
Miss either of those and your reach on a 256-person list can quietly be 40 people, not 256. Nothing in the app tells you that. There’s no bounce notification, no “undelivered” flag for broadcasts the way there is for individual chats. You just get silence, and most business owners assume the silence means low engagement rather than a delivery problem.
The story that taught me this
A client of mine, Dana, runs a boutique events business out of Tel Aviv with just under 3,800 contacts collected over four years of workshops and pop-up markets. She built her list into fifteen broadcast lists of roughly 250 each and sent a launch announcement for a new venue partnership, expecting a wave of replies the way she’d get from an email newsletter.
She got 61 replies. Out of 3,800 people.
We dug into it and found the issue immediately: the vast majority of those contacts had never saved her WhatsApp business number. They’d messaged her once through a Linktree click or a QR code at an event, she’d saved their number, but the relationship was one-directional. WhatsApp broadcast only works when both sides have each other saved, which almost nobody explains clearly because it makes the feature sound far less useful than it’s marketed to be.
Her fix wasn’t a clever workaround. It was a proper prompt: every follow-up message for a month included a one-line ask, “save this number so you don’t miss updates,” with her business card attached. Within six weeks her save rate on new contacts went from roughly 15% to 68%, and her next broadcast to the same-sized list got over 400 replies. The limit hadn’t changed. The audience who could receive the message had.
Broadcast lists, groups, and Communities: three different tools, one confusing name
WhatsApp has quietly built three separate ways to message many people at once, and they get lumped together constantly.
- Broadcast lists: one-way, private, 256 contacts per list, each recipient sees the message as if it came from you directly and doesn’t see who else got it. Best for updates, offers, reminders.
- Groups: up to 1,024 members (raised from the old 256 cap a couple of years back), everyone can see everyone else and reply into the shared thread. Good for building a genuine two-way community but noisy at scale, and picking the wrong name can quietly kill sign-ups before anyone even joins, which is worth sorting if you’re going this route (how you name a WhatsApp business group to attract members matters more than most people assume).
- Communities: the newer structure, a container that can hold up to 5,000 members split across sub-groups, plus an announcement channel only admins can post in that behaves much like a broadcast but reaches everyone in the community at once, including people who haven’t saved your number, which is the big practical difference.
That last point is the one that changes the maths for anyone frustrated by the 256 cap. Announcement groups inside a Community don’t carry the same “must be saved as a contact” restriction that plain broadcast lists do. If your real goal is one-to-many reach without chasing save-my-number compliance from thousands of people, a Community is very often the better tool, and I’ve walked through the exact setup, including the numbers on retention that most guides conveniently leave out, in a separate step-by-step guide to building a WhatsApp Community.
When 256 isn’t enough: the API tiers
Once you’re past a few thousand engaged contacts, or you need broadcasts to trigger from a CRM rather than a phone, the free app stops making sense and businesses move to the WhatsApp Business Platform, usually called the API, accessed through a provider like Twilio, 360dialog, or MessageBird rather than downloaded as an app.
The API doesn’t use a flat 256 cap at all. Instead Meta assigns your business phone number a messaging tier based on quality rating and volume history, measured as unique users you can message in a rolling 24-hour period:
- Tier 1: 1,000 unique customers in 24 hours. This is where every new API number starts.
- Tier 2: 10,000 unique customers in 24 hours, unlocked after sustained good sending behaviour, usually within the first two weeks if your quality rating stays high.
- Tier 3: 100,000 unique customers in 24 hours.
- Tier 4: unlimited, reserved for large-volume senders with a strong track record, think airlines and big retail chains, not most small businesses.
Meta upgrades you automatically as your quality rating and volume history improve, and it demotes you automatically too if people start blocking or reporting you. A high block rate can drop a Tier 2 number back to Tier 1 within days. So the API doesn’t remove limits, it just replaces one fixed number with a moving one that rewards good behaviour and punishes spammy sending, which is arguably a fairer system but a less predictable one to plan around.
There’s also the 24-hour customer service window rule that applies to both the free app and the API: once a customer messages you, you have 24 hours to reply with a free-form message. Outside that window, on the API, you must use a pre-approved message template, and templates now fall into three categories, marketing, utility, and authentication, each with different approval rules and, since late 2023, different per-message pricing depending on the recipient’s country.
Working within the limit, step by step
If you’re still on the free app and don’t need the API yet, here’s what moves the needle:
- Audit your save rate before you build lists. Send a short direct message to your last 50 contacts asking if they’ve saved your number. If under half say yes, fix that first, more lists won’t help.
- Segment by behaviour, not alphabetically. Fifteen lists of “whoever’s next” perform worse than five lists of “people who bought in the last 90 days,” “people who abandoned a booking,” and “past attendees.” Segmented broadcasts routinely get two to three times the reply rate of blanket ones in my own client data.
- Ask for the save, every time, for the first month. A line at the end of your first reply to any new contact, “save this number so updates don’t get missed,” does more for your real broadcast reach than any list-management trick.
- Stagger sends across lists rather than blasting all at once. Sending eight lists of 250 within the same ten minutes looks identical to spam behaviour to WhatsApp’s systems. Spread it across a few hours.
- Keep an opt-out line in every message. “Reply STOP to opt out” isn’t just polite, it materially lowers your block and report rate, which is the number that threatens your account, not the list size.
- Move to a Community once you’re managing more than four or five broadcast lists. At that point the admin overhead of the app itself becomes the bottleneck, not WhatsApp’s rules.
If you’re already integrating WhatsApp into a wider funnel, from your site chat widget to email to paid ads, it’s worth checking your setup end to end rather than optimising broadcast lists in isolation; there’s a full walkthrough on adding WhatsApp Business to your website and marketing stack that covers where broadcast fits against the rest.
The bit nobody wants to say out loud
Here’s what most guides on this topic won’t tell you plainly: the 256 limit is not really your problem, and treating it as your problem leads people toward the wrong fixes.
The temptation, once someone hits the cap, is to buy a second phone number and run two accounts, or to bulk-import a purchased contact list to bypass the save-my-number issue, or to send the exact same broadcast to every list back to back to save time. All three feel like sensible workarounds and all three are exactly the pattern Meta’s spam detection is built to catch. I’ve seen a client’s number restricted within 72 hours of switching to a bought list because the report rate spiked immediately, people who never gave consent report unfamiliar numbers fast, and once your block rate crosses roughly 2 to 3 percent WhatsApp starts throttling delivery even before it formally suspends the account.
The businesses that get good broadcast reach on WhatsApp aren’t the ones who found a clever loophole around the cap. They’re the ones with unglamorous, boring opt-in habits, always asking for the save, always segmenting by real behaviour, always keeping the block rate low, and treating 256 as a perfectly fine number for a list of people who want to hear from them. The cap only feels punishing when the underlying list quality is weak, and no amount of API tier upgrading fixes that.
Drafting fifteen slightly different broadcast messages by hand for different segments is tedious, and it’s one of the few places I’ll say AI tools earn their keep without overselling it, feeding your usual tone and past broadcasts into a tool trained on your own writing so the segmented versions still sound like you rather than a template, which is worth reading about if you’re curious how far that goes and where it falls down when trained on your own content.
Related reading: whatsapp business linked devices limit.
Frequently asked questions
Is the WhatsApp Business broadcast limit 256 for everyone?
Only for the free WhatsApp Business app. That 256-per-list cap does not apply to the paid WhatsApp Business Platform (API), which instead uses rolling 24-hour tiers starting at 1,000 unique contacts and rising to 10,000, 100,000, or unlimited based on your quality rating and sending history.
Why did my broadcast message not reach everyone on the list?
Broadcast messages on the free app only deliver to contacts who have saved your business number themselves. If someone messaged you once but never added your number to their own phone, they will not receive your broadcasts, even though the message shows as sent in your app and your list appears full.
Can I get around the 256 broadcast limit legally?
Yes, by creating more than one list, up to 256 contacts each, with no cap on how many lists you run in total, or by moving to a WhatsApp Community, which supports up to 5,000 members and includes an announcement feature that reaches everyone without the save-my-number requirement that broadcast lists carry.
Will sending too many broadcasts get my WhatsApp Business account banned?
It can, particularly if your block or report rate climbs above roughly 2 to 3 percent. Buying contact lists, sending identical broadcasts to every list within minutes of each other, or messaging people who never opted in are the fastest routes to a restricted or banned number, far faster than simply having a large, well-consented contact base.
