↔P2Priv 8 entries · updated 2026-11-01

Which Mullvad multihop mode should you use?

Compare Mullvad’s three multihop modes, check app availability, and understand what an extra VPN hop changes for peer-to-peer traffic.

P2Priv Editorial Team · 4 min read

For peer-to-peer traffic carried through Mullvad, the other peer sees the VPN’s exit IP address, whether you use one VPN server or two. Multihop changes the route before that exit; it does not make your connection invisible to the peer. Mullvad describes its two-hop route as a tunnel within a tunnel, passing through an entry server and then an exit server before reaching the destination. Mullvad’s multihop explanation

Choose When needed for automatic feature compatibility, Always if you deliberately want two servers, or Never if you want a single-server route and accept the resulting feature and location limits.

What the three modes do

Mode Connection path Best fit
When needed One server unless an enabled feature is unavailable at your selected location. The app then adds a nearby compatible server and exits through your selected location. You want your chosen features to work without managing an entry server.
Always Two different servers on every connection. You can choose the entry location or use Automatic. You specifically want an extra hop, rather than only adding one for compatibility.
Never One server. The selected location must support every active setting for a connection to succeed. You prefer a simpler route and can choose a compatible location.

These are the behaviors in Mullvad’s Multihop modes announcement. Never does not mean “disable the VPN”—it disables the additional hop.

For example, if you enable DAITA and choose an exit location without DAITA support, When needed adds a compatible server before your chosen exit. Never cannot add another server to resolve that mismatch: you must choose a compatible location.

Automatic is an entry-location choice, not a fourth mode. With Always, it lets Mullvad choose a nearby location supporting your enabled features. It does not promise entry and exit servers in different countries. If geographic separation matters to your threat model, choose the entry yourself. Mode and location behavior

Check your app version before looking for the modes

As of October 30, 2026, Mullvad’s announcement identifies iOS 2026.4 as available and targets desktop 2026.6 later in the year; that desktop version is a rollout target, not confirmation of availability.

Android’s release notes confirm that 2026.9 added the redesigned multihop controls and When needed option. Mullvad advises against using that version because QUIC can leave the tunnel stuck connecting or disconnecting. 2026.10 fixed that bug; use a current stable release rather than installing 2026.9 just to obtain the modes. The notes also flag a separate first-connection-attempt failure involving features such as DAITA or quantum-resistant tunnels, so a connection failure is not necessarily a mode or location mismatch.

Older apps may still show a multihop toggle rather than these three modes. When upgrading, review the migration notice: Mullvad maps existing settings to the closest equivalent where possible. With filters and the old DAITA Direct only setting off, its examples include multihop-on becoming Always, and multihop-off with DAITA-off becoming When needed. Direct only is replaced by the modes. Migration details

What an extra hop changes for P2P privacy

The benefit is mainly about observation along the VPN route, not what your final peer can learn from the application protocol. Mullvad says multihop can make incoming/outgoing traffic correlation harder across separate locations and can add protection if one server is compromised. Both servers remain part of Mullvad’s service: this is not a two-provider arrangement or a guarantee against traffic analysis. Mullvad’s threat-model explanation

It also does not remove protocol identifiers. In BitTorrent, for example, the peer handshake includes the content’s info-hash and a peer ID. Adding a VPN hop does not change those fields. BitTorrent protocol specification For the broader boundary, see what other peers can see.

Performance is route-dependent. Mullvad says multihop generally slows connections over distance, although a different route can sometimes improve inefficient ISP peering. Compare the same exit location with and without the extra hop rather than assuming a fixed speed penalty. Performance explanation

Verify the application path, not just the mode

After changing modes:

  1. Check the entry and exit shown in the app. When needed may legitimately show only one server when your chosen location supports all active features.
  2. Review split-tunneling exclusions. Multihop does not bring excluded apps back into the tunnel. Where those apps can connect, they use your regular connection and your own IP. On Android, Mullvad says Block connections without VPN prevents excluded apps from connecting. Mullvad also documents a Windows-specific issue: launching qBittorrent through a magnet link in an excluded Chrome browser can exclude qBittorrent too. Close and launch the client independently before checking its route. Split-tunneling guidance
  3. Check browser and P2P traffic separately. Mullvad’s connection check is useful for browser exposure, but it does not establish another application’s route. For lawful sharing, inspect the remote address recorded by a peer you control and repeat after reconnecting or changing settings. That tests the observed peer connection—not every tracker, DHT or other application traffic path.

If your aim is simply to keep your access-network IP out of peer connections, first ensure that the application actually uses the VPN. Always multihop cannot repair traffic that never enters the tunnel.