WhatsApp Status Ads in 2026: Sizes, Safe Zones, and the Spec Sheet Meta Never Wrote (Verified July 2026)

Meta has never published a creative spec for WhatsApp Status ads: its Ads Guide URL for the placement returns a 404, and business.whatsapp.com lists no dimensions, no file caps, no character limits. Everything below is sorted by what it actually is, verified July 2026: the Meta-official facts on destinations, targeting, and rollout; the 1080 x 1920 consensus every practitioner runs; and the conflicting safe-zone figures reconciled instead of averaged.

The 2026 WhatsApp Status Ads Spec Table

Verified July 2026 against Meta's June 16, 2025 Newsroom announcement, business.whatsapp.com, and the WhatsApp Help Center. Meta publishes destination behavior and privacy rules for this placement but no creative dimensions at all; every size below is cross-checked secondary consensus, and where guides conflict, the table says so instead of picking a side.

One number circulating that belongs in no table: 1080 x 1620 as "the Status safe area". No source, Meta or secondary, actually cites it. The figures that do exist, and where each comes from, are drawn to scale in the safe-zone section.

Status Ads vs Posting a Status: Not the Same Spec Problem

Nearly every page ranking for WhatsApp Status sizes is a design tool reciting 1080 x 1920 for organic Status posts, with a resizer attached. Organic posting is a different problem: WhatsApp compresses your upload, applies its own limits, and gives you no CTA. Status ads are bought in Meta Ads Manager, render full screen between your contacts' updates in the Updates tab, carry a tappable CTA, and never touch your chats. The canvas happens to be the same 9:16 that Instagram Stories use, which is why your Stories export is the right starting file, but the UI drawn over it is WhatsApp's own, and that difference is the entire safe-zone question below.

Image Status Ad Specs

Build at 1080 x 1920, JPG or PNG. The ~16 MB file cap comes from secondary sources only, and character limits for any text field on the placement are unpublished; Stories parity is likely but unconfirmed, so put the words you need on the creative itself, inside the safe band. The ad displays full screen on a timer between organic updates, with your business name and the Sponsored label at the top and the CTA at the bottom, both drawn over your pixels.

Video Status Ad Specs

MP4 at 1080 x 1920 is the consensus container; Meta publishes no file size cap. Duration is the field where the guides openly contradict each other: 30 seconds, 60 seconds, and 90 seconds all circulate as "the limit", and none of them traces back to a Meta page.

The Spec Sheet Meta Never Wrote

For most placements, Meta's Ads Guide is the tiebreaker. For Status ads there is nothing to break ties with: the 404 and the empty marketing page are the whole official record. That leaves every hard number on every page ranking for this query, including this one, secondary. The difference is knowing which is which:

• Meta-official: Status is a placement bought through Ads Manager; ads appear only in the Updates tab, "away from your personal chats"; a tap can open a WhatsApp chat, a website, or (soon) an app; targeting excludes message content; the rollout dates and the EU timeline.
• Secondary consensus, stated as such: 1080 x 1920 at 9:16, the ~16 MB image cap, MP4 for video, the objective set (Engagement, Traffic, Messages).
• Published nowhere: a safe-zone template, a video duration cap, a file size cap for video, character limits. Anyone printing a hard number for these fields is guessing, and the contradictions between the guides prove it.

Safe Zones: The Conflict Is the Spec

Status chrome sits on top of your creative: the progress bar, business name, and Sponsored label at the top, the reply bar and CTA button at the bottom. Meta has never said how many pixels either band eats, so the secondary sources each invented a figure, and they do not agree. Rather than pick a winner, here is every claim drawn to scale over a real 1080 x 1920 ad, with the one zone that survives all of them.

The claimed unsafe bands, drawn to scale

0-120 px: unsafe in every sourceto ~250 px: Chatarmin

0-200 px: unsafe in every sourceto ~400 px: Chatarmin

clear under every reported figurecentral 1080 x 1270

Dark amber: the top status UI and bottom reply-bar zones every source marks unsafe. Light amber: the extra area the most conservative claims add. Green: safe under all of them.

Every figure on the record

120 px top / 200 px bottomResizer tool page (moda.app)

The least conservative band claim on record

~250 px top / ~400 px bottomVendor guide (Chatarmin)

The most conservative band claim on record

1080 x 1330 visibleVendor blog (helo.ai)

Top/bottom split unstated

1080 x 1420 visibleVendor blog (Chatarmin)

Conflicts with the same vendor's band figures

~1080 x 1600 visibleVendor blog (progbiz)

