WhatsApp launches voice and video calls on the Web

WhatsApp has launched voice and video calls on the Web, according to WABetaInfo. The core change is that users can place calls directly from the web client instead of opening the mobile app or the desktop app to reach a contact. That moves calling out of the installed clients and into the browser session people already use for chat.

On product mechanics, the feature is voice and video calls from the Web: the web client becomes a call endpoint, not only a messaging surface. Users start and run the call in the same browser session where they message, so the path no longer depends on a phone or desktop binary for the call itself. Availability is limited for some features; full parity with the mobile and desktop call stacks should not be assumed until those gaps close.

For engineers and builders, this is a client-surface expansion: calling is no longer gated on a native app install. Teams that ship web-first workflows, browser-based support tools, or multi-device messaging can treat WhatsApp Web as a place where audio and video sessions can start, not only text. That changes how you design handoffs when a user is already in the browser and does not want to switch to a phone or desktop app mid-task.

Competitive and market context is straightforward. Calling from web clients is a capability users already expect from other messaging and collaboration products that run in the browser. WhatsApp is closing that gap on its own web client rather than forcing users onto mobile or desktop for voice and video. Relative to products that already treat the browser as a full call surface, this is catch-up on a high-frequency feature, not a new category.

Practical takeaway: if your product, support flow, or internal tooling assumes WhatsApp calling only works on mobile or desktop, revisit that assumption for web sessions. Watch rollout scope next—WABetaInfo notes that some features are not fully available yet—so verify whether group calls, device linking rules, and media quality match what your users get on the native apps before you treat web calling as the default path.