Android split tunneling lets you choose which apps use a VPN connection and which connect directly. It can be useful when a local app needs your normal network while selected apps use a remote route, but the setting is not identical across VPN clients. Before changing anything, check whether your client supports per-app routing, understand what “include” and “exclude” mean in its interface, and test the result with a small number of apps.

What Android Split Tunneling Does—and What It Doesn’t

A VPN app on Android typically creates a local VPN interface through Android’s VPN framework, then routes some or all device traffic through it. Split tunneling changes which apps are covered by that connection. Depending on the client, you may choose apps that must use the VPN, or apps that should bypass it and use a direct connection. These are two different rule styles: an include list selects VPN apps, while an exclude list names the apps that stay outside the tunnel.

For example, you might route a browser through the VPN while letting a local banking app connect directly. In an exclude-list setup, the same result may require selecting every app except the browser. Read the setting’s description rather than assuming that checking an app always has the same meaning. A toggle labeled “bypass,” “exclude,” “route through VPN,” or “selected apps” can describe opposite sides of the rule.

Split tunneling is not a separate VPN protocol. It is an app-routing policy applied by the VPN client and Android’s networking interfaces. The available controls depend on the client, its Android version support, and sometimes the subscription or configuration you imported. A provider’s subscription supplies connection details; it does not necessarily determine which Android apps use the connection. For a broader view of the service and supported platforms, see VPN40.

It also does not make an excluded app private. That app uses the device’s ordinary network path, so the destination may see the network’s public IP address rather than the VPN exit address. A split rule cannot make a service accept an account or region that it would otherwise reject, and it does not replace app permissions, account security, or the app’s own privacy settings.

Key point: First identify whether your client uses an include list or an exclude list. Then confirm the route for each app instead of relying on the setting’s name alone.

Choose the Right App Rule Before Editing Settings

Start by writing down the outcome you want in plain language: “these apps use the VPN” or “these apps connect directly.” This small step prevents the most common mistake—selecting the right app under the wrong rule mode. If the client offers both modes, compare the list carefully before saving.

  • ✅ Use an include list when only a few selected apps should use the VPN.
  • ✅ Use an exclude list when most apps should use the VPN and only a few need a direct route.
  • ✅ Check whether the client applies changes immediately or only after reconnecting.
  • ❌ Don’t assume that Android’s system VPN screen offers the same per-app controls as your VPN client.
  • ❌ Don’t enable a second VPN app to “add” another rule; Android generally allows only one active VPN service per user profile at a time.

Android’s Settings app may show the active VPN, connection status, or options such as always-on VPN and blocking connections without a VPN. Those controls are not a universal substitute for the client’s app-selection screen. Per-app routing is commonly configured inside the VPN app, which uses Android’s VPN framework to apply the selected apps. Menu names and features differ between providers, Android releases, and third-party clients such as Clash Verge-compatible Android apps or sing-box-based clients.

Check for profile boundaries too. A work profile, private space, or another Android user can have a separate set of apps and VPN behavior. An app installed in one profile may not appear in the VPN client’s list for another profile. If an app is missing, verify where it is installed before assuming the client has failed to scan the device.

Decide whether you want a rule to apply only while the VPN is connected or to remain enforced when the connection drops. Some clients provide a kill switch or an Android always-on option; others do not. A bypass rule and a kill switch can interact in ways that vary by app and operating system version. Review the client’s explanation, and avoid enabling a “block without VPN” setting until you know whether it will block apps you deliberately excluded.

Configure App Rules on Android

The exact labels vary, so use this procedure as a decision-based guide rather than expecting identical screens on every device. Keep the first test simple: choose one app to route through the VPN or one app to bypass, save the change, and verify it before expanding the list. If you use a subscription-based client, import the subscription and establish a working connection before changing routing rules; otherwise, a connection issue and a rule issue can look alike.

  1. Confirm the baseline. Open the VPN client and connect using a profile or server that already works. Check that the client reports a connected state and that an app intended to use the VPN can load normally. Note the client’s current mode, such as “all apps,” “selected apps,” or “exclude selected apps.”
  2. Open the per-app controls. Look in the connection, routing, app filter, or split-tunneling section. If the setting is not visible, consult the client’s own help information; not every Android client exposes this feature, and the option may only be available for a particular connection mode.
  3. Choose one rule model. Select the mode that matches your written goal. In an include mode, mark apps that should enter the VPN. In an exclude or bypass mode, mark apps that should connect directly. Read any summary displayed before applying the list.
  4. Apply the change as required. Some clients update routes on the existing connection; others require disconnecting and reconnecting. Follow the client’s prompt. If the app list is empty or stale, close and reopen the selection screen, then check Android’s app installation and profile status.
  5. Test one app on each side of the rule. Open the selected VPN app and check a service that can report the observed public IP. Then test an excluded app separately. Use the same network connection for both tests, and allow each app to make a fresh request rather than relying on a previously loaded page or cached result.
  6. Expand only after the test is clear. Add the remaining apps in small groups, reconnect if necessary, and retest the important cases. Keep a note of the original setting so you can restore it if an app stops working.

