Android VPN split tunneling lets you choose which apps send traffic through a VPN and which connect directly. It can be useful when a work app needs a protected route but a local device, banking app, or region-specific service works better without one. The exact controls depend on your VPN client: some let you exclude selected apps, while others let you send only selected apps through the VPN. This guide explains the difference, gives a careful setup sequence, and shows how to test and reverse the rules.

What Android VPN split tunneling means

When an Android VPN app is connected, it usually creates a system VPN interface and directs eligible device traffic through it. Split tunneling changes which apps use that route. Apps selected for the VPN send their network traffic through the VPN connection; apps excluded from it use the device’s ordinary network connection instead. The setting changes routing, not the app’s account, permissions, or content.

Clients commonly offer one of two approaches. In an exclude selected apps mode, most apps use the VPN unless you add them to a bypass list. In an include selected apps mode, only the apps on an allowlist use the VPN, while other apps connect directly. The labels differ between clients, so read the screen carefully before saving. “Bypass” and “include” describe opposite policies, and selecting the wrong mode can route more traffic than intended.

Direct does not mean that an app becomes invisible or that its traffic is automatically encrypted in the same way as VPN traffic. HTTPS and other app-level protections still apply, but the connection does not travel through the VPN tunnel. Depending on the network and the app, the local network operator or internet provider may be able to observe connection details that would otherwise be carried through the VPN. Split tunneling is therefore a routing choice, not a general privacy upgrade.

It also helps to distinguish app routing from domain rules. App-based split tunneling selects applications, usually by their Android package identity. A browser’s app traffic may go through the VPN even when it opens a website that you would prefer to access directly. Conversely, excluding the browser may send all of its destinations directly, not just one website. Domain-based rules, when available, are a separate feature and should not be assumed to exist in an app-selection screen.

Decide which apps should use the VPN

Before changing settings, write down the outcome you want for each app. For example, you might want a browser and a messaging app to use the VPN while a local smart-home app connects directly. Another person might want only a work app to use the VPN, leaving other traffic on the ordinary connection. The right policy depends on what each app needs, not on a universal list of apps that should always be included or excluded.

Consider the app’s dependencies as well as its main screen. A media app may rely on a sign-in helper, a browser-based authentication flow, or a system component to complete login. A local printer, casting device, or home-control app may need access to devices on the same Wi-Fi network. If the app cannot discover those devices while routed through a VPN, bypassing it may help, but first check whether the client has a local-network option that addresses the issue without bypassing all of the app’s traffic.

Also consider what happens when an app is excluded. It may connect directly on both Wi-Fi and mobile data, depending on how the client applies the rule. If you only need a temporary exception, note the original selection so you can restore it later. Avoid broad changes such as turning off the VPN for the entire device when the problem is limited to one app.

  • ✅ Choose an include-only policy when you want a small, clearly defined set of apps to use the VPN.
  • ✅ Choose an exclusion policy when most apps should stay on the VPN and only a few need direct access.
  • ✅ Check whether an app depends on sign-in helpers, local devices, or another app before changing its route.
  • ❌ Do not assume an app bypass rule applies only to one website or one feature inside that app.

Check the client’s policy description before connecting. If the wording is unclear, do not guess based on a toggle’s color or position. Look for an explicit explanation such as “selected apps use VPN” or “selected apps bypass VPN,” then compare it with the apps listed. When you need to consult account or client information, the Q9VPN home page is a suitable starting point; keep the app-routing decision itself in the Android client that provides the feature.

Practical rule: Define the desired route for each app first, then select the client mode whose description matches that plan.

Set up app rules on Android

Menu names vary by client version and Android release, so treat the following as a workflow rather than a promise that every screen will use the same labels. Keep the VPN disconnected while you review the policy if the client recommends doing so. If you are changing rules on a device used for work, follow the organization’s device-management policy rather than overriding managed settings.

  1. Confirm the client is connected and current. Open the VPN app and make sure it has a valid configuration and can connect without split tunneling. If the basic connection is already failing, resolve that first; otherwise it will be difficult to tell whether a later problem comes from the route or the rule.
  2. Find the per-app control. Look in the client’s settings for wording such as “Split tunneling,” “App routing,” “Bypass apps,” or “Only these apps.” Some clients place it under connection or advanced settings. If the control is not available, check the client’s own documentation rather than changing unrelated Android permissions.
  3. Select the policy mode. Read the explanatory text and identify whether the list means apps that use the VPN or apps that bypass it. Do not infer the meaning from the list alone. If the client offers separate include and exclude modes, select one and avoid adding the same app to conflicting lists.
  4. Choose apps deliberately. Search or scroll the installed-app list, select the intended entries, and review the full selection before saving. App names can be similar, and some system components may have unfamiliar labels. If you cannot identify an entry, leave it unchanged until you know what it does.
  5. Save, reconnect, and grant the Android VPN prompt if shown. Some clients apply changes immediately; others require disconnecting and reconnecting. Android may show a system permission prompt for a VPN connection. Confirm it only when you recognize the client and intended action.
  6. Test one changed app before editing more rules. Open the app and try the specific action that previously failed, such as signing in or discovering a local device. Then check a second app that should still use the VPN. Testing one change at a time makes it easier to identify a mistaken selection.

