The WhatsApp broadcast limit is the reason a promising campaign to 500 contacts turns into three separate sends of under 256 each. No guarantee any of them actually land. Most businesses discover this limit only after building a contact list they cannot actually message in one go.
This guide covers exactly what the WhatsApp broadcast limit is. The 256-contact cap and the monthly frequency restriction Meta has been rolling out. It also covers how the API removes these constraints and the practical steps for sending to a larger list safely.
What Is the WhatsApp Broadcast Limit?
The WhatsApp broadcast limit is the maximum number of contacts you can message in a single broadcast list. It is 256 contacts on both the standard WhatsApp app and the WhatsApp Business app. A broadcast sends one message to every contact on the list as a separate, private one-to-one chat. No recipient sees who else received it or what anyone else replied.
Beyond the per-list cap, recipients also need to have your number saved in their address book for the message to deliver at all. If they have not saved you, the message is silently dropped, with no error notification on your end. This single requirement quietly reduces effective reach on the native app well below the 256-contact ceiling for most businesses reaching cold or new leads. For the fuller picture of how broadcast works on the app versus the Business API, see our guide to WhatsApp broadcast messages.
The 256-Contact Limit Explained
The 256-contact cap applies specifically to the standard WhatsApp Business App, not the API. Here is exactly what it restricts and why it exists, since the two constraints get confused often enough to cause real troubleshooting delays.
1. The Limit Applies Per List, Not Per Account
Each broadcast list on the app is capped at 256 recipients independently. You can create multiple lists on the same account, but a business with 1,000 contacts still needs at least four separate lists to cover them. Each list sends separately, with no shared analytics or coordinated scheduling across lists.
2. The Cap Exists to Prevent Spam
WhatsApp set the 256-contact ceiling to curb mass unsolicited messaging while preserving the platform’s high engagement rates. Without this cap, and without the app’s lack of opt-in enforcement, broadcast would function as an open spam channel.
3. The Limit Has Stayed Fixed
The 256-contact cap has stayed fixed even as WhatsApp’s global user base grew past 3 billion monthly active users. This is a deliberate product decision, not an oversight Meta is expected to fix. It pushes serious business messaging toward the paid, compliance-governed Business API. Our guide to WhatsApp marketing strategy covers how that shift changes campaign planning.
The Monthly Broadcast Frequency Limit
Beyond the per-list cap, Meta has been testing a separate restriction on how many broadcast sends an account can make monthly. This is newer and less understood than the 256-contact rule.
1. What the Monthly Limit Covers
Starting in 2025, Meta began testing monthly caps on broadcast sends for individual users and business accounts. One early example put the limit around 30 broadcasts per month during the test phase. Based on existing research, this monthly ceiling has continued rolling out gradually rather than applying uniformly to every account. Treat the frequency limit as an active area of change, not a fixed number to plan around indefinitely.
2. Why This Limit Exists Separately From the 256 Cap
The per-list cap controls how many people receive a single broadcast. The monthly cap controls how often an account can send broadcasts at all. This closes a loophole where a business could work around the contact limit by sending very frequently to smaller segmented lists. Together, the two restrictions push meaningful broadcast volume toward the API rather than the free app entirely.
3. What Happens When the Monthly Limit Is Reached
Accounts that hit the monthly ceiling on the free app typically lose the ability to send further broadcasts until the next cycle resets. Exact enforcement has varied during the rollout. Meta has suggested Status updates and Channels as alternative outlets for individual users who want to reach a large audience without using broadcast specifically. For businesses, this makes the monthly limit one more structural reason the free app does not scale.
Signs You Have Outgrown the Native Broadcast Limits
Some businesses hit the 256-contact ceiling once and immediately know it is time to move. Others operate under it for months without realizing the limit is already costing them measurable reach and engagement. None of these signs come with a clear alert the way an outright rejected send would.
1. You Are Splitting the Same Campaign Into Multiple Sends
If a single campaign regularly requires two or more separate broadcast lists, you are already past what the free app handles cleanly. Each split send loses the coordinated timing and unified reporting a single campaign should have.
2. A Meaningful Share of Your List Has Not Saved Your Number
If many contacts have never saved your business number, your effective reach on the native app is likely far below your actual list size. Undelivered messages produce no error to alert you. This silent gap is one of the most common reasons broadcast performance looks weaker than list size alone would suggest.
3. You Need Scheduling or Timezone-Aware Sending
The native app has no scheduling capability at all. If your business serves customers across multiple timezones, or needs a campaign timed to a specific hour, this alone justifies moving to the API.
4. You Cannot Measure What Is Actually Working
Without delivery, read, or click data, there is no way to know why a broadcast underperformed. Content, timing, or the saved-number gap described above could all be the cause. Businesses that cannot answer this question are already past the point where the free app’s limitations outweigh its convenience.
WhatsApp Business API Limits and Tiers
The WhatsApp Business API removes the 256-contact cap and the saved-number requirement entirely. It replaces them with a tiered daily sending limit that scales with account quality and volume history.
1. The Four Sending Tiers
API accounts start at Tier 1, allowing 1,000 unique recipients per day. They scale to Tier 2 at 10,000, Tier 3 at 100,000, and Tier 4 with no daily limit. Tier upgrades happen automatically as an account maintains a strong quality rating and sends consistently near its current tier’s ceiling.
2. Limits Now Apply at the Business Portfolio Level
Since October 2025, Meta calculates these sending limits across the entire Meta Business Portfolio rather than per individual phone number. Adding a second number to the same portfolio does not double daily capacity, since both numbers draw from the same shared pool. Businesses planning multiple numbers need to plan around this shared limit rather than assuming each number gets its own independent allowance.
3. Opt-In Is Mandatory
Unlike the free app, where anyone can be added to a broadcast list regardless of consent, the API requires documented opt-in for every contact. This includes a consent timestamp and source. Our guide to WhatsApp CRM integration covers how that consent data connects to the rest of your customer records. Sending to a purchased or scraped list on the API is a policy violation that risks account restriction, not just a quality problem.
How to Send Broadcast with WhatsApp Business API
A business needing more than 256 contacts should follow a consistent sequence to get there. The same applies to any business needing the API’s compliance and scheduling capability regardless of contact count.
1. Confirm the API Is the Right Move
If your contact list has already outgrown 256, or you need scheduling, personalization, or delivery analytics, the API is the correct next step. Not a workaround on the native app. Our guide to how to get WhatsApp Business API covers the requirements and application process.
2. Access the API Through an Official BSP
Direct Cloud API integration requires engineering resources most businesses do not have readily available. Working with an official WhatsApp Business Solution Provider gives you the platform interface, template management, and compliance tooling without building it from scratch.
3. Build a Properly Documented Opt-In List
Collect consent through website forms, checkout flows, or Click-to-WhatsApp ads, and document the timestamp and source for every contact. This list becomes the foundation for every broadcast sent through the API going forward.
4. Submit and Get Approval on Message Templates
Every business-initiated broadcast through the API requires a pre-approved template. Our guide to WhatsApp Business API message templates covers how to structure templates that clear Meta’s review without unnecessary delay.
5. Start at Your Current Tier and Scale Deliberately
Sending consistently and maintaining a strong quality rating moves an account up through the tiers automatically. Sudden spikes in send volume look like spam to WhatsApp’s systems, so steady, relevant sending builds trust faster than trying to maximize volume immediately. Based on existing research, proactive customer service delivered through well-timed, gradually scaled broadcasts produces stronger engagement than infrequent, high-volume bursts.
Common Mistakes That Trigger Broadcast Restrictions
A handful of avoidable errors account for most of the account restrictions businesses run into when trying to scale past the native limits.
1. Using Unofficial Bulk Senders to Bypass the 256 Cap
Third-party tools that claim to bypass WhatsApp’s broadcast limit on the free app operate outside WhatsApp’s terms of service. Accounts using them risk permanent bans, with no appeal path once flagged.
2. Sending to Contacts Who Have Not Opted In
On the API specifically, sending to non-consented contacts is a policy violation, not just a quality issue. Documented opt-in is the deliverability floor, not a best practice to consider later.
3. Ignoring the Two-Marketing-Message Daily Cap
Based on existing research, each user can receive roughly two marketing template messages per day across all businesses combined, not per business. Exceeding this triggers delivery errors and damages sender reputation for the account responsible.
4. Sudden Volume Spikes Instead of Gradual Scaling
An account sending a handful of messages one week and thousands the next looks statistically identical to a spam pattern, regardless of intent. Gradual, consistent scaling protects the account’s quality rating far better than an aggressive push. Our guide to customer service KPIs covers how to track broadcast performance alongside the rest of your channel metrics.
How Qiscus Helps You Scale Beyond the Broadcast Limit
Qiscus is an official WhatsApp Business Solution Provider that removes the native app’s constraints on broadcast messaging entirely. It replaces the 256-contact ceiling with infrastructure built for real business volume.
1. Full Compliance Built In
WhatsApp Broadcast through Qiscus runs on the Business API. There is no 256-contact ceiling and no saved-number requirement, and opt-in and template compliance are enforced automatically.
2. Segmented Campaigns at Any List Size
Contact segmentation and dynamic message variables mean a broadcast to 10,000 contacts can be as targeted and personalized as one to 100. No identical generic text sent regardless of who is on the list.
3. Delivery Tracking That Shows What the Free App Cannot
Every broadcast sent through Qiscus reports delivery rate, read rate, and click data per campaign. That gives a business the analytics the free app has never offered at any list size.
Paragon Technology increased traffic by up to 600% after moving to WhatsApp Business API through Qiscus. That result depended on removing exactly the kind of contact and frequency ceilings this guide has covered. Not working around them with tools that risk the account.
The Limit Is a Signal to Move Platforms, Not a Wall to Work Around
The 256-contact cap and the monthly frequency restriction both exist to keep the free app usable for small-scale, low-volume messaging. Neither one is a bug to exploit or a wall to break through with unofficial tools. They are Meta’s way of pointing serious business messaging toward the Business API, where the same volume becomes fully compliant rather than a spam risk.
Businesses that treat the limit as the signal it actually is move to the API before it becomes urgent. Not after an account restriction forces the decision.
This applies whether the pressure comes from the 256-contact ceiling, the monthly frequency limit, or the missing scheduling and analytics. The free app never offered any of these in the first place. Waiting for one specific limit to bite is usually a sign. The other constraints have already been quietly limiting results longer than the business realized.
Explore official WhatsApp Business API access built for the volume the free app was never designed to handle.
Frequently Asked Questions
The questions below cover what businesses ask most often when they first hit the WhatsApp broadcast limit.
It is exactly 256 contacts per list, not 250. The 250 figure is a common misconception, but 256 is the confirmed cap on both the standard WhatsApp app and the WhatsApp Business app.
No. The API removes the 256-contact cap entirely and replaces it with a tiered daily sending limit. It starts at 1,000 unique recipients per day and scales up to unlimited based on account quality.
You can create multiple lists, and each one is capped at 256 independently, but this does not function as a true workaround. Each list still sends separately with no shared scheduling or analytics. The monthly frequency limit Meta has been rolling out can still restrict how often you send across all lists combined.
Unofficial bulk-sending tools that bypass WhatsApp’s broadcast restrictions operate outside WhatsApp’s terms of service. Accounts using them risk permanent bans with no appeal path, which makes this a significantly riskier option than simply moving to the official Business API.
The most common cause is that those contacts have not saved your phone number in their address book. On the native app, a broadcast only delivers to recipients who have you saved as a contact. The message is silently dropped for anyone who has not, with no error shown. This is exactly why businesses relying on cold or newly acquired contacts tend to see broadcast performance well below what their list size suggests. Moving to the Business API removes this requirement entirely. That shift often produces a noticeable jump in actual reach, not just a technical upgrade on paper.
