WhatsApp Broadcast Limit: What It Is and How to Send Beyond It
WhatsApp broadcast limit is 256 contacts per list. Learn why the limit exists, what happens when you hit it, and how to send bulk WhatsApp messages to larger lists without getting banned.
Kartik Patel
Head of Delivery
Contents
Contact us
Overview: The WhatsApp broadcast limit is 256 contacts per list on the free app and WhatsApp Business App. Messages go out as individual private chats, so recipients never see each other. The limit exists because WhatsApp requires recipients to have your number saved before the message delivers. This guide covers why the 256 limit exists, what the WhatsApp broadcast message limit means for delivery, and the practical options for sending to lists larger than 256 without getting your account flagged.
Most businesses hit the WhatsApp broadcast limit within the first week of using it seriously. A list of 300 clients. A promotional send to 500 leads. A reminder campaign to 1,000 registered contacts. The native broadcast list stops at 256 and has no scheduling, no personalisation beyond what you type, and no delivery tracking. A WhatsApp bulk message sender free tool built on WhatsApp Web sidesteps the 256 cap entirely, removes the saved-contact requirement, and adds scheduling and message activity tracking. This guide explains the broadcast limit in full, why it works the way it does, and what your options are once you need to go beyond it.
The WhatsApp broadcast limit is 256 contacts per list. This applies to both the standard WhatsApp app and the WhatsApp Business App. You can create multiple broadcast lists, but each list is capped at 256 recipients and each send goes out separately.
A broadcast message is not a group message. Each recipient receives it as a private individual chat, exactly as if you had messaged them directly. They cannot see who else received it. Their replies come back to you as private conversations. The 256 figure is the hard ceiling on how many people can receive one broadcast in a single send.
Feature | Free App and Business App |
Max contacts per broadcast list | 256 |
Recipients see each other | No |
Replies | Private, one-on-one |
Scheduling | No |
Message personalisation | None (same message to all) |
Delivery tracking | No |
Recipient must have sender's number saved | Yes |
Available on desktop or web | No — mobile only |
The 256 limit is not the only constraint. The more consequential one is the saved-number requirement.Also Read: WhatsApp Message for Event Invitation: 17 Templates and How to Send in Bulk
WhatsApp designed the broadcast feature for personal use: a family group announcement, a team update, a small-business promotion to a tight known audience. The 256 limit is a deliberate friction point. It discourages mass unsolicited messaging and keeps the feature within a range where the sender genuinely knows every recipient.
From WhatsApp's perspective, a broadcast to 256 people who all have your number saved is a trusted communication. A broadcast to 10,000 numbers sourced from a directory is spam. The limit enforces a floor of prior relationship before any message delivers.
This is also why the WhatsApp broadcast message limit is tied to the saved-number requirement. If a recipient does not have your number saved, the message does not deliver regardless of how many contacts are on your list. The two constraints work together to limit broadcast to genuine two-way relationships.
Rule: The broadcast limit is not punitive. It is a design constraint that ties reach to relationship. Every workaround that bypasses it needs to respect the same underlying principle: only message people who recognise you.The 256-contact cap is the stated limit. The saved-number requirement is the actual delivery constraint most businesses encounter first.
When you send a broadcast, WhatsApp checks whether each recipient has your number saved in their phone contacts. If they do not, the message does not deliver. It will show as sent on your end but will never arrive on theirs. No error message. No notification. The message simply does not reach them.
For businesses with warm, established contact lists where every recipient has interacted with the business before and likely has the number saved, delivery is reliable. For any list that includes leads, new enquiries, or contacts collected at events or through forms, a significant portion of the list will not receive the broadcast.
In short: The saved-number requirement is not a technical bug. It is WhatsApp's primary spam filter for broadcast. A contact who has not saved your number has not established a relationship with you on WhatsApp, and the platform treats that as a reason not to deliver your message.If you are regularly seeing single grey ticks on broadcast messages that you expect to be delivered, this is almost always the cause. For a full breakdown of WhatsApp delivery failures, see our guide on why WhatsApp messages are not being delivered.
The WhatsApp Business API lifts the 256 limit with a tiered structure. Tiers are based on account history and message quality. Each tier represents the number of unique users a business can message in a 24-hour period.
Tier | Daily Sending Limit | Requirement |
Free App / Business App | 256 per list (no daily cap stated) | Recipients must have number saved |
API Tier 1 | 1,000 unique contacts per day | Verified business account |
API Tier 2 | 10,000 unique contacts per day | Consistent quality history |
API Tier 3 | 100,000 unique contacts per day | Strong quality track record |
API Tier 4 | Unlimited | High-volume established accounts |
Since late 2025, Meta shifted from per-phone-number limits to Business Portfolio limits. This means your daily sending capacity is shared across all phone numbers registered in your Meta Business Manager, not tracked per number separately.
The API also removes the saved-number requirement. Recipients receive messages as long as they have opted in to receive communications from that business. Template messages, which must be pre-approved by Meta, are required for sending outside of an active 24-hour conversation window.
Important: The Business API requires a Meta-verified business account, approved message templates, and integration through a Business Solution Provider. It is not a quick switch. For businesses that need to go beyond 256 contacts without API approval, browser-based tools are the practical alternative.Also Read: 10 WhatsApp Marketing Examples That Actually Work (2026)
Three options exist for reaching multiple WhatsApp contacts at once. They are not interchangeable.
Broadcast List | WhatsApp Group | Browser-Based Tool (Roklo) | |
Contact limit | 256 per list | 1,024 members | No fixed cap |
Recipients see each other | No | Yes | No |
Saved number required | Yes | No | No |
Scheduling | No | No | Yes |
Message personalisation | None | None | Name variable ({{name}}) |
Delivery tracking | No | No | Yes |
Anti-ban interval management | No | No | Yes (built-in) |
Cost | Free | Free | Free |
The broadcast list is the right tool when your list is under 256 contacts, all recipients have your number saved, and you do not need scheduling or tracking. For anything beyond that, a browser-based tool is the practical path that does not require API approval or business verification.
For context on how these approaches work in real business scenarios, see our WhatsApp marketing examples that cover flash sales, appointment reminders, and lead nurture sequences across different contact sizes.
When your contact list exceeds 256, the broadcast feature in WhatsApp gives you two options: stop at 256, or create multiple broadcast lists and send separately to each.
Option 1: Multiple broadcast lists
You can create as many broadcast lists as you need. A list of 600 contacts becomes three lists of 200. You compose the same message and send it from each list one by one. WhatsApp does not prevent this. The practical problems are time, no scheduling, no tracking of which contacts received which send, and the saved-number requirement still applies to every contact on every list.
Option 2: Browser-based bulk sending
A browser-based tool connects through your WhatsApp Web session. You import your full contact list via CSV or Excel, create segments, set up a message template, and schedule a single campaign. The tool spaces the messages automatically to stay within WhatsApp's safe usage patterns. Recipients do not need to have your number saved. The full list receives the message in one campaign.
Multiple broadcast lists solve the 256 problem at the cost of significant manual effort. A browser-based tool solves it in one campaign.
The step-by-step process below uses Roklo. The same logic applies to any browser-based tool that connects via WhatsApp Web.
Step 1: Import your full contact list
Open Roklo in your browser and click Sync your WA to import your existing WhatsApp contacts. For contacts not already in your WhatsApp, use Import Excel. Your spreadsheet needs a phone number column with country code. A name column enables personalisation via the {{name}} variable.
Result: your full contact list is visible in Roklo regardless of size, with name, phone number, and connection type.
Step 2: Segment into groups
Go to Groups and create segments based on how you want to target your sends. Existing clients, active leads, contacts by city or product interest. Segmentation is the single most effective protection against spam reports: a relevant message to a targeted group performs better and gets flagged less than a generic blast to your full list.
Step 3: Set up your message template
Go to Templates and write your message. Use the {{name}} variable at the opening. Keep the message under 300 characters where possible. State the purpose in the first sentence. One clear action. An opt-out line.
Step 4: Create a campaign and schedule
Go to Campaigns and click New Campaign. Select your template and contact group. Choose Schedule for Later to set a send date and time, or send immediately via Message Now. Roklo's anti-ban engine spaces messages automatically. No manual pacing required.
In short: Four steps: import contacts, segment into groups, set up the template, schedule the campaign. No 256 cap. No saved-contact requirement. No manual interval management.For a full guide to the send process including troubleshooting delivery issues, see our guide on how to send bulk WhatsApp messages.
Removing the 256 cap does not mean sending 5,000 messages overnight on a new number is safe. WhatsApp's spam detection monitors the rate of change in account behaviour, not just the total volume. An account that jumps from 10 messages per day to 800 overnight is flagged regardless of list quality.
Account History | Recommended Daily Volume | Key Guidance |
New number (under 1 month) | 50 to 100 messages per day | Start low. Build sending history before scaling. |
Established (1 to 6 months) | 200 to 500 messages per day | Increase in weekly steps, not daily jumps. |
Active (6 or more months) | 500 to 1,000 messages per day | Consistent daily patterns. No sudden spikes. |
Account warm-up: If you are starting bulk sends for the first time on a number, begin at 50 to 100 messages per day for the first two weeks. Increase by 50 to 100 per week after that. A gradual ramp-up builds a safe sending history. A sudden spike on a new number is the most reliable way to trigger a restriction.Only message contacts who recognise you
The saved-number requirement on native broadcast exists for a reason. When you send beyond the limit using a browser-based tool, the technical constraint is gone but the underlying principle is not. Contacts who do not know you will report your message. Spam reports are the fastest path to an account ban.
Include an opt-out line in every message
Reply STOP to unsubscribe. A contact who opts out is one fewer potential spam report. On a list of 500 contacts, five or six opt-outs that you honour are far less damaging than the same contacts becoming spam reports.
Do not send the same message twice to the same group
Duplicate sends to the same contacts accumulate reports faster than any other pattern. If a campaign did not get the response you expected, change the message before the next send. Do not resend the same content.
Monitor message activity after every campaign
Check Message Activity in Roklo after each send. A drop in delivery rates or a rise in non-delivery signals may indicate your account is being throttled. If you see this pattern, reduce volume and pause for 48 hours before resuming at a lower rate.
For the complete breakdown of ban triggers and how to avoid them when sending beyond the broadcast limit, see our guide on how to send bulk WhatsApp messages without getting banned.
The WhatsApp broadcast limit of 256 contacts per list is a deliberate design constraint, not a technical ceiling. It is tied to the saved-number requirement, which means the real delivery limitation is prior relationship rather than a hard number. Once you understand why the limit exists, working within it or around it becomes straightforward.
For lists under 256 with all contacts having your number saved, native broadcast works. For anything larger, requiring scheduling, or where not all contacts have saved your number, a browser-based tool removes all three constraints in a single workflow.
If you want to send to your full contact list beyond the 256 cap without API approval or manual interval tracking, Roklo handles the complete flow from your browser as a free bulk message sender. Open your browser, sync your contacts, and your first campaign beyond the broadcast limit is live in minutes.