During verification, separate three questions: is the VPN connected, is the app covered by the rule, and is the destination behaving as expected? A page failing to load does not by itself show that the rule is wrong. The app may require a local service, use cached session data, have its own region or account restriction, or be unable to reach the selected route. Likewise, an app opening successfully does not prove that its traffic used the intended route.

For a more useful comparison, check the selected app and a deliberately excluded app independently. A public-IP check can help identify the route, but results may differ across IPv4, IPv6, DNS, or individual app requests. Treat one test page as an indicator, not a complete audit of every connection an app makes. Avoid entering account credentials into unknown diagnostic pages just to test routing.

Verify DNS, Local Services, and Other Traffic

Per-app routing describes which app’s traffic is assigned to a VPN path, but the visible result can involve more than one network request. An app may contact a sign-in provider, a content delivery network, or a service opened through an external browser. If one screen appears to use a different route from another, check whether the request belongs to the app itself or was handed to another app. Android may apply the receiving app’s rule to that separate request.

DNS behavior is also worth checking when a result seems inconsistent. VPN clients can handle name lookups through the VPN, through a configured resolver, or according to their own routing mode. A bypassed app using a direct route may resolve names differently from an app covered by the VPN. Do not assume that a successful IP check proves that every DNS request follows the same path. Review the client’s DNS and routing documentation if your use case depends on a particular resolver.

Local-network discovery can be another source of confusion. Casting, printers, smart-home devices, and local web interfaces may depend on traffic remaining available on the home or office network. Some clients provide a local-network access option; others treat local addresses according to routing rules. If a local device becomes unreachable after connecting, test the client’s documented local-network setting before excluding broad groups of apps. Avoid adding an exception you cannot explain, because it may send more traffic directly than intended.

Also check battery restrictions and background behavior if a rule appears to work only while the VPN app is open. Android power management can pause background activity, while a client may need permission to maintain its VPN service. These are different from split-tunneling rules. Follow the client’s Android setup guidance, and change only the permission relevant to the observed problem rather than disabling unrelated security controls.

Troubleshoot or Undo a Rule Safely

If an app loses access after you edit the list, first return to the per-app screen and verify which mode is active. A list that looks correct can have the opposite effect if the client switched from “include selected apps” to “exclude selected apps.” Check whether the affected app is installed in the profile being edited, and confirm that the client saved the change. Reconnect only if the app or client indicates that a new connection is needed.

To undo a problematic configuration, remove the recently added selection or restore the previous list. If you did not record the old list, temporarily return to the client’s default routing mode—often all apps through the VPN or no per-app filtering—and test the connection. Do not clear the subscription or delete the whole client configuration as a first step: that can remove working connection details without addressing the app rule.

If only one app remains affected, compare its behavior with a second app under the same rule. If both fail, investigate the VPN connection or route. If only one fails, inspect that app’s profile, permissions, local-network needs, and account requirements. You can then test a different route or restore the app to the direct path, depending on the reason for the rule. Keep in mind that direct routing exposes the app to the ordinary network path and does not inherit the VPN route’s network handling.

When asking for help, provide the Android version, VPN client name and version, the rule mode, whether the affected app is included or excluded, and the steps that reproduce the issue. Do not post a subscription URL, QR code, authentication fields, or an unredacted configuration export. If you need to attach a screenshot, crop it to the relevant setting and remove account identifiers first.

Practical takeaway: Use the smallest rule list that meets your needs, test both a VPN-routed app and a direct app, and restore the prior mode before changing unrelated connection settings.