WhatsApp Broadcast Limit India: 256 vs 250

Both, for different products. Here are the two systems side by side, every row from Meta's own pages.

Read the third row and the fourth row together, because that is where the money goes. On the free app you can make unlimited lists of 256, which makes the cap sound soft — and in one sense it is, because nothing stops you building twelve lists. On the Platform you cannot make a second portfolio to escape the 250. Meta's wording is explicit that limits are shared, and that one number can consume the whole portfolio's capacity. So the free app's limit is an inconvenience you work around with your thumbs, and the Platform's limit is a real ceiling you have to earn your way past.

One more distinction that matters commercially. The Platform's limit only counts messages sent outside a customer service window — that is, business-initiated templates. When a customer messages you first, your replies for the next 24 hours do not count against it at all. So the limit does not restrict how much conversation your business can have. It restricts how many people you can interrupt.

256, on WhatsApp's own published figure — with a scope caveat worth knowing before you quote it at anyone.

WhatsApp's broadcast-lists help article states it plainly, under the heading "Broadcast list requirements":

> "You can include up to 256 contacts in each broadcast list."

And, in the same article:

> "You can create as many broadcast lists as you like."

(WhatsApp help centre, "How to use broadcast lists", faq.whatsapp.com/861663048350950, read 30 Jul 2026.)

Now the caveat. That article is WhatsApp's general one, with Android and iPhone tabs — the main WhatsApp app. Meta publishes a separate article for the Business app, "How to use broadcast lists on the WhatsApp Business app", and I read it on both the Android and iPhone tabs on 30 Jul 2026. It carries no number at all. Its opening paragraph, in full and verbatim, is:

> "Broadcast lists are saved lists of contacts that allow you to message many of your customers at once. This message will be sent to all customers on the list, as long as they have your number saved in their phones' address book."

No cap appears anywhere in the body of that article. So the honest statement is this: 256 is the figure WhatsApp publishes for broadcast lists, and Meta does not print any figure on the Business-app version of the page. A page telling you flatly that "the WhatsApp Business app caps broadcast lists at 256" is extending the general article's number to a page that does not contain it. It is very probably the same cap. It is not something I can show you Meta writing about the Business app, and if a vendor is quoting it at you as Business-app policy, ask them for the URL.

Two more published facts from the same article that change how you plan a campaign, and both get missed:

Broadcast lists do not work on a computer. Verbatim: "Note: Broadcast lists aren't supported on Windows, Mac, or Web." If your list is 3,000 people, that is twelve lists of 256 selected by hand on a phone screen, with no copy-paste from a spreadsheet and no keyboard. That labour repeats every campaign, and it is the real cost of the free route.

A monthly broadcast limit is being rolled out. A banner at the top of the same article reads, verbatim: "People in some countries might see a monthly broadcast limit. This feature is rolling out gradually and might not be available everywhere. Learn more about broadcast limits." I could not read the linked article's contents — see the section on what I could not verify — so I publish no number and no country list for it. If you are searching for a specific figure you saw in your own app, trust your app over any page including this one.

Because of one rule, and it is the single most consequential fact on this page. The recipient must have your number saved in their phone before your broadcast will reach them. Meta states it three separate ways across two pages, all read 30 Jul 2026:

> "Make sure all contacts in the broadcast list have saved your number in their address book."

> "Only people who've added you to their phone's contacts will receive your broadcast message."

(Both from the broadcast-lists help article, faq.whatsapp.com/861663048350950.)

> "Note: Only contacts who've added your number to their phone's address book will receive your broadcast message. If your contact isn't receiving your broadcast messages, check to make sure they've added you to their address book."

(From the Business-app article, faq.whatsapp.com/653415899610349.)

Sit with what that means for an Indian small business. Your list has 256 people you have served, billed and delivered to. How many of them saved your number? You do not know the split, you did not choose it, and you cannot change it from your end — the action required is on the customer's handset, not yours.

So the effective size of a broadcast list is not 256. It is however many of those 256 saved you. I am not going to put a percentage on that, because we have not measured it and neither has anyone quoting a figure at you. The structural point is what matters: the broadcast list is the only messaging channel where your reach is decided by your customers' phone habits rather than by your list. A business with 200 regulars who all have the number saved gets near-total reach for free. A business with 3,000 customers acquired through ads, marketplaces and walk-ins gets an unknown fraction, silently.

The Business Platform removes that condition entirely — a template goes to a number whether or not you are in their contacts, which is precisely why Meta wraps it in opt-in rules, template approval and a daily ceiling. You are trading an invisible technical filter for a visible policy one. That trade is the whole decision.

