VPN split tunneling is a setting that routes only some of your internet traffic through the VPN tunnel while the rest goes out over your normal connection, decided by app, by destination, or by traffic type depending on the client. It answers the question "what goes through the tunnel and what doesn't" before you connect. The key boundary: split tunneling changes routing, not security per app — anything you exclude inherits whatever protection your home or mobile network already has, which is usually none on public Wi-Fi.

Defining Split Tunneling By the Three Rules Clients Actually Use

The mechanics matter more than the label, because the three routing modes behave very differently and one of them quietly leaks. Most desktop VPN clients built on OpenVPN or WireGuard support app-based split tunneling, where you tick which executables bypass the tunnel. A smaller group supports IP-based or subnet-based routing, where you enter destination ranges that skip the VPN — this is the mode corporate IT departments use to keep internal resources reachable while remote staff tunnel everything else. The third mode, inverse or "tunnel only these apps," routes a short allowlist through the VPN and sends everything else direct; it's less common in consumer clients but exists in several open-source ones.

The distinction that trips people up is direction. "Exclude these apps from the VPN" and "include only these apps in the VPN" sound like the same control and produce opposite results for every program you didn't think about. If you exclude your banking app, the bank sees your ISP's IP address; if you include only your banking app, every other program on the machine is exposed. Check which way your client words the toggle before you touch it.

Platform support is uneven and version-specific. On Windows, the routing is typically handled through the client's virtual adapter and its own driver, which is why some clients warn that split tunneling requires a TAP adapter install. On macOS, newer clients that use the Network Extension framework can enumerate installed applications directly, which is cleaner than the old approach of matching binary paths. On Android, the operating system exposes per-app VPN through VpnService.Builder.addAllowedApplication(), so any well-built Android client can offer per-app routing. iOS is the outlier: Apple's Network Extension personal VPN API does not offer general per-app split tunneling to third-party VPN apps, so iPhone users should not expect the same menu they see on a laptop.

One more structural point: split tunneling is a client-side decision enforced by the VPN app and the operating system's routing table, so it only governs traffic from that device. A router-level VPN with split tunneling configured at the router governs every device behind it but exposes the same weaknesses — anything routed around the tunnel leaves from your ISP address. The rule lives where the routing table lives.

How the Routing Decision Is Made, Hop By Hop

When you connect with split tunneling on, the VPN client adds routes to the operating system's routing table. Destination addresses matching the "through the tunnel" list get a next-hop of the VPN's virtual adapter; everything else keeps the default gateway your DHCP server handed out. The operating system consults the table per packet, longest-prefix match wins, and that's the whole decision. No per-app firewall, no content inspection — just routing.

DNS is where the design gets fragile. If your excluded apps resolve names through a DNS server the VPN pushed, those queries travel the tunnel even though the app's data doesn't, which can produce geographically odd results or break local discovery (think printers and smart TVs). Some clients handle this by sending DNS for excluded apps to the local resolver; others don't, and you get the classic symptom where a streaming service thinks you're in another country because the DNS answer came from the VPN exit. Look for a client setting like "use local DNS for excluded apps" or set it manually if the option exists.

IPv6 is the second leak surface. A client can route IPv4 through the tunnel and leave IPv6 untouched, so an excluded-capable stack on a dual-stack network may reach a site over IPv6 outside the tunnel while the app's IPv4 traffic uses it. Reputable clients either route both families or block IPv6 entirely while connected — but "reputable" is a claim you can verify yourself by connecting and checking an IP-leak test site that reports both v4 and v6.

Two failure modes are worth knowing before you configure anything. First, some games and anti-cheat systems treat a virtual adapter as suspicious, so a title that runs fine on a full tunnel may refuse to launch with split tunneling because the anti-cheat detects the adapter's presence. Second, corporate networks often push a full-tunnel policy through the VPN client's management profile, and split tunneling will be greyed out or silently overridden — if the toggle is disabled and you didn't disable it, that's why. Neither is a bug in the concept; both are the environment asserting control over routing.

