WhatsApp broadcast limits: what actually caps your reach

Which WhatsApp broadcast limit are you actually hitting?

"Broadcast limit" is four mechanisms wearing one name. They belong to different products, count different units, and clearing one does nothing for the others — which is why searching the phrase returns contradictory advice.

Two more mechanisms cause the same symptom without being limits: delivery pacing, and a cap sitting on the recipient. If the platform is new to you, start with how the WhatsApp Business Platform works.

• Which WhatsApp broadcast limit are you actually hitting?
• What is the 256-contact limit on a WhatsApp broadcast list?
• How many people can you message a day on the WhatsApp Business API?
• How do you raise your WhatsApp messaging limit?
• How many messages per second can a WhatsApp number send?
• Why does a WhatsApp broadcast stop part-way through?
• What does WhatsApp quality rating actually restrict?
• Why did only some people receive the broadcast?
• What can a brand-new WhatsApp number expect to reach?

What is the 256-contact limit on a WhatsApp broadcast list?

This is the phone-based limit and the number most people mean. WhatsApp's Help Centre lists three broadcast list requirements: "Make sure all contacts in the broadcast list have saved your number in their address book", "You can create as many broadcast lists as you like", and "You can include up to 256 contacts in each broadcast list" (WhatsApp — how to use broadcast lists).

So 256 caps one list, not your audience — four lists reach 1,024 people. The address book requirement is what actually binds: "Only people who've added you to their phone's contacts will receive your broadcast message." Nothing tells you when that fails. The message shows as sent, and whoever never saved you does not receive it — on a list built from enquiries, most of them.

A further cap now sits on top, counted in broadcasts rather than recipients: "people in some countries might see a monthly broadcast limit", "rolling out gradually", and "you can only send a limited number of broadcasts per month" (WhatsApp — about broadcast limits). No figure is published, so treat any monthly number on a vendor page as invented. Yours is in the app under Settings, then Broadcasts.

Connect that number to the API while keeping it on your phone and the lists stop entirely: "Broadcast lists will be disabled" and "Existing Broadcast lists will become read-only" (Meta — onboarding WhatsApp Business app users). That is part of the bargain in running one number on the app and the API at once.

Checked against WhatsApp's Help Centre and Meta's developer documentation on 22 August 2026.

How many people can you message a day on the WhatsApp Business API?

The API has no broadcast list and no 256. It has a messaging limit, and it counts people rather than messages: "the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period" (Meta — messaging limits).

Ten messages to one person therefore spend one unit, not ten. Replies to customers who wrote first do not count at all, because they sit inside a service window. And the period moves continuously rather than resetting at midnight.

The limit is also not per number. Meta sets it "at the business portfolio level", shared by "all business phone numbers within a portfolio", and warns that "it's possible for one number to consume all of the portfolio's messaging capability within a given period" — the rule since 7 October 2025 (Meta — upcoming changes to messaging limits). A second number no longer buys a second allowance.

Your current figure is in WhatsApp Manager under Account tools, then Messaging limits.

How do you raise your WhatsApp messaging limit?

Only Meta raises it, and it publishes the criteria. To reach 2,000 you complete one of three scaling paths: verify your business, have the partner who onboarded you verify it, or "send 2,000 delivered messages outside of customer service windows to unique WhatsApp user phone numbers within a 30-day moving period, using templates with a high quality rating".

Above that it is automatic, on two conditions Meta states together: "you are sending high-quality messages across all of your business phone numbers and templates" and "in the last 7 days, your business has utilized at least half of your current messaging limit". Meet both and the limit "increases by one level within 6 hours".

The second condition traps cautious senders: you cannot climb by sending sparingly, because Meta wants to see half your current limit used.

How many messages per second can a WhatsApp number send?

Throughput is a separate system, constantly confused with the limit: the limit is how many people, throughput is how fast. Meta supports "up to 80 messages per second (mps) by default, and up to 1,000 mps by automatic upgrade" per registered number, and it "is inclusive of inbound and outbound messages and all message types" (Meta — throughput). Exceed it and the API returns error 130429.

A number in use with both the WhatsApp Business app and the Cloud API is fixed lower: Meta gives those numbers "a fixed throughput of 20 mps", and publishes no reason for the figure. It sounds punitive and rarely is — at 20 mps a 10,000-recipient campaign clears in about eight minutes. The messaging limit binds long before throughput does.

The 1,000 mps upgrade is not bought: Meta requires an unlimited portfolio limit, 100,000 or more unique recipients in a moving 24 hours and a quality_score of YELLOW or higher, and then "your business phone number is automatically upgraded to 1,000 mps at no cost to you".

