Windows VPN split tunneling lets you choose which apps use a VPN connection and which connect through your regular network. The useful part is control: a browser can use the VPN while a banking app or local device stays on the normal route, for example. The exact behavior depends on the VPN client, Windows configuration, and how each app makes network requests. Before adding rules, confirm that your client supports app-based split tunneling and understand whether its setting means “include these apps” or “exclude these apps.”

Understand What Split Tunneling Changes

A VPN normally creates a network path through a VPN server. Depending on the client and its settings, it may send most or all internet traffic through that path. Split tunneling changes that arrangement by selecting traffic that should use the VPN and traffic that should bypass it. It does not make an app anonymous, change its account region, or determine whether a website will accept your connection.

There are two common ways to define the split. In an include list, only the apps you select use the VPN; other apps connect directly. In an exclude list, traffic uses the VPN by default except for the apps you exempt. The labels can vary between clients, so read the explanation beside the setting rather than assuming that “add app” always means the same thing. A mistaken interpretation can route the very app you meant to exclude through the VPN.

App-based rules are also different from domain or IP rules. An app rule identifies traffic by a Windows executable or application identity. A domain rule identifies a destination, while an IP route applies to a network address or range. A browser can contact many domains through several processes, and apps may share Windows networking components. That is why an app rule is convenient but not always a complete description of every request associated with a task.

  • ✅ Use an include list when only a small, clearly defined set of apps needs the VPN.
  • ✅ Use an exclude list when most apps should use the VPN and only specific apps need a direct route.
  • ❌ Do not assume that an app’s visible name is the same as the executable the client needs.

Check Windows Client Support Before Adding Rules

First inspect the VPN client you actually use. Look in settings for terms such as “split tunneling,” “app routing,” “bypass VPN,” or “route selected applications.” If there is no such option, do not assume that Windows has automatically applied app-specific rules. The client may support only a system-wide tunnel, domain rules, or a different form of traffic selection.

Check the client’s own help information for its supported Windows versions, rule type, and limitations. Some clients require administrator permission to change routes or install a network component. A work-managed computer may also block changes to network adapters or require approval. Do not disable endpoint protection, remove security software, or override a company policy to make a split rule work.

Consider how the client represents an app. It may ask you to browse to an executable file, select an installed application, or choose a package from a list. A desktop program may have a stable executable path, while a Microsoft Store app can use a package identity and may launch helper processes. If the client offers a built-in app picker, use it where possible. If you browse manually, verify that you selected the actual application executable rather than an updater, launcher, or unrelated process with a similar name.

Also note whether the client applies the rule to every connection from an app or only to traffic handled by a particular adapter or protocol. Browser extensions, background services, and helper processes may not share the same executable identity as the main window. If the result is inconsistent, this distinction can explain why one part of an app appears to follow the rule while another does not.

Bottom line: Confirm the client’s rule model and application identity before changing anything. A correct rule in the wrong mode, or attached to the wrong executable, can look like a VPN failure.

Add App Rules in a Controlled Order

Before editing rules, record the current VPN mode and the apps that are already allowed or excluded. If the client provides a configuration export or profile backup, save one according to its instructions. This gives you a way to restore the previous setup if a new rule interrupts access.

  1. Choose one test app. Start with an app whose network behavior you can check without disrupting work, payments, or account security.
  2. Decide which route it needs. Write down whether that app should use the VPN or connect directly. State the choice in plain language before selecting an include or exclude mode.
  3. Open the split-tunneling setting. In the VPN client, select the mode that matches your intended default: selected apps through the VPN, or selected apps bypassing it.
  4. Add the correct application. Use the client’s app list or browse to the application it identifies. Check the displayed name and path where available; avoid guessing based on a shortcut label.
  5. Apply the change as instructed. Some clients apply changes immediately; others require reconnecting to the VPN or restarting the app. Follow the client’s prompt rather than repeatedly toggling the setting.
  6. Test the app, then add the next rule. Change one variable at a time. If several rules are added at once, it becomes harder to identify which one caused a failure.

Keep a short rule log as you work. Note the app, its executable or package identity, the chosen route, and whether you had to restart the app or reconnect. This is particularly helpful if an application updates and moves to a new location, or if you later change from an include list to an exclude list. A remembered rule can remain in the client even after the application’s identity changes.

If you use a compatible third-party client such as Clash Verge or sing-box, distinguish app rules from the client’s general routing rules. These tools may offer policy groups, process matching, domain matching, or other routing controls, but their syntax and Windows support vary by client and version. Follow the documentation for the exact client build you installed. Do not paste a configuration written for a different client or assume that an app-level rule and a domain rule have identical effects.

Keep the VPN profile and subscription configuration private. A subscription link can contain access credentials, so do not post it in a public issue, screenshot, or troubleshooting forum. For a general overview of available service and connection options, see VPN40.

Test the VPN Route and the Direct Route

