Android VPN split tunneling lets you decide which apps send traffic through a VPN and which use your regular internet connection. It can be useful when a work app needs a VPN while a local service works better on your normal connection, or when you want to route only selected apps through a particular exit. The key is to understand the rule you set: an app list can mean “VPN only these apps” or “VPN everything except these apps.” Those choices produce opposite results.
This guide explains how app-based split tunneling works, how to configure and test it, and what to check when an app cannot connect. Menu names differ between Android versions and VPN clients, so use the labels in your installed app rather than expecting every screen to match these descriptions exactly.
Understand app-based split tunneling
When an Android VPN connects, the client creates a virtual network interface and asks Android to route network traffic through it. With app-based split tunneling, the VPN client applies a routing rule to apps rather than asking you to select individual websites. Depending on the client, you may be able to include selected apps in the VPN or exclude selected apps from it.
In an include-only mode, apps on the selected list use the VPN and other apps normally use the device’s regular connection. In an exclude mode, apps on the selected list bypass the VPN and other apps use it. Read the mode label and the explanatory text carefully before adding apps. A screen titled “Bypass selected apps,” for example, has different behavior from one titled “Route selected apps through VPN.” The same app names can appear in both lists, but the outcome is reversed.
This rule applies to app traffic, not to a promise that every request from an app will follow one predictable path. An app may use background services, external browsers, system components, or a separate work profile. The browser opened from an app may be a different app with its own routing rule. If a service is made up of several apps, test each one you actually use rather than assuming that selecting one covers them all.
App-based routing also differs from domain-based or URL-based rules. Selecting a browser usually routes its network traffic according to the browser’s app identity; it does not necessarily send only one website through the VPN. If you need different routes for different domains, look for a client that explicitly supports domain or rule-based routing, and check what its Android implementation offers. A basic per-app list cannot express every kind of routing policy.
- ✅ Use an include list when only a small set of apps should use the VPN.
- ✅ Use an exclude list when most apps should use the VPN and only a few need a direct connection.
- ❌ Don’t assume “selected apps” means the same thing in every client; check whether the list includes or bypasses them.
- ❌ Don’t treat a VPN connection indicator as proof that a particular app is using the intended route.
Android’s VPN framework generally gives a VPN configuration an allowed-app list or a disallowed-app list. A client may present those choices as simple switches or as a selection mode. If you need both types of rule at once, check whether the client supports the combination; do not assume that separate lists are being merged. Another client may offer a more flexible rules engine, but it still needs to explain how its Android traffic routing works.
Choose the mode that fits your apps
Start with the outcome you want, not with the app list. Write down which apps should use the VPN and which need a direct connection, then choose the mode that makes that outcome easiest to verify. If only one or two apps need the VPN, an include-only list is often simpler to audit. If nearly everything should use the VPN, an exclude list may involve fewer selections. The better option is the one that leaves fewer opportunities for an accidental exception.
Include selected apps
In include-only mode, the apps you select are routed into the VPN tunnel, while apps outside the list usually remain on the regular connection. This can help when a specific browser, messaging app, or work tool needs a VPN but other apps should keep using the local network. It also means that adding a new app later does not automatically put it in the VPN. Revisit the list whenever you install an app that should follow the same rule.
Remember that the selected app’s traffic may include more than the foreground action. Background refreshes, notifications, sign-in requests, and media downloads can also originate from that app. Conversely, a button inside an app may open a system browser or another application. If the new app is not included, its follow-up request may take a different route from the app that launched it.
Exclude selected apps
In exclude mode, selected apps bypass the VPN and the remaining apps use it. This can be convenient when most traffic should use the tunnel but a local banking, casting, printing, or network-management app needs access to a local service. Whether a particular app actually requires a direct route depends on the service and the network; test it instead of excluding it pre-emptively.
Exclusions are meaningful privacy and routing choices. An excluded app connects through the network available to the device rather than through the VPN, so the VPN does not provide its exit location or tunnel protection for that app’s traffic. If you exclude a browser, for example, browsing in that app will not follow the VPN route. Keep the exception list short, name each exception for a reason, and remove entries that are no longer needed.
For a service that relies on local network discovery, first check whether the VPN client has a specific local-network option. Adding an entire app to a bypass list can solve one local-access problem while also routing that app’s unrelated internet traffic outside the VPN. Prefer the narrowest supported rule, and confirm how the client treats local addresses before changing several settings at once.
Set up app-based routing on Android
The following workflow uses generic labels because Android VPN clients organize split tunneling differently. First import your configuration or subscription into the client you intend to use, connect successfully with the ordinary VPN settings, and confirm that the client can reach a server. Establishing a working baseline makes it easier to tell whether a later failure comes from the app-routing rule or from the connection itself.
- Open the active VPN profile. In the VPN client, select the profile or connection you normally use and find a setting such as “Split tunneling,” “Per-app proxy,” “App routing,” or “Apps.” If the setting is absent, check the client’s documentation or current account instructions; Android itself does not provide the same app-selection controls in every VPN app.
- Choose include or exclude behavior. Read the description shown by the client. Identify whether checked apps will use the VPN or bypass it. If the wording is unclear, do not build a long list yet. Select one non-sensitive test app and verify the result before applying the rule to daily-use apps.
- Select apps by their displayed names. Android may show installed apps, system apps, or apps within a profile. Check the app icon and name carefully, especially if you have a work profile, a cloned app, or more than one browser. A personal copy and a work-profile copy can be treated as separate app instances.
- Save the rule and reconnect if requested. Some clients apply changes immediately; others require you to disconnect and reconnect. Follow the client’s prompt. If Android asks for permission to establish a VPN connection, make sure the request comes from the client you chose. Android generally allows one active VPN service at a time, so another VPN app may need to be disconnected first.
- Test both sides of the rule. Open an app meant to use the VPN and check its route using a reputable IP-check service or an app-specific connection test. Then test an app meant to bypass the VPN, if you have one. A page loading successfully proves connectivity, not which route it used; compare the observed network location with the intended behavior.
- Record the working configuration. Note the routing mode, selected apps, VPN profile, and any Android system settings that affect the result. This makes it easier to restore the setup after an app update, profile change, or client reinstall. Avoid changing the protocol, server, DNS, and app list simultaneously, because that makes a failure harder to diagnose.
For account setup, subscription access, and supported client options, the LeleVPN site is the starting point for the service’s platform information. A subscription import and an Android app-routing rule are separate tasks: the subscription supplies connection settings, while split tunneling decides which apps use the connection. Complete and verify them separately.
Keep your first test narrow. For example, route one browser through the VPN and leave a second test app outside it, then confirm the observed behavior for each. Once the rule works, add other apps in small groups and test again. This is more reliable than selecting many apps at once and trying to infer which selection caused an unexpected result.
Verify the route and check Android settings
Use an app-level check whenever possible. Open the selected app and visit an IP-check page or a service that reports the connection location. Repeat the check in an app that should bypass the VPN, if your configuration includes one. The result should match the routing policy you chose, but interpret it carefully: content delivery networks, account region settings, cached pages, and app-specific network behavior can affect what a service displays.
Do not rely only on the VPN client’s connected label. It generally confirms that the tunnel is established, not that every app is routed through it. Likewise, a successful page load does not establish whether the page used the VPN or the regular connection. Test the actual app and, if possible, use a separate network-information check from within that app’s traffic context.
Android system-level VPN options can change the outcome. “Always-on VPN” may automatically reconnect a selected VPN service. An option that blocks connections without a VPN can prevent excluded apps from reaching the internet, depending on Android and the client’s configuration. If an app that should bypass the tunnel stops working as soon as the VPN connects, inspect these system settings before assuming the split-tunneling list is broken. The setting may be unsuitable for a setup that intentionally sends some apps outside the VPN.
Private DNS is another setting worth checking when name resolution fails. A custom DNS provider, a client’s DNS configuration, and an app’s own encrypted DNS feature may interact differently. If an app connects by IP address but cannot resolve site names, change one DNS-related setting at a time and retest. Do not disable protections permanently just to make one test pass; first identify which resolver the app is using and whether the issue occurs only while the VPN is active.
Profiles matter too. Android work profiles and app-cloning features can create separate instances of the same application. A rule for the personal app may not cover its work-profile counterpart. Some system services may also make requests on behalf of an app. If only a sign-in flow or an external link behaves differently, check which app actually opened that screen and whether it belongs to the same profile.
Finally, distinguish routing from access policy. A VPN can provide a different network path, but it cannot guarantee that a site or app will accept a connection from every exit location. Services may impose their own region, account, or security checks. If the route is correct but access is still denied, verify the service’s requirements and test another permitted connection path rather than repeatedly toggling the app list.
Troubleshoot common split-tunneling problems
If an app cannot connect after you enable split tunneling, return to a simple baseline. Temporarily turn off the per-app rule, reconnect the VPN, and check whether the app works. If it still fails, the cause may be the VPN connection, the app, DNS, or the underlying network rather than the routing list. If it works with the rule disabled, re-enable the rule and test one selection at a time.
- The wrong apps use the VPN: Check whether the list is in include or exclude mode. Confirm the selected profile is the one currently connected, then reconnect if the client requires it. Also check for a second app instance in a work profile or cloned-app environment.
- An excluded app has no internet access: Review Android’s always-on and block-without-VPN options. Check whether the client has a kill-switch setting that blocks direct traffic. An exclusion and a device-wide block policy can conflict because one asks for a direct connection while the other may disallow traffic outside the tunnel.
- A selected app opens, but some actions fail: The app may hand off part of the task to a browser, system component, or another app. Identify which app performs the failing step and apply the routing rule to that app only if appropriate. Avoid broad system-app exclusions unless the client explains their effect.
- Local devices disappear: Look for a local-network or LAN-access setting in the client. If none exists, test whether bypassing the relevant app restores access, but remember that doing so may also send its internet traffic outside the VPN. Use the smallest exception that solves the actual problem.
- Connections stop after the screen locks: Check Android battery optimization and background-activity controls for the VPN client and the affected app. Power management can pause an app or its background work, which may look like a routing failure. Follow the operating system’s current controls rather than applying broad battery exceptions to every app.
- Another VPN will not connect: Disconnect the existing VPN service and confirm which client Android currently shows as active. Android typically routes through one active VPN service at a time; two clients cannot generally establish independent system-wide VPN tunnels simultaneously.
After each change, reconnect and repeat the same test. Keep the device on the same network while comparing results, and avoid changing the server, protocol, DNS, and app-routing mode together. If the problem persists, note the Android version, VPN client and version, selected routing mode, affected app, and whether the issue occurs with the rule disabled. Share only the diagnostic details needed for support; never post a private subscription link or account credentials.
Review the list occasionally, especially after installing a replacement app or moving an app into a work profile. A split-tunneling rule is not a general-purpose speed switch: it is a routing policy with a clear trade-off between tunnel use and direct access. Keeping the policy short, testing both included and bypassed apps, and checking Android’s system-level VPN controls will make the setup easier to understand and maintain.