Why does a WhatsApp broadcast stop part-way through?

This ceiling has no name in most write-ups and explains more stalled campaigns than the tier does. Meta operates business portfolio pacing, "a template message delivery batching mechanism that allows time to gather feedback on any template sent as part of a large-scale messaging campaign", and applies it to portfolios that have "sent less than 500K template messages" collectively "within a moving 365-day lookback period" (Meta — business portfolio pacing).

Half a million template messages a year is a large sender, so that threshold puts most small and mid-sized businesses inside the batching — with one caveat Meta states on the same page: "This feature is being released gradually over the coming weeks so may not apply to you immediately." Being under the threshold makes you eligible for pacing, not certainly subject to it.

Meta's account of what pacing does: "an initial set of messages will be processed normally", then "subsequent messages will be held", returning a message_status of held_for_quality_assessment. Batches release as feedback arrives; if it suggests suspicious activity, the rest are dropped with error 135000.

Template pacing does the same to individual templates — "valid for marketing and utility templates", with newly created, unpaused and non-GREEN templates as candidates (Meta — template pacing). It exists to pause a template before it reaches everyone, and a paused template then fails with error 132015, which Meta describes as "Template is paused due to low quality so it cannot be sent in a template message".

Meta does publish a ceiling on the delay: "even if paced, campaign messages with highest throughput still get delivered within an hour (99 percentile)". So a campaign still stalled the next morning is not being paced — it is failing, and the status webhook will say which code.

A campaign that sends 400 of 5,000 and then hangs is often neither broken nor throttled by your tier. It is being assessed.

What does WhatsApp quality rating actually restrict?

Less than it used to, and this is the correction most pages have missed. Meta bases quality on "how messages have been received by WhatsApp users over the past seven days", "weighted by recency" and "determined by a combination of user feedback signals like blocks, reports, mutes, archives, and reasons users provide when they block you" (Meta — send messages).

Two changes landed on 7 October 2025: "the Flagged phone number quality state is no longer possible", and "if your business phone number quality rating drops, its messaging limit will not be downgraded".

A red rating therefore does not shrink your limit. It stops it growing, because high-quality messaging is half the automatic scaling test, and it feeds pacing. Policy enforcement runs on a separate track, covered in how a restriction on your own number behaves.

Templates carry their own rating — GREEN, YELLOW or RED — and Meta drops one to YELLOW or RED on "negative feedback from multiple WhatsApp users, or low read-rates" (Meta — template quality rating). Meta can see that read rate; you cannot reproduce it, because recipients can switch read receipts off. Which is why no open-rate figure appears anywhere on this site, and why one on a vendor's page is not a measurement.

Checked against Meta's developer documentation on 22 August 2026.

Why did only some people receive the broadcast?

If delivery is patchy rather than stalled, the cap is probably not on your side. Meta limits marketing templates per recipient, counted across every business messaging that person — its wording is "from any business". It surfaces as error 131049, which no platform setting removes: see what WhatsApp error 131049 is telling you.

One country rule caps reach absolutely rather than temporarily: "WhatsApp does not currently deliver marketing template messages to WhatsApp users with United States phone numbers" (Meta — per-user marketing template message limits). Utility and authentication templates sit outside that sentence; waiting or re-segmenting changes nothing.

What can a brand-new WhatsApp number expect to reach?

250 unique people in a moving 24 hours, on a portfolio Meta has not yet verified, with deliveries possibly batched on top. Numbers earn their way up by sending well to people who asked to hear from them, and business verification runs on Meta's schedule.

So a launch plan built on "import the list, broadcast on day one" fails on arithmetic first. Segmenting, sending the best segment first and letting the limit climb works with the mechanism rather than against it. Still choosing a product? The Business app against the API sets the 256 cap beside the tier system.

No platform changes any of this. Every ceiling belongs to Meta, set against your portfolio, your number and your templates. Software can only show you where you stand and stay out of the way: surface the messaging limit and quality rating with the time they were last read from Meta, let you force a fresh read rather than trusting a cached one, record Meta's error code per recipient so a 131049 is not filed beside a 132015, and never auto-retry a code Meta says not to retry — a fair test for any platform, the campaign and inbox tools included.

Every figure attributed to Meta's developer documentation was re-read there on 22 August 2026, and every quotation attributed to WhatsApp's Help Centre was read from the article linked beside it the same day. Meta changes both without notice; the linked pages are authoritative and this one is not. One number is deliberately absent: WhatsApp publishes no figure for the monthly broadcast limit, so any specific number you find quoted for it was not read from WhatsApp.