Skip to article

Android VPN Split Tunneling: Set App Rules With Ease

Route selected Android apps through your VPN while keeping others on a direct connection. Learn where to find app-based routing options, how to verify your choices, and how to troubleshoot common connection issues.

Android VPN split tunneling lets you decide which apps use a VPN connection and which connect through the regular network. It can be useful when a work app needs a protected route but a local device or service works better without one, or when you want to limit VPN use to a few selected apps. The exact controls depend on the VPN client: some provide an app list, some offer only a global connection, and the labels can differ between Android versions.

The important part is to distinguish an app-routing rule from a guarantee about every connection an app makes. An app may use more than one network service, and Android’s VPN behavior can also be affected by Always-on VPN, “block connections without VPN,” work profiles, and manufacturer settings. Before changing anything, decide which apps should use the tunnel, which should bypass it, and whether direct access is acceptable for the data those apps handle.

Understand what app-based routing changes

Split tunneling generally works in one of two ways. An inclusion list sends only the apps you select through the VPN; other apps use the ordinary network. An exclusion list sends apps through the VPN by default, except for the apps you select to bypass it. These approaches can sound similar in a settings screen, so read the option’s description carefully before applying a rule.

  • Use an inclusion list when you want a small, known group of apps to use the VPN and prefer other apps to remain direct. Confirm whether newly installed apps are excluded until you add them.
  • Use an exclusion list when most apps should use the VPN but a few need direct connectivity. Check whether the client applies the exclusion as soon as you save it or only after you reconnect.
  • Use the default route when you do not need per-app behavior. A single VPN route is easier to reason about and reduces the chance of accidentally sending sensitive app traffic outside the tunnel.

On Android, per-app routing is usually configured by the VPN application through Android’s VPN facilities, rather than by assigning a separate network interface manually to every app. As a result, a client may show installed applications in its own settings, and its available options may depend on its implementation. Android settings menus also vary across manufacturers and releases. If the VPN client does not expose app selection, do not assume that a similarly named Android system setting exists or that another VPN app can control the current connection.

Choose apps by purpose, not by guesswork

Start with the reason you want split tunneling. For example, you might want a particular application to use a VPN while keeping a local-network utility direct. Write down the intended result in plain language before opening the settings: “This app uses the VPN; these other apps do not.” That statement helps you detect a reversed include/exclude list before it affects several apps.

Consider the following groups separately rather than selecting apps based only on their names:

  • Apps that need a VPN route: Select only the apps that should use the tunnel, and verify that their sign-in, content loading, and background activity work after connecting.
  • Apps that need local access: A printer, casting utility, or another local-network tool may behave differently when VPN routing is active. Whether excluding it solves the issue depends on the app and the client’s routing behavior; test the actual function, not just whether the app opens.
  • Apps carrying sensitive information: Review their privacy and network requirements before allowing a direct route. A bypass rule can change which network path handles their traffic.
  • System and vendor components: Avoid changing unfamiliar system entries just because their names are unclear. They may support another app, device features, or system services. If the client offers no explanation, leave them unchanged until you can identify their purpose.

Also account for duplicate or separate app environments. An Android work profile can contain a separate copy of an app, with its own icon and data. A personal-profile selection may not describe the work-profile copy, and a client may present profile apps differently. If the app appears more than once, identify which profile you actually use and test that instance.

For a broader overview of the service and its supported platform options, you can visit QingVPN. For split tunneling specifically, however, rely on the controls and documentation shown by the Android client you have installed; feature availability can differ between clients and versions.

Selection rule: Start with the smallest possible app list, confirm whether it is an inclusion or exclusion list, and add exceptions only when a repeatable test shows they are needed.

Set the app rules and verify them step by step

