WhatsApp launches voice and video calls on the Web
WhatsApp is rolling out voice and video calling from its web client, according to WABetaInfo. The core change is that users can place calls directly in the…
By Dillip Chowdary • Aug 04, 2026 • Source: WABetaInfo
WhatsApp is rolling out voice and video calling from its web client, according to WABetaInfo. The core change is that users can place calls directly in the browser instead of switching to the mobile app or the desktop app to reach contacts.
On the product side, the web client becomes a full call surface for both voice and video. Call placement no longer depends on having the phone or desktop app in the loop for that step. WABetaInfo frames this as a major upgrade to how WhatsApp handles calls across clients, with availability still limited for some related features rather than a single all-or-nothing flip for every capability.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
For engineers and builders, this matters because browser-based calling is now a first-class path in a messaging product that many teams already treat as infrastructure for support, ops, and customer contact. If users can start and run voice or video from the web alone, product and platform work around “must open mobile or desktop to call” becomes obsolete for that flow. It also raises the bar for any web product that still treats real-time media as mobile-only.
In market terms, WhatsApp is closing a gap between its web experience and the mobile and desktop apps that already supported calling. Competitors and adjacent tools that ship strong web call experiences force the same expectation: messaging on the web should not be chat-only if the native apps already do voice and video. This move aligns WhatsApp Web more closely with that multi-client standard.
Watch how quickly full voice and video call parity lands for all web users and which related features remain gated. Teams that integrate WhatsApp into support or field workflows should retest browser-only call paths and update any docs or tooling that still assume mobile or desktop is required to place a call.
Advertisement