There is no single WhatsApp broadcast message limit per day. What you can send depends on which path you send from: the free WhatsApp Business app enforces a soft anti-spam ceiling with no published number, while the Meta Cloud API meters you in documented tiers from 250 up to unlimited per rolling 24 hours.
That is the honest 30-second answer, and most guides get it wrong by quoting one number as if it were law. The truth is that "per day" means three completely different things depending on how you send, and the number people search for most often does not exist. This article separates the real limits from the folklore, links every platform fact to Meta's own docs, and shows where a third path fits when neither the app nor the API is the right shape for your volume.
One clarification before we start, because it is the single most common mistake in this category. Blueticks, the tool this site makes, is not the WhatsApp Business API and not the free app. It is a third path: your own number over WhatsApp Web. Keep the three separate in your head and the whole "how much can I send" question gets clean.
How many WhatsApp broadcast messages can you send per day?
The number depends entirely on the path, so here is the short table before the long explanation.
On the free WhatsApp Business app, there is no published daily broadcast number. You can add up to 256 recipients to a single broadcast list, but the app polices sending through soft anti-spam signals, not a fixed daily quota. Send fast to people who never replied and you can be limited or banned well before any imagined "cap."
On the Meta Cloud API (the WhatsApp Business Platform), the daily limit is explicit and tiered. Meta caps how many unique customers you can send business-initiated messages to in a rolling 24-hour window at 250, then 2,000, then 10,000, then 100,000, then unlimited, and above the 2,000 tier your number climbs the ladder automatically as your quality and volume hold up.
On the own-number path (your existing number over WhatsApp Web, which is where Blueticks sits), there is no Meta-issued quota at all, because you are not on Meta's Business Platform. What governs you instead is WhatsApp's ordinary anti-spam behavior on a normal account, so sensible pacing, not a dashboard number, is the real limit.
So "how many broadcast messages can I send on WhatsApp per day" has no universal answer. It has three answers, and picking your path is what sets your number.
Why isn't there a single 'broadcasts per day' number in WhatsApp?
Because WhatsApp was never one product. It is a consumer app, a small-business app, and a programmable platform, and each layer treats sending differently.
The consumer and small-business apps are built to stop spam, not to license bulk sending. So their limits are deliberately vague. A hard, published "you may send N per day" number would be a spammer's specification sheet. Vagueness is the point: the app watches how you send, not just how much, and reacts to blocks, reports, and reply rates. This is why two accounts sending the same volume can get wildly different outcomes.
The Cloud API is the opposite. It is a paid, accountable platform, so Meta publishes an exact ceiling and a clear path to raise it. There the daily limit is a real, queryable number tied to your messaging limit tier.
The "per day" confusion comes from mixing these worlds. People read the API's clean tier numbers, assume the app must have an equivalent hidden number, and go hunting for it. It is not hidden. It does not exist in that form.
What are Meta's tiered messaging limits (250 to unlimited per 24h)?
On the Cloud API, your daily reach is set by your messaging limit tier, and Meta documents the ladder plainly. The tiers cap how many unique customers you can send business-initiated messages to in a rolling 24-hour period at 250, 2,000, 10,000, 100,000, and finally unlimited.
A few details that trip people up:
- The limit counts unique people you reach, not the number of messages. Replying to customers who messaged you first does not count against it; only business-initiated outreach does.
- New numbers begin at the 250 tier. Reaching 2,000 takes a manual step (business verification, or delivering 2,000 high-quality template messages). Above 2,000 you climb automatically: when you keep a healthy quality rating and use at least half your current limit over 7 days, Meta raises your tier within 6 hours. You do not apply; you earn it.
- Business-initiated messages are template-gated. To message someone outside an open 24-hour window you must use a pre-approved message template, and since July 2025 Meta bills per template message delivered, not per conversation.
This is the legitimate high-volume road. If you genuinely need to reach tens of thousands of new customers a day with people who have opted in, the Cloud API through a provider is built for exactly that, and it is the honest recommendation for that scale. The cost is real though: Meta verification, a provider relationship, template approval, and per-message pricing on every template you deliver.
What daily limit does the WhatsApp Business app actually enforce?
Here is where most of the internet gets it wrong. Search "whatsapp broadcast limit 35" and you will find confident claims that the app lets you broadcast to exactly 35 people, or send exactly 35 messages, per day. That number is folklore. Meta does not publish it. It appears nowhere in WhatsApp's or Meta's documentation, and treating it as a rule will only mislead you.
What the WhatsApp Business app actually enforces is softer and smarter than a counter. A broadcast list can hold up to 256 recipients (that is a list-size cap, a different limit we cover in the broadcast list limit guide, and if you need more than that see sending to more than 256 contacts). But there is a second condition that matters more than list size: a broadcast only reaches a person if they have saved your number in their contacts. Send to people who have not, and the message silently does not land, which is the usual reason a broadcast isn't delivering.
On top of that, the app watches your sending behavior. Rapid sends to strangers, a wave of blocks, or spam reports can get your number rate-limited or banned regardless of how few messages you sent. So the app's real "daily limit" is not a number you can plan against. It is a reputation you can lose. Plan around the reputation, not around a mythical 35.
Per day vs per month: which WhatsApp broadcast limit hits you first?
People also search for the WhatsApp broadcast message limit per month, expecting a monthly quota to sit above the daily one. On the app, there is no published monthly number any more than a daily one, so the honest answer is that neither is a fixed quota; behavior is what governs you.
On the Cloud API, the binding constraint is almost always the daily tier, not a monthly figure. If you are at the 2,000 tier and try to reach 5,000 new customers in a day, you hit the 24-hour ceiling immediately, long before any monthly consideration. The practical monthly capacity is just your daily tier multiplied out, assuming your quality holds and you keep climbing.
So for planning, ignore "per month" as a separate limit. Ask two questions instead: which path am I on, and what is my rolling 24-hour reality on that path. That is the limit that hits you first, and usually the only one that matters.
What actually gets you banned when you broadcast at volume?
Volume alone rarely triggers a ban. Sending pattern does. Across every path, the same signals put a number at risk:
- Messaging people who never opted in or never saved your number.
- A spike in blocks and "report spam" taps right after you send.
- Identical, salesy, link-heavy messages fired in a rapid burst.
- A brand-new number that starts blasting on day one with no warm-up.
On the Cloud API these signals show up as a falling quality rating, which can freeze or drop your tier. On the app and the own-number path they show up as rate-limiting or a ban with no appeal dashboard. The mechanism differs; the cause is identical.
The durable fix is not a clever workaround. It is consent and pace. Message people who expect to hear from you, keep content relevant, and spread sends over time instead of firing everything at once. Consent is the sender's responsibility, on every path, and no tool, including this one, can promise you will never be banned. Anyone who guarantees a no-ban outcome is selling you a story.
How can you broadcast reliably at volume from your own number?
Here is the path many guides skip, because it is neither the app nor the API. You can keep broadcasting from the WhatsApp number you already use, over WhatsApp Web, and let software handle the pacing and the repetition for you. This is the own-number path, and it is what Blueticks does.
Be clear about the honest trade. On this path there is no Meta verification and no per-message billing, because you are not on the Cloud API. In exchange you live with WhatsApp Web semantics (your number, your account, ordinary consumer-grade behavior) and, as with every path, no guaranteed protection from bans. It is not the API, it does not pretend to be, and it is not the only tool that works this way; be fair to the Cloud API for true enterprise scale and to the other own-number tools out there.
Where it fits best is the durable, repeating job: the weekly update to your customer list, the standing campaign you send every Sunday, the recurring reminder you have been pasting by hand. That is the work that actually compounds, and it is the work most likely to get you flagged if you fire it all in one burst. The answer is to pace it. Instead of sending 2,000 messages in five minutes, you schedule a recurring broadcast that spreads across the day at a human rhythm.
If that is your situation, the practical move is simple: connect the WhatsApp number you already use and schedule a recurring broadcast that sends on a safe daily pace instead of all at once. Set the recurring broadcast up once and let it repeat, keep every contact, and keep the pacing sane. Consent is still yours to earn, and sensible timing is still yours to keep, but the mechanical part, the part you were doing by hand at 11pm, sends itself.
FAQ
Is there a WhatsApp broadcast message limit per day? Not a single universal one. The free WhatsApp Business app enforces a soft, unpublished anti-spam ceiling; the Meta Cloud API sets an explicit tier from 250 to unlimited business-initiated conversations per rolling 24 hours; the own-number path has no Meta quota and is governed by ordinary anti-spam behavior. Your path sets your number.
Is the "35 messages per day" WhatsApp limit real? No. The "35" figure is folklore. Meta does not publish it in any WhatsApp or Business Platform documentation. The app limits by sending behavior and reputation, not a fixed count of 35.
How many contacts can a WhatsApp broadcast reach? A broadcast list holds up to 256 recipients, and a recipient only receives it if they have saved your number. That is a list-size cap, separate from any daily send limit. To go beyond 256, see the more-than-256-contacts guide.
What is the WhatsApp broadcast message limit per month? There is no separate published monthly quota. On the API your monthly capacity is just your daily tier multiplied out; on the app there is no fixed monthly number. The daily rolling window is the constraint that binds first.
Does sending more messages get my number banned? Volume alone usually does not. Sending to people who did not opt in, triggering blocks and spam reports, and blasting from a cold number are what put a number at risk. Consent and steady pacing are the real protection, and no path can guarantee a no-ban outcome.