Not in messages. This is the mistake that makes most write-ups on this topic unreliable, because the wrong unit changes every calculation built on it. Meta's definition, verbatim:

> "Messaging limits are 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."

(WhatsApp Business Platform messaging limits, developers.facebook.com, page states "Updated: May 21, 2026", read 30 Jul 2026.)

Three things follow from reading that sentence properly.

The unit is the person, not the message. Sending one customer three templates in a day consumes one unit of your limit, not three. So a limit of 250 is not "250 messages a day" — a business running order updates and reminders to the same 250 customers is nowhere near constrained by it. It bites when you want to reach the 251st person.

Replies are free of the limit. "Outside of a customer service window" is doing real work in that sentence. Once a customer messages you, the 24-hour window opens and everything you send back inside it sits outside the count. A business whose customers start the conversations effectively has no messaging limit at all. A business that pushes outward has a hard one.

It is a moving 24 hours, not a calendar day. There is no midnight reset to wait for. Capacity frees up gradually as yesterday's sends age out.

The published ladder, verbatim:

> "Newly created business portfolios have a messaging limit of 250, but this messaging limit can be increased to: 2,000 (by completing a scaling path) / 10,000 (via automatic scaling) / 100,000 (via automatic scaling) / Unlimited (via automatic scaling)"

So: 250 / 2,000 / 10,000 / 100,000 / Unlimited. Only the first step is something you do; every step after it is Meta's decision. And 1,000 is not on that ladder, whatever you read before this page — which brings us to the corrections.

Three of them, and Meta documents all three changes itself, on a page it keeps online specifically for reference. The page carries its own status note — "The changes described in this document are now live, and are only here for reference purposes" — and states "Updated: Jun 17, 2026". I read it on 30 Jul 2026.

Each one changes a decision, so take them in turn.

The 1,000 that became 2,000. If you planned a campaign believing the first step up was 1,000 a day, your schedule is wrong in your favour — the first rung is twice what you budgeted. It also means the tier-up condition and the tier itself are the same figure: Meta's volume-based scaling path asks for 2,000 delivered messages, and the reward is a 2,000 limit.

Per portfolio, not per number. This is the expensive one. The workaround people are commonly sold — add a second WhatsApp number to double your daily sending — does not work and has not worked since October 2025. Meta says the capacity is shared and warns in the same breath that one number can consume all of it. So if you run a main number and a campaigns number in one portfolio, a busy campaigns day can starve your main number's ability to reach new customers. Two numbers is a routing decision, not a capacity decision.

The Flagged rule is gone — and this corrects our own earlier page. On our bulk WhatsApp page I wrote, in the section on what I could not verify, that vendor pages state word for word that seven days at Flagged costs you one tier, that we went looking for that sentence in Meta's documentation and could not find it, and that we would not print it as Meta's wording without showing you where Meta wrote it. I have now found it, and the resolution is better than either possibility I allowed for. The sentence was real Meta wording. Verbatim, from the "Before October 7, 2025" column of the same change table: "The Flagged phone number quality state is possible. If your business phone number quality rating has been set to Flagged for the last 7 days, we will decrease its limit by one level, immediately." It is now superseded, and the same table row says so. The pages copying it were not inventing it. They were quoting a rule that expired, from a document they stopped re-reading.

So, as of 30 Jul 2026, Meta's current messaging-limits documentation contains no downgrade language of any kind. Quality still matters: it can pause or disable individual templates, and it is one of the two criteria Meta names for approving automatic scaling. But the specific mechanic where a bad week costs you a tier is not what Meta currently publishes. If a provider is using tier-loss to sell you a monitoring add-on, that is worth a question.

There are exactly two mechanisms and Meta names both. Getting to 2,000 is something you do. Everything above 2,000 is something Meta does to you.

Step one: 250 to 2,000. Verbatim: "You can increase your messaging limit to 2,000 by completing one of the scaling paths below." The three paths, verbatim:

> "Verify your business" > > "Have your partner verify your business (if you were onboarded by one)" > > "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."

And then, verbatim: "Once you complete one of these paths, Meta analyzes your message quality. Based on this analysis, your business portfolio's eligibility for automatic scaling will either be approved or denied."