A Worked Example: Bandwidth, Latency, and What Split Tunneling Saves

Take a home connection on a 500 Mbps plan with a VPN that sustains 300 Mbps through its tunnel on a nearby server. Route everything through the VPN and large downloads crawl at 300 Mbps; exclude a download client and those transfers get the full 500 Mbps while your browsing stays tunneled. That's the everyday case for split tunneling, and the number to remember is the difference between tunnel throughput and raw throughput — for many VPN protocols the tunnel is the bottleneck, and the gap widens with distance to the server.

Latency tells a similar story. If your VPN server adds 40 ms of round-trip time versus a direct connection, an online game played through the tunnel feels that 40 ms every action; exclude the game and it plays on the direct path, but every other app keeps the tunnel's privacy. Video calls are the awkward middle: they tolerate latency less than downloads but leak your real IP to the call provider when excluded, and some corporate meeting tools will show your home location to participants.

Privacy cost is the part people skip. Every excluded app sees your ISP-assigned IP address and whatever the destination can infer from it — approximate city, ISP name, and the fact that this address also browses other sites. If you excluded a browser profile, every site in it can correlate you; if you excluded only a game launcher, the exposure is narrower but the launcher's telemetry still leaves from your home address. Split tunneling trades exposure surface for speed and compatibility, and the trade is per app, so make it deliberately.

Security on hostile networks is non-negotiable in the other direction: on hotel, airport, or café Wi-Fi, anything outside the tunnel sits on the same untrusted segment as any other guest device. A practical rule — carry two configurations, one full-tunnel for public networks and one split for home — costs a few seconds of reconnecting and removes the worst case. If your client supports profiles or shortcuts, save both.

When It's the Right Call: Work, Games, and Local Devices

Remote work is split tunneling's strongest legitimate use. A company VPN often routes internal tools through the tunnel while general browsing goes direct, which keeps SaaS video calls off the corporate gateway and preserves bandwidth for everyone else. Many organizations pair this with a zero-trust access product that authenticates per application rather than per network, so "on the VPN" stops being the boundary and identity becomes the boundary — a meaningful architectural difference from the older model where being tunneled granted broad internal reach.

Gaming is the consumer case. Matchmaking, anti-cheat, and latency all argue for sending game traffic direct, while everything else stays tunneled. The catch is regional pricing and storefront region locks: if a storefront sees your tunnel exit instead of your real region, purchases and libraries can behave unexpectedly, and some publishers treat VPN use as a terms-of-service issue. Read the terms rather than the forum folklore.

Local network access is the third. Printers, NAS shares, smart home hubs, and screen-mirroring all rely on mDNS, SSDP, or SMB broadcasts that generally do not traverse a VPN tunnel, and full-tunnel clients sometimes break local discovery outright. With split tunneling configured to keep the local subnet off the VPN, discovery keeps working. If your client offers "allow local network access" or a "bypass LAN" checkbox, that's this feature under a friendlier name.

Choose split tunneling when tunnel throughput bottlenecks your work, when a specific app misfires under the VPN, or when local devices must stay reachable. Skip it when the device joins untrusted networks regularly and the user won't reliably switch profiles, and skip it on managed corporate devices where policy overrides the toggle anyway. The honest drawback for the recommended home setup — full tunnel by default, split profile for gaming and LAN — is that profile switching is a manual step people forget, and a forgotten switch on public Wi-Fi is exactly the failure the setup was designed to prevent.

Configuring It in Three Clients: WireGuard, OpenVPN, and a Consumer VPN App

The exact menu names differ, but the shape of the task is consistent across clients. What follows uses the official implementations and is written for the versions current as of late 2026; confirm menu labels on the maker's site if yours differs.