A rule is not verified just because it appears in the client’s list. Test the app while the VPN is connected, then compare the result with the VPN disconnected if doing so is safe and appropriate. Use a test page or service that reports the apparent public IP, and check the result from the specific app or browser affected by the rule. A separate browser can use a different route, so testing only in another application may not prove that the target app follows its rule.

For an app expected to use the VPN, confirm that it can reach its intended service and that its apparent network location is consistent with the selected route. For an app expected to connect directly, check whether it can reach a service that normally works on your current network. Avoid using a single website’s location label as the only test: IP location databases can be imprecise, and services may classify addresses differently.

Use the same network, app, and destination when comparing results. Close and reopen the app if the client requires a restart, and reconnect the VPN if its documentation says rule changes take effect on connection. Clear only the relevant app’s cached session or connection state when a test is clearly reusing an old connection; do not erase broad system settings as a first step.

Some apps use several network paths. A browser may resolve a name using Windows DNS, use a proxy setting, or connect through a helper process. A program can also keep an existing connection alive after a rule changes. If the app’s result and a system-wide IP check disagree, check the client’s route status and repeat the test after a clean app restart. The discrepancy does not automatically mean the rule is broken.

Pay attention to IPv4 and IPv6 behavior if your client offers separate controls or diagnostics. A VPN may handle one address family differently from another, depending on its configuration. Do not disable IPv6 or change Windows adapter settings blindly to force a particular test result. First consult the VPN client’s guidance and confirm which addresses and DNS requests are supposed to use the tunnel.

  • ✅ Test the selected app itself, not just another browser or a system-wide indicator.
  • ✅ Repeat the check after the reconnect or app restart required by the client.
  • ✅ Compare a VPN-routed app and a direct-route app separately.
  • ❌ Do not treat one location lookup as proof that every request follows the same path.

Troubleshoot Rules That Do Not Take Effect

If an app still uses the unexpected route, start with the simplest causes. Confirm that the VPN is connected, the split-tunneling mode is enabled, and the app appears in the correct list. Recheck whether the list includes apps that should use the VPN or excludes apps that should bypass it. A mode mismatch is easier to overlook than a complicated networking fault.

Check the app identity and path

Updates can replace an executable, create a new versioned folder, or change the process that makes network requests. A shortcut can also point to a launcher that starts a separate application process. Compare the current process or installed app identity with the entry in the VPN client. If the client supports package selection, use that rather than adding a guessed path. Remove only the obsolete rule after confirming what the client has stored.

Check existing connections and competing routes

An app may keep an established connection after a setting changes. Close the app fully, verify that it is no longer running in the background if the client requires this, then reopen it. If the VPN client asks for a reconnect, disconnect and reconnect using its controls. Avoid running multiple VPN or proxy clients at the same time while diagnosing: they may compete for the default route, DNS handling, or virtual network adapter, making results difficult to interpret.

Windows Firewall, security software, a corporate VPN, or managed network policies can also affect the outcome. If the problem occurs only on a work device, ask the administrator before modifying adapters, DNS, firewall rules, or device policies. Do not turn off protection to see whether routing changes; doing so can introduce a separate security risk without identifying the cause.

Check DNS, proxy, and browser behavior

DNS behavior can make a routing test confusing. An app might send its web traffic through one route while name lookups are handled according to a different client or system setting. Browser-level proxies, secure DNS features, or extensions can further change how requests are resolved or forwarded. Check the VPN client’s documentation for DNS behavior, then temporarily test with a simple, known configuration rather than changing several browser and Windows options at once.

If only one website or service fails, compare it with another destination in the same app. The site may block a connection, require a fresh sign-in, or be unavailable on the current network regardless of the app rule. If all apps fail after a routing change, restore the previous setting or disable the new rule and retest. This helps separate a faulty app rule from a general connection problem.

Bottom line: Troubleshoot in order: rule mode, app identity, connection restart, competing network clients, then DNS or security policy. Change one setting at a time so each test has a clear result.

Use App Rules Carefully: Frequently Asked Questions

Can I route only one browser tab through the VPN?

Usually, an app-based rule applies to the browser process, not an individual tab. To separate destinations or browsing sessions, you may need a client that supports domain or policy-based routing, or a separate browser profile if the client can distinguish its process. Check the client’s actual capabilities; a tab name is not normally a Windows executable identity.

Why does an app change route after an update?

An update can change the executable path, package identity, or helper process that sends network requests. The old rule may still exist but no longer match the process in use. Recheck the app identity in the VPN client and update the rule only after confirming which process is responsible.

Does a direct-route app still use the VPN?

If the rule successfully bypasses the VPN, that app’s traffic uses the available non-VPN network route. The VPN does not automatically protect or encrypt that traffic. The exact behavior also depends on the client’s failure handling and Windows network configuration, so review whether the client blocks direct traffic when the tunnel disconnects.

Can I run split tunneling with another VPN or proxy client?

It may be possible in some setups, but simultaneous clients can compete over routes, DNS, adapters, and firewall rules. Test one client at a time first. If you need both a corporate VPN and a personal routing tool, confirm compatibility with the relevant client documentation and your organization’s IT policy before combining them.