Keep a brief note of the selected mode and app names, especially if you are troubleshooting a device that other people also use. A screenshot can be useful, but hide account details, subscription information, and any private network identifiers before sharing it. If the app offers separate controls for local-network access, DNS, or protection against direct connections, treat those as distinct settings; they can change behavior beyond the simple per-app route list.

Do not run multiple VPN clients at the same time to simulate separate app rules. Android generally allows one active VPN service for a user profile, and competing VPN, firewall, or filtering apps can interfere with routing. If you need a particular app to use a VPN while another connects directly, use the split-tunneling feature in the active client that supports that policy.

Verify that each app rule works

A “connected” label in the VPN client confirms the client’s connection state, not necessarily the route of every app. Verify the outcome from the apps you changed. For an app intended to use the VPN, open it after connecting and check a relevant service or destination. For an app intended to connect directly, test the function that required direct access, such as finding a device on the local network. A successful home screen alone may not exercise the traffic that was failing.

Where available, use the client’s per-app status or connection log to see whether traffic is associated with the intended rule. You can also compare the result while connected and disconnected, but avoid changing several variables at once. A site’s displayed location can provide a clue for a browser, yet it does not prove how a different app is routed. Similarly, an app that continues to work does not necessarily reveal whether its requests passed through the VPN.

Test after switching between Wi-Fi and mobile data if you expect the same policy to apply on both. Android network changes can interrupt active sessions, and some apps keep a connection open until they are restarted. Close and reopen the affected app after changing a rule. If the client’s settings require reconnection, reconnect the VPN before drawing a conclusion from the test.

  • ✅ Check one app that should use the VPN and one app that should connect directly.
  • ✅ Repeat the relevant action after reconnecting if the client applies rules only at connection time.
  • ✅ Restart an affected app when it may be holding an existing network session.
  • ❌ Do not treat a VPN icon, a single website result, or a speed test as proof that every app follows the intended rule.

If a selected app cannot connect, first confirm the mode and whether the app is on the correct list. Then reconnect, restart the app, and test with the rule temporarily removed. If the app works only when excluded, the VPN route or a dependency may be involved; if it works only through the VPN, its direct route or the network may be the issue. These observations narrow the cause, but they do not by themselves identify a particular protocol or server problem.

Undo rules and troubleshoot interruptions

If a local service becomes unreachable or an app stops working after you edit the list, return to the same split-tunneling screen and restore the previous mode and selections. If you did not record them, remove only the most recent change first rather than clearing every setting. Save the change, reconnect if required, and repeat the same test. This preserves other working rules and helps isolate the cause.

For a broad reset, disable the split-tunneling feature or return it to the client’s default policy, then reconnect the VPN. Check whether the app now works and whether other apps still behave as expected. If the client has a “block connections without VPN” or always-on option, understand its effect before using it: a direct-connection rule may be blocked or behave differently under a no-bypass policy. The client’s documentation and Android’s current system settings are the authoritative places to confirm how those options interact.

If the rule screen is unavailable or the VPN no longer connects, disable the client’s app rules first, then test the normal connection. Avoid repeatedly clearing Android network settings or uninstalling apps as an initial response; those actions can remove useful configuration without addressing a mistaken app selection. If the problem persists after restoring the default route, record the client version, Android version, selected policy mode, and the steps that reproduce the issue. Do not include passwords, subscription links, or other credentials in a support request.

App-based split tunneling is best used as a focused exception, not as a substitute for understanding what the VPN protects. Keep the policy as simple as your use case allows, verify both included and excluded apps, and revisit the list after installing or removing apps. If a rule causes unexpected access or breaks a local function, restore the default behavior first, then make a narrower change and test it again.

Bottom line: Choose the correct include-or-exclude mode, change a small number of app rules, and verify the actual task in each app before relying on the configuration.