WhatsApp Template Message Character Limits (2026)

The WhatsApp template message character limit for the body is 1,024 characters. The header and footer are each capped at 60 characters each, and buttons are limited to 25 characters per label.

Memorizing these numbers isn't the hard part. The real risk is forgetting that your variables count toward them once a real customer name or order number gets substituted in.

Below is the quick-reference version for each component, followed by the full limit table, where sources disagree, and how to test a template before it gets rejected for length.

The Complete WhatsApp Template Character Limit Table

A WhatsApp template is built from a handful of parts: the template name, the body, an optional header and footer, and optional buttons. 

Each one has its own character limit, and some limits change depending on the template's category or the button type you pick. The table below lists every one of them in a single place.

A quick note on the button-label number: Meta's current template component documentation states 25 characters for quick-reply, URL, and phone-number button labels. You will still find some older third-party integrator docs citing 20 characters. If your provider's editor enforces a stricter number, follow what it actually accepts over what any article (including this one) states, since Meta's component specs are periodically revised.

Bonus Read: WhatsApp Template 101: Types, Benefits, and Examples

How WhatsApp Variables Count Toward the Limit

Meta requires you to supply a sample value for every variable when you create a template, and replaces the placeholder with the real value at send time. 

• Named parameters must be unique, lowercase, and use letters, numbers, and underscores. Positional parameters must stay in order.
• The limit that matters is the rendered message, not the literal template source:
• literal text + substituted variable value(s) ≤ component limit.
• Test with your longest plausible real value for every variable, not the placeholder token, and leave a buffer below the hard limit rather than targeting it exactly.

For example, a body written as "Hi {{customer_name}}, your order {{order_id}} ships {{ship_date}}." looks short in the editor. 

If {{customer_name}} becomes "Alexandria Montgomery-Whitfield-Osei" and {{order_id}} becomes a 24-character tracking code, the rendered body is a lot longer than it looks. 

Rules That Affect Length Beyond the Raw Character Count

Staying under the character limit doesn't guarantee approval. Meta rejects templates for how the content is used, not just how long it is, so a technically compliant template can still fail for the wrong reason.

• Category matters more than length: Marketing templates can promote products, offers, or renewals. Utility templates must stay non-promotional and tied to a specific user action or request: mixing a promotion into an order update can get a utility template reclassified as marketing.
• Authentication templates are locked down: You don't write custom body text for OTP templates. Meta controls the core wording, and you're limited to the supported OTP button plus optional, also Meta-controlled, security or expiration text.
• Vague body content gets rejected regardless of length: A body that's just {{1}} or "Congratulations!" with no context is a common approval failure. State clearly why the customer is receiving the message.
• Every variable needs a realistic example: Ideally, your longest expected value, submitted at creation time for Meta's review.
• Text headers reject Markdown special characters: keep header copy plain.
• Encode URL variables: URL variable values need percent-encoding for special characters, or delivery/validation can fail.
• Approval isn't permanent: Only an approved template can send, and quality ratings can change after the fact based on user engagement.

Best Practices for Writing WhatsApp Templates

These habits keep templates readable, faster to approve, and easier to maintain across languages.

1. Lead with the point: "Your order {{order_number}} ships today" beats a preamble before the useful information.
2. Stay well under 1,024 characters in the body: shorter copy reads better on mobile and tends to have an easier approval path.
3. Keep button labels to a few words: even though 25 characters are technically allowed, shorter reads better on small screens regardless of the limit.
4. Put stable, explanatory copy directly in the body text: reserve variables for genuinely dynamic, bounded values.
5. Use the footer for one compact detail: a deadline, an opt-out instruction, or a support line, kept well under 60 characters.
6. Test every translated language separately: a translation is often longer than the English source, and Meta doesn't translate your template text for you.
7. Create a new template rather than combining objectives: don't fold a discount offer into a utility order-status template.
8. Before submitting, render your worst-case example: count characters after substitution, with roughly a 10-20% buffer below the limit.

Creating and Sending Templates in Wati

Wati covers the full lifecycle, from building a template to sending it to tracking how it performs.

• Creating: Wati's template creation flow walks through choosing a category and language, writing body text, inserting variables, and configuring an optional footer, header, and buttons. Save as a draft to review the rendered text before submitting for Meta's review.
• Sending: Wati's V3 template-send endpoint accepts the template name, recipient list, and per-recipient variable values, returning request- or recipient-level errors. It's a delivery API, not a validator, so check the rendered length against Meta's limits before you submit.
• Tracking: Once live, Wati's campaign analytics show read, reply, and click-through behavior by template, a practical signal for spotting an underperforming template and revising the next one.

Ship Templates That Get Approved the First Time

Templates that respect the character limits and account for what variables do to them once real data is substituted in clear Meta's review faster and get resubmitted less often. 

Wati's template editor, sending API, and campaign analytics cover the rest of the workflow, but the character count is still on you to check. Get it right, and the approval process comes down to clarity and category, not length.

Building templates that stay compliant and convert? Book a free demo to see Wati's template editor and approval workflow in action.