Matches moda.app's 120/200 bands

250 px top / 672 px bottomMeta's 9:16 Stories template

Real template, wrong surface: it is not Status-specific

1080 x 1620No source on record

Circulates widely; nobody cites an origin. Skip it.

Meta-published safe zoneNone exists

The only official answer for this placement

The reconciliation, not a fake number: build at 1080 x 1920, keep headline, CTA, and logo inside the central band, roughly 250 px clear at the top and 400 px clear at the bottom, and every published claim is satisfied at once.

1:1

9:16

One 9:16 export covers Stories, Reels, and Status.

The free Meta Ad Resizer reframes square or landscape creative into 9:16 without cropping (this pair is its real output). The resizer tools ranking for this query crop to 1080 x 1920; this one reframes, and this page tells you where the UI bands sit.

Resize an ad free

The Surface by Meta's Own Numbers

The reach number that matters for this placement comes from Meta's announcement post: 1.5 billion people open the Updates tab, where Status and Channels live, every day. WhatsApp itself passed 3 billion monthly users in 2025, per Meta's earnings. The "500 million statuses posted per day" figure is commonly cited but no longer confirmable on a live Meta page, and the ~2.3 billion daily-user estimates you will see are third-party numbers, not Meta's.

Meta's own framing of the placement doubles as the trust math for skittish stakeholders: "Subscriptions, promotions and ads will appear only on the Updates tab, away from your personal chats." And on data: "Your personal messages, calls and groups you are in will not be used to determine the ads you may see", plus "We will never sell or share your phone number to advertisers." End-to-end encryption stays intact; targeting runs on country or city, language, Channels followed, ad interactions, and cross-Meta signals only when the user links WhatsApp to Accounts Center.

Three Status-Ready Example Ads

Status ads run between friends' casual updates, so shot-on-phone energy beats studio gloss here. All three examples are real 9:16 files shown inside the Status unit they would occupy, with headline, CTA, and badge held in the central band the safe-zone section maps; the top and bottom of each photo carry no text at all.

SSpice RouteSponsored

Chat with us

Click-to-chat native: the offer, the green chat pill, and the trust badge all sit at half height, clear of both UI bands the page maps above.

KKYTESponsored

Send us a message

Built for the Status-heavy markets: a COD badge plus a message CTA does the work of a landing page in India, Brazil, and Indonesia.

GGloss StudioSponsored

Book on WhatsApp

It runs between friends' updates, so a candid mid-service frame reads native; a studio banner in the same slot reads as an intruder.

Buying Path, Destinations, and the Boring Fields

Status ads are bought in Meta Ads Manager only; the "Create an ad" button on business.whatsapp.com deep-links straight into it. There is no self-serve ad buying inside the WhatsApp Business app, and secondary sources consistently report a connected Facebook Page as a requirement. Status arrives as a placement, included through Advantage+ placements or selected manually. One delivery quirk repeated across guides but never Meta-confirmed: manual-placement Status delivery reportedly requires Instagram Stories left enabled, so verify in Ads Manager before building an isolation test around it.

The tap destinations are the placement's best-documented spec field, and Meta is explicit about the flagship one: "When people click on your ad, they are taken directly into a WhatsApp chat with your business." Three destinations exist: a WhatsApp chat (the click-to-WhatsApp flow, with Send Message and Chat on WhatsApp buttons), a website, and an app, which Meta marks as coming soon. Website destinations use the standard Meta CTA set per secondary sources. Reported objectives are Engagement, Traffic, and Messages, with click-to-WhatsApp running through the Messaging Apps conversion location; that objective list is secondary, so treat it as a map, not a contract.

Regional availability is the field to check last, every time: non-EU markets (US, India, Brazil, Indonesia among them) went live through late 2025, while the EU, blocked through 2025 by the Irish DPC, began phasing in during 2026 per Meta's March 2026 DMA filing. Verify per country in Ads Manager before committing spend.

What Changed, Dated

The June 16, 2025 announcement bundled three Updates-tab products, and conflating them is the most common error in coverage: ads in Status (this page), Promoted Channels, and Channel Subscriptions. Only the first is a creative placement you design for.

Those dates are also a freshness test. A guide claiming Status ads launched in June 2024 is wrong by a full year; Social Media Today printed exactly that. The same test catches pages treating the EU as fully live, which is ahead of Meta's own filing, and any clean safe-zone number quoted with no source attached. The same test applied to Meta's other new placement is in our Threads ads spec sheet, where the stale number is 1:1.

WhatsApp Status Ads FAQ

Related Resources