Use this process when your Android VPN client provides per-app routing. Menu names vary, so treat the labels below as concepts rather than exact button text. If an option is missing, check the client’s own help or release notes instead of changing unrelated system settings.

  1. Record the starting state. Note whether the VPN is connected, which routing mode is selected, and whether Always-on VPN or a setting that blocks connections outside the VPN is enabled. If you already have a working configuration, take a screenshot or write down the selected apps so you can restore it.
  2. Open the active VPN client’s settings. Look for options described as app routing, per-app VPN, split tunneling, excluded apps, or allowed apps. Do not configure a second VPN client at the same time; Android VPN connections can conflict, and a competing client may replace or interrupt the existing route.
  3. Read the mode description before selecting apps. Determine whether the list means “only selected apps use the VPN” or “selected apps bypass the VPN.” If the client offers a switch between those modes, confirm the switch’s state after saving rather than relying on the list alone.
  4. Choose one test app first. Apply the smallest rule that can demonstrate the behavior you want. Save the selection, disconnect and reconnect if the client requests it, and wait for the client to show its normal connected state.
  5. Test the selected app and a control app. Open the app whose route you changed, then test an app that should retain the other route. Check a real task, such as loading the relevant service or reaching a local device. Merely seeing an app launch does not confirm which network path it used.
  6. Check the route with a suitable verification method. If you use an IP-checking service, compare results from the selected app’s connection with the expected VPN or direct behavior. Some apps do not expose a browser-like page, so an IP check in a separate browser may only report the browser’s route, not the route used by another app. Interpret each result in the context of the app that made the request.
  7. Expand the rule gradually. Add the remaining apps one at a time, reconnecting and checking after meaningful changes. If the result becomes unclear, restore the last known working selection and repeat the test with fewer variables.

Keep a note of the mode and selected apps if you depend on the configuration. Client updates, app reinstalls, Android profile changes, or a reset of the VPN settings may alter the list or its behavior. Recheck the route after a significant change instead of assuming that an old selection is still active.

  • ✅ Confirm the selected mode means what you intend: selected apps through the VPN or selected apps direct.
  • ✅ Verify a changed rule using the app that should follow it, not an unrelated browser alone.
  • ✅ Reconnect when the client requires it, then test both a selected app and a control app.
  • ❌ Do not infer a route from an app’s display name, a successful launch, or a connected indicator alone.
  • ❌ Do not enable a direct bypass for sensitive apps without considering the privacy consequences.

Troubleshoot apps that stop connecting

If an app fails after you change a rule, first return to the simplest configuration: disable per-app routing if possible, reconnect the VPN, and test the app again. If it works under the default route, reapply the routing rule with one app at a time. This separates a route-selection problem from an app outage, account issue, or unrelated network change.

Check that the list mode is not reversed

A reversed mode is a common source of confusion. In an inclusion mode, an unselected app may remain direct; in an exclusion mode, an unselected app may use the VPN. Compare the client’s description with the observed result for one test app. If the client uses unfamiliar wording, temporarily select a single non-sensitive app and verify what happens before adding the rest.

Review Always-on VPN and blocking options

Android or the VPN client may offer an Always-on setting and, on some devices, an option to block connections that do not use the VPN. These controls can prevent an app from using a direct route even when you have added it to a bypass list. Conversely, changing these protections can allow traffic to go direct during a disconnection. Review their descriptions and decide whether continuity or preventing non-VPN connections is more important for your use case. Do not turn off a protection just to make an app connect unless you understand what traffic may then use the regular network.

Separate routing issues from other causes

If the app still fails with routing rules disabled, check whether the same app works on the ordinary network, whether another VPN or proxy is active, and whether the client reports a connection error. Also consider local DNS settings, Private DNS, battery restrictions, and background-data controls. These can affect name resolution or background activity independently of an app-routing list. Change one setting at a time and return it to its original value if the result does not help.

For local services, test from the same Wi-Fi network and confirm that the device can reach the local resource without the VPN. Some clients provide separate controls for local network access; that is not necessarily the same as excluding a particular app. Do not treat an app bypass as a general fix for every local-network problem, and do not assume it will expose only local traffic unless the client clearly documents that behavior.

Keep the configuration understandable over time

Split tunneling is easier to maintain when each exception has a reason. Keep the list short, remove rules that are no longer needed, and review it after changing VPN clients or moving an app between personal and work profiles. When an app updates its network behavior, re-test the task that motivated the rule; a previously successful setup may not cover every connection the updated app makes.

Think of the VPN status indicator as one useful signal, not a complete audit. It can tell you that the client considers a tunnel active, but it does not by itself prove that every app is using it, that an excluded app is direct, or that all background requests follow the same path. Use client documentation and app-specific checks together, and avoid making conclusions from a single test performed in another application.

If your goal is simply to make one app work, first confirm whether the problem is actually caused by VPN routing. Changing several app rules, DNS options, battery settings, and system protections at once makes it difficult to identify the cause and can weaken privacy without solving the original issue. A controlled test—one rule, one app, one verification task—produces a clearer result.

Bottom line: Use per-app routing only when you have a clear reason, verify the include/exclude semantics in your client, and test the affected app directly. If the client does not provide an explicit app-routing feature, do not assume Android will apply per-app rules on its behalf.
First Month Free