WhatsApp Cloud API pricing in 2026: what you actually pay per message
Meta's per-message model has been live since July 2025, and the last free category ends on 1 October 2026. Here is what actually lands on the bill, and what stays free.
Meta's per-message model has been live since July 2025, and the last free category ends on 1 October 2026. Here is what actually lands on the bill, and what stays free. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
- The pricing model you remember is gone
- The four categories, and which ones you pay for
- What stays free after 1 October
- The two details that decide whether October touches you
- A payment method is now mandatory
- The window is still your biggest cost lever
- How to model your own bill in ten minutes
- Related Reading
Most businesses ask me the same question before they commit to WhatsApp: what does this actually cost?
The honest answer changed twice in eighteen months, and the second change lands tomorrow. On 1 October 2026 Meta stops giving away service messages. If you are working out your numbers today, you need the current model, not the one from a 2024 blog post.
Here is the plain version.
The pricing model you remember is gone
Until July 2025, WhatsApp charged per conversation. You paid once for a 24-hour window and could send as many messages as you liked inside it, of any type.
Since 1 July 2025 that is finished. Meta charges per delivered message, priced by the category of the message and the country code of the recipient. Sending ten messages where one would do now costs ten times as much.
That single change did more to WhatsApp budgets than any rate increase, because it punished exactly the flow most businesses had built: a chain of short automated replies inside one conversation.
If you have not yet settled the more basic question of whether you need the API at all, start with WhatsApp Business API vs the WhatsApp Business app. The cost model below only applies once you are on the API.
The four categories, and which ones you pay for
Every message you send falls into one of four buckets.
- Marketing templates: always charged. Promotional by definition, so no free window applies.
- Authentication templates: always charged. These verify identity and never ride a service window.
- Utility templates: charged outside an open customer service window, and charged inside it too from 1 October 2026.
- Service messages: the free-form replies your team sends inside the open window. Free for the first 1,000 per phone number each month, then charged.
Anything a customer sends to you is never charged. Inbound is free, always.
What stays free after 1 October
Two things survive the change, and both matter when you model your bill.
First, the 1,000 free service messages per business phone number, per calendar month. It is per number, not per account, and it does not roll over. Unused messages expire at the end of the month, so you cannot bank them. A support team answering a handful of conversations a day stays inside the allowance. An automated flow that fires six short replies per conversation burns through it fast.
Second, the 72-hour free entry point window is untouched. A conversation that starts from a click-to-WhatsApp ad or a click-to-chat button makes all message types free for 72 hours, templates included. This is still the cheapest way to start a paid conversation, and most businesses forget it exists.
I keep the full ruleset on the canonical page: WhatsApp Business Platform pricing explained. Read that if you want the category-by-category table.
The two details that decide whether October touches you
The change is architectural, not commercial. Your bill depends less on how many customers you have and more on how your flows are built.
Detail one: the free allowance is shared and does not roll over. One-to-one and group deliveries both draw from the same 1,000. A group message counts one unit per recipient it reaches. If you run group announcements, the allowance can disappear in a single send.
Detail two: service messages get no volume tiers. Marketing and utility rates fall as volume grows. Service messages do not. Their rate never drops, no matter how much you send. That means a high-volume automated support flow now carries a real per-message cost that will not shrink with scale.
A payment method is now mandatory
This is the part that trips people up on the first of the month. A payment method must be attached to the WhatsApp Business Account.
Without one, Meta delivers your first 1,000 service messages of the month and then stops delivering. It does not queue them. They are not sent later. They are simply not sent.
For a business that answers enquiries, silent non-delivery is worse than a bill. Check this before 1 October, not after.
The window is still your biggest cost lever
The 24-hour customer service window has not changed. It opens when a customer messages you, and restarts with every new message from them. Inside it you can send any message type without a template.
That gives you one clear rule for designing flows: make routine confirmations land while the window is open. An order update, a delivery note, a booking confirmation. If those go out inside the window they are service messages, covered by the free allowance. If they arrive a day later, they need an approved utility template and are charged from the moment they are delivered.
Same message, different cost, decided entirely by timing.
How to model your own bill in ten minutes
Do this before you commit to any platform.
- Count your monthly conversations, not your customers.
- Multiply by your average outbound messages per conversation. This is the number October changes.
- Subtract 1,000 per phone number. If your result is negative, you pay nothing for replies.
- Add your marketing and authentication templates, which were always charged.
- Add utility templates sent outside the window.
If that arithmetic is uncomfortable, the fix is usually flow design, not a cheaper provider. Every platform on the market bills on Meta's rates, because Meta sets them. A provider is not a discount on message cost, it is a layer on top of it. That is why I tell people to choose on inbox, automation and reliability, not on a rate card that is identical everywhere.
If you want a second opinion on your numbers, or a view on how BNex handles the shared inbox and campaigns on one verified number, message me on WhatsApp at wa.me/917358722745. I will tell you honestly whether you are inside the free allowance or not.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.