WhatsApp calls on a Mac in the UAE, without putting your bank on a VPN

WhatsApp voice and video calls are restricted in the UAE, and the usual fix is a VPN. The usual problem with that fix is that a VPN moves your whole Mac abroad: your bank's app starts asking security questions, local services stop recognising you, and everything gets slower for the sake of one app.

VPNonly does it the other way round. Your Mac stays exactly where it is, and only WhatsApp goes through the VPN. This page is what that looks like, and what we actually measured.

What you need

• A Mac with Apple silicon.
• A VPN account that speaks WireGuard. NordVPN works with just an access token; Mullvad, Proton, IVPN, AirVPN or your own server work with the config file they give you. Details per provider.
• WhatsApp for Mac, the native app from the Mac App Store or whatsapp.com, not the web version in a browser tab.
• VPNonly 1.9.17 or later. Earlier versions crash WhatsApp the moment a call asks for the microphone; that's fixed in 1.9.17.

Setting it up

1. Install VPNonly and connect your provider. Pick an exit country where WhatsApp calls work normally.
2. Search for WhatsApp in the list and flip its switch on. WhatsApp closes and reopens once. That's macOS, not a bug: an app's network identity is fixed the moment it opens.
3. The first time you make a call, macOS asks whether WhatsApp can use the microphone. Allow it. That's the normal prompt, and it names WhatsApp, not VPNonly.
4. Make a call.

Everything else on the Mac, including Safari, your bank, and any other app, keeps using your normal connection. Nothing else changes.

What we measured

Claims about VPN routing are easy to make, so here's the test rather than the claim. macOS can label every packet with the process that sent it, so we watched which interface WhatsApp's packets actually used on a Mac running VPNonly 1.9.17 with a Mullvad tunnel, on 6 September 2026:

Activity	Through the tunnel	On the normal connection
Sending messages	632 packets	0
Placing a call (ringing and setup)	172 packets	0
A connected voice call	618 packets	19, not reproduced in a repeat capture

The call media went through the tunnel; the relay it connected to was Meta's STUN/TURN server at port 3478, seen inside the tunnel interface. The 19 packets on the normal connection during the first call appeared once and didn't recur when we watched that interface alone for the rest of the call. We're saying so rather than leaving them out.

What it can't do

• FaceTime. Its audio and video run in a macOS system process, not inside the FaceTime app, so no per-app tool can route it. Same reason Safari can't be routed. WhatsApp does its own networking, which is why it works.
• WhatsApp's notification and Siri extensions are launched by macOS outside the app, so they use your normal connection. They handle notification previews and Siri shortcuts, not calls or messages.
• If the tunnel drops, the call drops. WhatsApp shows "calling…" until you redial. VPNonly reconnects the tunnel on its own after a network change, but a call in progress doesn't survive it. That's true of any VPN.

On the rules

VoIP restrictions in the UAE are set by the telecoms regulator, and some calling apps are licensed to work without a VPN. This page describes what the software does; whether and how you use it is your call, so know the rules where you are.

Why this works when the VPN's own app doesn't

Most VPN apps for Mac are all or nothing. NordVPN has no split tunnelling on macOS at all. Proton and Mullvad have it, but only as "exclude": your whole Mac joins the VPN and you pick apps to leave out, which is the opposite of what you want here. VPNonly starts from nothing on the VPN and adds one app. The comparison, provider by provider.

The part of VPNonly that needs admin access is open source, so you can read what it does before trusting it with your firewall.