WireGuard (official Windows client). WireGuard's official client does not offer per-app split tunneling in its GUI. Tunneling by app requires the community "WireSock" companion or a comparable third-party front end, which is a real limitation to know before choosing WireGuard for this purpose.

OpenVPN (OpenVPN Connect or the open-source GUI). In OpenVPN GUI on Windows, open the connection's .ovpn file in a text editor and add route-nopull to stop the server's pushed routes, then add only the route lines you want tunneled. On macOS and Linux with tun-based setups, the equivalent uses route directives in a script. This is IP-based split tunneling, not app-based.

A mainstream consumer VPN app (the pattern to look for). Open Settings, find the split tunneling or "VPN bypass" section, and switch the mode.

1: Connect first, then open the split tunneling setting — some clients hide it while disconnected. 2: Choose the mode (exclude listed apps, or include only listed apps) and note which phrasing your client uses. 3: Add applications by browsing to the executable or picking from the installed list. 4: Save, disconnect, reconnect — the routing table is rebuilt on connect, so the change takes effect only after a fresh session. 5: Verify with an IP-checker in an excluded app's browser versus an included one; the two should report different addresses. 6: On Windows, if the app list is empty or the toggle won't stay on, install or repair the client's TAP/virtual adapter, then repeat from step 4.

If excluded apps still show the VPN address after reconnecting, the usual culprits are a client update that reset the list, a DNS leak as described earlier, or an IPv6 path the client didn't cover. If included apps lose connectivity, check whether the VPN server pushes routes your client is now ignoring — route-nopull in OpenVPN discards all pushed routes, so you may need to re-add the one you actually want.

Five Mistakes That Quietly Undo the Point of Split Tunneling

Excluding the browser you use for everything. It's the most common configuration error: people exclude "the browser" to fix a streaming site and then shop, bank, and read email through it from their home IP. Exclude a dedicated secondary browser profile or a specific site's helper app instead, so the exposure stays scoped.

Forgetting DNS. A tunneled DNS resolver answering for an excluded app can send queries to the VPN provider even though the app's data bypasses it, which mixes your identities from the provider's perspective. Check for a local-DNS option for excluded apps and test with a DNS-leak test page.

Ignoring IPv6. A client that tunnels IPv4 only leaves a whole address family outside the tunnel on dual-stack networks. Prefer clients that handle both or block v6 while connected, and verify rather than assume.

Expecting it to fix a site that blocks VPNs. Split tunneling changes which path traffic takes for that device; it doesn't change what the site sees if you left the app included. Likewise, a service that blocks the VPN exit address will keep blocking it while the app is tunneled.

Treating it as a privacy control for other devices. Split tunneling on one laptop says nothing about the phone, the tablet, or the smart TV. Router-level configurations cover the household but reintroduce the same routing mistake for everyone at once.

Split Tunneling vs. Full Tunnel vs. Inverse Mode: Choosing Under Two Conditions

Full tunnel sends 100% of traffic through the VPN: maximum consistency, minimum thinking, tunnel throughput as the ceiling for everything. Split tunneling sends selected traffic around it: speed and compatibility for the excluded set, exposure for that same set. Inverse mode tunnels only a list: useful when you want a specific app protected and don't care about the rest, but dangerous if the rest includes anything sensitive.

Dimension Full tunnel Split tunneling (exclude list) Inverse (include list)
Share of traffic through VPN All of it All except the listed apps/IPs Only the listed apps/IPs
Default protection level Highest available Reduces with every excluded app Reduces with every unlisted app
Typical throughput ceiling VPN tunnel rate Mixed: tunnel rate + raw rate Mostly raw rate
Local network discovery Often broken Preserved when LAN bypassed Usually preserved
Best fit Public Wi-Fi, managed corporate use Gaming, work VPN split, LAN devices A single app needing the tunnel
Failure habit Slow downloads, blocked local services Forgotten exclusions on hostile Wi-Fi Forgotten inclusions leak silently