Here is the honest arithmetic on those three, because for most Indian small businesses only one of them is real. The third path asks for 2,000 delivered messages to unique numbers inside a moving 30-day window. At a 250 limit that is eight consecutive days of sending to your absolute ceiling, and it requires you to have 2,000 opted-in customers you are willing to message in the first place. A clinic with 800 patients or a showroom with 1,200 enquiries cannot complete that path at all, however patient it is. Business verification is the path that actually applies to a small business, and it is paperwork rather than volume. Start it before the season you care about, not during it.

Step two and beyond: automatic scaling. Two criteria, verbatim:

> "You are sending high-quality messages across all of your business phone numbers and templates" > > "In the last 7 days, your business has utilized at least half of your current messaging limit"

> "If these criteria are met, your portfolio's limit increases by one level within 6 hours."

One honest gap in that second criterion, because it is the one people plan around. Meta does not spell out whether "utilized at least half of your current messaging limit" means half of the daily limit reached on a single day inside that week, or half aggregated across the seven days, and I found no worked example on the page. So I am not going to hand you a target number and present it as Meta's. What is unambiguous is the direction: the ladder does not run ahead of your actual sending. You cannot pre-provision headroom before a festival rush, because Meta only raises the ceiling for a business already pressing against it. Two practical consequences follow. A business that runs one campaign a month will sit at its tier indefinitely, and that is completely fine. A business that genuinely needs 10,000 in December should be sending real volume in October.

Where to read your actual limit. WhatsApp Manager shows your current limit, and that is the number to trust over any tier a vendor quotes you. If you or your developer read it through the API, note that Meta has changed the field: "The messaging_limit_tier field, which used to return a business phone number's messaging limit, has been deprecated. Request the whatsapp_business_manager_messaging_limit field instead." (messaging-limits documentation, read 30 Jul 2026.) A dashboard still calling the old field is a dashboard nobody has maintained since the October 2025 change, which is a fair proxy for how current the rest of that vendor's WhatsApp knowledge is.

Divide your list by your current limit. That is the whole calculation, and it is the one that decides whether a time-bound offer is even possible.

A 3,000-person list at the starting tier is a twelve-day campaign. Say that out loud before you plan a festival offer. A Diwali message that reaches the last 250 people on day twelve is not a Diwali message. A limited-time discount that runs for a week cannot be announced to everyone inside that week. The offer has to be built around the delivery schedule, not the other way round.

Three ways to handle it, in the order I would try them.

Complete business verification first. On the table above it converts twelve days into two. It costs paperwork and time rather than money, and it is the highest-return thing a new Platform account can do.

Send in value order rather than alphabetical order. If the send takes twelve days regardless, the people who buy most should be in the first day's 250 and not the twelfth's. Breaking a list into daily batches forces a ranking decision that is usually worth making anyway.

Change the shape of the campaign so replies do the work. The limit only counts business-initiated messages. Reach 250 people today and every one who writes back opens a 24-hour window in which the conversation is unconstrained by the limit. A campaign designed to start conversations runs into the ceiling once. A campaign designed to broadcast at people runs into it every day.

The free-app version of the same arithmetic, for completeness: 3,000 contacts is twelve broadcast lists of 256, each built by selecting contacts by hand on a phone because broadcast lists are not supported on Windows, Mac or Web, and each message reaching only those recipients who have saved your number. There is no daily cap to work around there. There is also no reporting, and the labour repeats every campaign.

The two limits produce different symptoms, and the fix for one is useless against the other. This is the diagnostic table I would run before spending anything.

The crossover point is easier to name than most vendors will admit. Under a few hundred contacts who mostly have you saved, stay on broadcast lists. They are free, entirely within the rules, hold 256 each, and you can make as many as you like. The address-book condition, which is fatal at scale, is barely a constraint for a business whose customers all saved the number — that is exactly the business the feature was designed for, and templates, approvals, opt-in records and a credit balance would all be overhead bought for no gain.

From a few hundred to a few thousand, mostly acquired through ads or marketplaces, the Platform is the right move — and the first thing to do on it is business verification, not a campaign.

And one case where the answer is simply no, regardless of tier: you bought a list. There is no compliant way to broadcast to it and no tier that makes it work. The rules on that are set out in is bulk WhatsApp legal in India.

Broadcast lists on the free app cost nothing. No per-message charge, no platform fee, no account to open. That is a genuine advantage below a few hundred contacts and I would not talk anyone out of it.

The Platform charges per message. Two Indian platforms publish an India rate card openly. Both sets of figures below are pricing-card values from those vendors' own pages rather than sentences they wrote in prose, and both vendors attach their own warning that the numbers move with Meta's policy.

