Audio and video calls on WhatsApp Web are no longer part of the beta program. Meta has confirmed the global rollout of this feature, integrated into the multi-device architecture that allows linking up to four companion devices without keeping the phone constantly connected. For Linux users or those who refuse to install the desktop client, the browser becomes a full-fledged calling station.
Here, we detail the technical points that consumer guides often overlook: actual browser compatibility, network constraints, limitations for business accounts, and optimal audio configuration.
Related reading : Tips and advice to enhance your beauty daily with suitable care
Browser Compatibility and Audio Codec on WhatsApp Web
WhatsApp Web supports calls on Chrome, Edge, Safari, and Firefox, on Windows, Linux, and macOS. This official list masks concrete disparities.
The transport relies on WebRTC. Each browser implements its own audio and video codecs. Chrome and Edge share the Chromium engine and handle Opus with smooth adaptive bitrate. Firefox also uses Opus, but its implementation of ICE (Interactive Connectivity Establishment) negotiation can introduce a slightly longer setup time on some restrictive networks.
Further reading : How to Enhance Your Online Security: Discover Cybersecurity with CGI Network
Safari, since macOS Ventura, manages WebRTC stably, but minor updates sometimes break support for USB audio devices. We recommend checking the microphone’s functionality after each system update. On Linux, Fedora Workstation with Firefox is a tested and functional combination, as confirmed by feedback from beta program users.
A often overlooked point: some older versions of browsers are not supported. WhatsApp does not specify a minimum version number, making diagnosis difficult in case of silent failure. If the call icon does not appear, the first action remains to update the browser.
To delve deeper into configuring calls from the browser, you can explore hebdolinux.org for your specific needs, especially under Linux distributions.
WhatsApp Web Calls and Multi-Device Architecture: What Changes on the Network Side
The old architecture of WhatsApp Web worked by mirroring the phone. Every message, every call passed through the smartphone. The multi-device architecture breaks this dependency: the browser establishes its own end-to-end encrypted session with the WhatsApp server.
Direct consequence on calls: the quality depends exclusively on the computer’s internet connection, not that of the phone. A smartphone in airplane mode does not prevent receiving a call on WhatsApp Web, provided that the device was linked in the last few days (the session expires after a prolonged inactivity period).
Network Constraints to Anticipate
- Corporate networks that block the UDP ports used by STUN/TURN prevent call establishment. WebRTC traffic requires at least the opening of outgoing UDP ports beyond simple HTTPS.
- A poorly configured VPN adds noticeable latency. Double encryption (VPN + WhatsApp encryption) increases the CPU load on older machines.
- Application firewalls of the HTTPS proxy type (common in enterprises) can intercept WebRTC negotiation and cause a call failure without an explicit error message.
On a standard home network, these constraints do not arise. In a professional context, they explain the majority of reported call failures.
WhatsApp Business Accounts and API: A Limitation to Know
Calls from the browser are not available for numbers connected via the WhatsApp Business API (Cloud API or On-premise). Third-party platforms like respond.io, Twilio, or MessageBird only support messaging. Calls remain limited to the standard mobile and desktop applications.
This restriction affects businesses using WhatsApp as an automated customer support channel. An agent connected via the Cloud API platform cannot initiate a voice call from their web interface. To bypass this limit, one must use a standard WhatsApp number (non-API) linked to WhatsApp Web.
Meta has not announced a timeline for integrating calls into the Business API. Companies planning a vocal support deployment via WhatsApp should take this into account.
Optimal Audio Configuration for WhatsApp Web Calls
WhatsApp recommends using a headset. This advice is not cosmetic: an external microphone and speaker can cause echo, as confirmed by the official FAQ. The echo cancellation (AEC) processing built into browsers works better with a combined headset-microphone than with separate devices.
Checkpoints Before a Call
- Check that the browser has permission to access the microphone (site settings in Chrome/Firefox/Edge). A previous denial silently blocks calls.
- On Linux, PulseAudio or PipeWire must correctly route the audio stream to the browser. The command pavucontrol allows checking streams in real-time.
- On macOS, microphone permissions are managed at the system level (System Preferences, then Privacy). Safari requires a separate permission from that granted to Chrome.
A quick test: make a call to a trusted contact and ask for feedback on the quality. Echo or latency issues can be detected within seconds.
WhatsApp Web calls now meet the needs of the majority of desktop users, provided they master browser compatibility, network prerequisites, and limitations related to business accounts. The most structuring restriction remains the lack of support for calls via the Business API, a technical choice by Meta that directs businesses toward separate telephony solutions for vocal support.