Pick full tunnel as the default on any device that leaves the house. Add a split profile for the cases where it demonstrably earns its keep — a game that won't run, a printer that won't appear, a work network whose gateway saturates. Reserve inverse mode for narrow, well-understood tasks, because its failure mode is silent. The one real drawback of the default-plus-profile pattern is that it depends on human discipline at the moment of joining a network, and humans are worst at discipline exactly when the stakes are highest.

Platform and Version Quirks That Change the Answer

Windows clients vary in whether they match apps by executable path or by process name, and a browser or launcher that spawns child processes can slip past an app entry that matched the parent only. If an excluded app seems partially tunneled, check the client's documentation for how child processes are handled before assuming a bug.

Apple platforms deserve their own caveat. Since the Personal VPN framework on iOS does not expose general per-app split tunneling to third-party apps, iPhone users should expect either full-tunnel behavior or, for some enterprise/Managed settings, per-app rules delivered through supervised-device management rather than a user-facing list. A consumer app that advertises per-app routing on iOS is worth verifying on the maker's site before buying.

macOS sits between: clients using the Network Extension framework can offer per-app routing, older clients using kernel extensions cannot, and Apple has been deprecating the older path. A macOS client that offers the feature on one macOS version and not another is plausible; check the release notes.

Android's per-app VPN is a first-class OS feature, but only one VPN can be active at a time (excluding the OS's own "always-on" behavior), so a corporate VPN profile can displace a personal one and the split configuration travels with the profile that's active.

FAQ

Does split tunneling make a VPN less secure?

It makes the device's traffic less uniformly protected, at least for excluded apps. The size of the gap depends on which apps you exclude and which network you're on: on home broadband the excluded traffic sees your ISP's sniffing and your IP's visibility, while on public Wi-Fi it sits fully exposed on a shared segment. Many clients offer to force full tunnel automatically on untrusted networks, which is the least-effort fix.

What happens if I exclude my browser — can the VPN provider still see my browsing?

If the browser is excluded, its traffic never reaches the VPN server, so the provider can't see it. Your ISP can. A secondary browser profile for the excluded use case keeps this deliberate rather than accidental, and means your main browsing identity stays tunneled.

Do I need split tunneling for corporate apps and personal apps on the same laptop?

An app-level exclusion list is exactly the tool for that when company policy permits it. Many corporate VPN profiles lock the toggle, in which case the answer is a separate device or a virtual machine for personal use. Check your employer's acceptable-use policy before adding exclusions.

Why does my game refuse to launch with split tunneling on?

Anti-cheat systems sometimes treat the presence of a virtual network adapter or the mixed routing path as a tampering indicator. Common workarounds are launching the game before connecting the VPN with the game excluded, or using a client that can exclude by process rather than by adapter. If neither works, the game's own support pages are the authority.

Is split tunneling the same as a "bypass" feature?

Generally yes in consumer apps — "bypass VPN," "skip the VPN for these apps," and "exclusion list" describe the same exclude-list behavior. The inverse mode (only these apps tunneled) is less common and usually labeled explicitly, but verify which one a given app offers rather than inferring from the name.

Can I use split tunneling on a router?

Some router firmwares and VPN-capable routers support it at the device level, letting you choose which household devices route through the VPN. That covers phones and TVs, but the routing choice applies to everyone behind the router, and the excluded devices inherit the same exposure profile.

How much speed does split tunneling actually recover?

It recovers the difference between your raw connection and the VPN tunnel's throughput for the excluded apps — nothing more. If your plan delivers 500 Mbps and the tunnel sustains 300 Mbps, excluded downloads get up to 500 Mbps while included traffic stays at 300 Mbps, and the benefit scales with how much of your traffic you exclude.

Which VPN protocols support app-based split tunneling?

Support lives in the client, not the protocol: the underlying OpenVPN or WireGuard tunnel can carry either behavior, and the client decides how to populate the routing table. That's why two apps using the same protocol can differ in whether per-app routing exists at all.