MyOperator's card adds the note, verbatim: "Price for Indian destination numbers. Subjected to change as per Meta's policies." Neither page publishes Meta's own rate beside its own, so I cannot show you whether either card is Meta's charge passed through at cost or carries a margin, and I will not guess. Multiplying the range out — my arithmetic on their published figures, not a quote from either vendor — 3,000 marketing messages sits between ₹2,580 and ₹2,850 on those two cards. What your own Meta invoice will read is a separate question that I have no primary source for.

I am deliberately not rebuilding the whole bill on this page, because it already exists on this site and duplicating it would make both pages worse. The four cost lines on a WhatsApp bill are worked through on the WhatsApp Business API cost page, the provider board is on WhatsApp API providers in India, and a full month-one credit table for a 3,000-member campaign — ours included, with the part that does not flatter us — is on is bulk WhatsApp legal in India.

The one cost line that belongs on this page is what happens after the limit has been respected and the messages have landed. Replies are free on Meta's side, they are the point of the campaign, and they arrive in the evening after the counter staff have gone home. With us they are ₹2 per conversation — a conversation being the 24-hour window with one customer, not each message, so fifteen messages back and forth across a day is ₹2 — with no subscription and no platform fee, and Meta bills your own WhatsApp account at Meta's rates with zero markup from us, so the two invoices stay separate and you can audit ours against theirs. Our claim is about terms, not about being the lowest number on anyone's page: ₹2 per conversation and ₹2 a minute from the very first one, no subscription, no minimum volume, no lock-in. If all you want is to push 3,000 templates out of the door and nobody needs to answer the replies, a platform with published plans will do that for less than we will, and you should buy one. The full price list is on /pricing.

Stated plainly, because a page that projects total certainty about a system Meta re-wrote nine months ago is telling you something about its author. All as of 30 Jul 2026.

The size of the new monthly broadcast limit, and whether India is affected. WhatsApp's banner confirming that the limit exists is quoted in full earlier on this page. The article it links to is real — its title is "About broadcast limits" and it sits at faq.whatsapp.com/1176325363861991 — and I confirmed that title myself. The body never rendered across roughly a dozen attempts; the help centre throttled the session, direct requests returned an error and automated fetches returned only the page title. So I read no number and no country list, and I publish neither. If you have seen a specific monthly figure in your own app, your app is a better source than this page. Ask your provider for Meta's URL if they quote you one.

Whether the 256 cap is published for the WhatsApp Business app specifically. It is not. Meta's Business-app broadcast-lists article carries no numeric cap on either the Android or the iPhone tab. The 256 comes from the general broadcast-lists article. I have quoted each to its own page rather than merging them.

What "utilized at least half of your current messaging limit" means precisely. Meta states the criterion but does not define whether it is half the daily limit on one day inside the seven, or half across the week. I did not find a worked example, so I have not published a target number.

Delivery rates on broadcast lists. We have not measured what share of a typical Indian business's customers have saved its number, so we publish no percentage and you should distrust anyone who does. The rule is certain; the size of its effect on your list is not, and it varies with how you acquired your customers.

Whether a per-user cap limits how many marketing messages one person receives per day across all businesses. Widely reported, and not something I could confirm in Meta's own documentation — the same open item our bulk WhatsApp page records. If it is real it matters for campaign timing, so ask for the source before planning around it.

What Meta's India rates will be next quarter. Both published rate cards quoted above carry their own publishers' warning that the figures move with Meta's policies. Rates in this market changed within weeks while we were collecting them, so treat 21 Jul 2026 as a hard check date.

The honest division of labour, because half of this is not something any vendor can do for you.

One thing we will not do: send to a purchased or scraped list. We decline the build if that is the plan, and it is not a negotiation.

On the commercial side, stated plainly rather than as fine print. The custom setup is ₹40,000 and is free for our 10 founding clients, in return for the Care Plan for the first three months at the founding rate and an honest testimonial plus a short case study after go-live. The Care Plan lists at ₹12,000 a month and is ₹5,000 at the founding rate locked six months — required for months one to three, optional from month four. Credits are pay-as-you-go from one balance: minimum first load ₹10,000, later top-ups from ₹500, credits never expire.

If you want the mechanics of running a campaign where the replies are the point, that is written up in WhatsApp campaigns with AI replies. The definition of the underlying product is in the glossary under WhatsApp Business API. The founding-client build is on /pilot, and if you would rather ask a person, /contact reaches me.

You can also just message our own live agent on WhatsApp at +91 79956 76588 and watch it answer before you decide anything.