Android VPN Split Tunneling: Choose Which Apps Use VPN
Route selected Android apps through your VPN while letting the rest connect directly. Learn where to find per-app settings, test your rules, and fix common connection issues.
Android VPN split tunneling lets you choose which apps send traffic through a VPN and which connect directly to the internet. It can be useful when one app needs a VPN connection while another depends on your normal network, a local device, or a service that works better without the VPN. The key is to understand which routing mode your VPN client provides, then test both paths instead of assuming that a selected app is covered exactly as expected.
Android does not provide one universal per-app split-tunneling screen that works the same way with every VPN. The available controls usually depend on the VPN app or the profile it imports. Android’s system VPN settings can show and manage a VPN connection, but the app-selection list—when available—is generally configured in the VPN client. Menu names and supported options vary, so treat the following as a practical method rather than a promise that every client has identical controls.
What split tunneling means on Android
A VPN creates a route for network traffic, and split tunneling changes which apps use that route. In a typical per-app setup, you choose apps to include in the VPN or apps to exclude from it. The wording matters: an “include selected apps” list means only the chosen apps use the VPN, while an “exclude selected apps” list usually sends the chosen apps directly and leaves other traffic on the VPN. The same selection can therefore have the opposite effect when you change modes.
Think of the configuration as two paths rather than a single on/off switch. Apps assigned to the VPN path send eligible traffic through the active VPN connection. Apps assigned to the direct path use the device’s ordinary network connection, such as Wi-Fi or mobile data. A direct-path app does not inherit the VPN’s exit address simply because another app on the same phone is using the VPN.
2
Possible paths: VPN or direct
Per app
Selection may be available in the client
Test
Verify each app after changing rules
Per-app rules are not the same as choosing a country or server, and they do not necessarily control every connection made on behalf of an app. A browser, for example, may open links in another app; apps can rely on shared system components, embedded web views, or external services for sign-in and content. As a result, a page that appears inside one app may not behave like a page opened in your usual browser.
Also distinguish app routing from website-level rules. Per-app split tunneling usually selects an Android app as a whole, not an individual domain or feature inside that app. If the client offers only app selection, it may not let you send one site in a browser through the VPN and another site in the same browser directly.
Check whether your VPN client supports per-app rules
Start inside the VPN client, not by searching every Android settings page. Open the client’s settings, connection preferences, or the active VPN profile and look for terms such as “split tunneling,” “per-app routing,” “include apps,” or “exclude apps.” Some clients offer a selectable app list; others provide only system-wide VPN routing or a different rule system. If you cannot find an app filter, check the client’s own documentation and the settings for the profile you are using before assuming the feature is available.
When a profile has been imported from a subscription, it may not expose every option supported by the underlying connection format. A client can display server and connection settings while keeping app routing in a separate local menu. Conversely, a profile may be read-only, so changing its connection details is not the same as changing the Android app filter. If the interface says a setting is controlled by the profile or administrator, do not edit unrelated fields just to make the option appear.
Android may ask the client to establish a VPN connection the first time you connect, and the system can show a VPN indicator while that connection is active. This indicator does not confirm that a particular app is using the VPN: an excluded app can still connect directly while the VPN remains on for other apps. Check the client’s routing list and verify the result from the apps you care about.
Before changing settings, write down which apps should use the VPN and which should remain direct. Keep the list short at first. For example, you might put a work app on the VPN path while leaving a local-network utility direct, but the correct choice depends on your privacy needs and the app’s requirements. If you are comparing client availability or connection options, the VPN32 home page is a natural place to review the service information; it does not replace checking whether your chosen Android client exposes per-app routing.
- ✅ Confirm that the active client or profile offers per-app routing.
- ✅ Read whether the list includes selected apps or excludes them.
- ✅ Decide which apps need VPN privacy and which need a direct route.
- ❌ Do not assume the Android VPN indicator proves every app uses the VPN.
Configure and test your app rules
Use this sequence to make one controlled change at a time. Exact button names differ by client and Android version, but the logic is the same. If the client is currently connected, follow its instructions for editing a live profile; some apps require disconnecting before the app list can be changed.
- Open the active VPN profile. In the VPN client, locate the profile or connection you actually use. If several profiles exist, verify the selected one before editing its routing options.
- Find the app-routing control. Open the client’s settings and locate the split-tunneling or per-app section. If Android asks you to approve the VPN connection, review the system prompt and confirm that it refers to the client you intended to use.
- Choose the routing mode. Read the description beside the app list. In include mode, add the apps that should use the VPN. In exclude mode, add the apps that should bypass it. If the interface offers a master switch as well as a list, check both; an inactive feature can leave the list with no effect.
- Apply a small test set. Select one app whose route is easy to check and leave the rest of the list unchanged. Save the settings, then disconnect and reconnect if the client requests it. Reconnecting helps ensure the new selection is applied to fresh network sessions.
- Test both sides of the rule. Open the selected app and a second app assigned to the opposite path. Check a suitable IP or network-information page in each, where available, and confirm that the observed route matches the rule. Do not rely on one app’s result to represent the entire phone.
- Expand the list gradually. If the first pair behaves as expected, add the remaining apps in small groups. Re-test after each change so that a failure can be linked to a specific rule rather than a long set of simultaneous edits.
For a useful comparison, keep the test conditions consistent: use the same network, the same VPN profile, and the same test destination when comparing before and after. A page’s language, available content, or response time is not by itself proof of the route being used. A page can be cached, use a content delivery network, or apply account-specific settings. Prefer a clear network-address check, and repeat it from each app where possible.
Testing should include the app’s real task, not only its home screen. A messaging app may load its interface while a separate call or media feature fails. A work app may reach its login page but fail to connect to an internal resource. Check the specific function you need, and note the exact error or step that fails. That makes it easier to tell a routing issue from an account, service, or app problem.
A VPN connection can be active while an excluded app uses the direct network. Verify the route from inside the app being tested, and avoid entering sensitive account details into a route you have not checked.
Choose apps according to privacy and connectivity needs
Decide the route based on the data an app handles and the network resources it needs. An app may contain private messages, account credentials, or work information that you want to send through the VPN. Another may need to discover a printer, media receiver, or other device on the local network, which can be harder if its traffic is routed through a remote VPN. Neither rule is universally right: the choice depends on the task, your trust requirements, and how the VPN client handles local traffic.
Apps to consider for the VPN path
Consider placing an app on the VPN path when you want its network traffic to use the VPN connection, especially when using networks you do not fully trust. Remember that the VPN route does not make an app’s account, device, or data automatically anonymous. The app can still identify a signed-in account, request permissions, or send information to its own service. A VPN changes the network path; it does not replace careful account and privacy settings.
Apps to consider for a direct path
A direct route can be useful for an app that needs local network access, relies on a specific connection method, or is disrupted when routed through the VPN. However, bypassing the VPN means that the app’s traffic uses the ordinary network connection instead. This can reveal the network’s public IP address to the destination and may expose traffic to the network operator according to the connection and app’s encryption. Do not exclude an app merely because it is slow until you have checked for a client, DNS, or service issue.
Some devices separate personal apps from work apps, or allow cloned app instances. A per-app list may show package names or more than one entry with similar labels. Confirm which instance you are selecting. A work-profile copy can have different permissions and network behavior from its personal-profile counterpart, so test the instance you actually use rather than assuming that one selection covers both.
Keep the routing policy understandable. A short list makes future troubleshooting easier, especially after an app update or a change of VPN profile. Record the purpose of each exception in a note outside the client, such as “local printer app stays direct” or “account app uses VPN.” Avoid broad exclusions when a narrow, app-specific rule is enough.
Troubleshoot common routing problems
If an app does not follow the expected route, first verify the selected profile and whether the list is in include or exclude mode. Then check that the feature is enabled, save the change, and reconnect. A rule can be correct but appear ineffective if an existing session has not reopened its network connections. Force-closing and reopening the affected app may help, but do not clear app data unless you understand what local information will be removed.
- The selected app has no connection: Temporarily test the app with split tunneling disabled, if the client allows it. If it works only when the VPN is off, check whether the route, DNS handling, or the selected server is compatible with the app. Restore your intended policy after the test.
- The app appears to bypass the VPN: Confirm that the list is in include mode or that the app is not excluded. Check the route from within that app rather than looking only at the Android status bar.
- Only part of an app works: The app may use separate services or embedded content for different functions. Test the exact failing feature and check whether another app, browser, or system component opens it.
- Local devices are unreachable: Check whether the client has a separate local-network option. A per-app direct rule may not be the only factor affecting access to devices on the same Wi-Fi network.
- The problem starts after changing networks: Disconnect and reconnect the VPN, then reopen the affected app. Moving between Wi-Fi and mobile data can interrupt existing sessions, so a reconnect is a useful diagnostic step.
Also check whether another VPN-based app is active. Android clients that use the system VPN service can conflict because the device’s VPN connection is managed at the system level. A firewall, filtering app, or another VPN client may also change how traffic is handled. Test with only the intended VPN client active, then restore other tools one at a time if they are required.
Battery and background restrictions can interrupt a client or app after the screen turns off. If the connection fails only after the device has been idle, check Android’s battery settings and the client’s guidance for background operation. Do not disable every battery safeguard by default; make a targeted change only when the symptoms point to a background-process interruption.
Finally, distinguish a routing failure from a platform-side restriction or outage. If an app reports an account, permission, or service error, read that message and check the app’s own status or support information. Changing VPN routes repeatedly will not resolve an expired session, a missing permission, or a service that is unavailable.
Keep the configuration clear over time
Per-app rules can become confusing when you add apps, import a new profile, or reinstall the client. After any significant change, revisit the routing list and verify a small sample from both paths. App updates can also change package details or network behavior, so a rule that worked previously is not a guarantee that every feature will continue to behave the same way.
Keep a simple record of the intended policy: which apps use the VPN, which apps connect directly, and why each exception exists. This is especially helpful if you later switch clients, restore a profile, or troubleshoot after an Android update. Do not store a private subscription link in an unsecured note just to document the rules; record the app names and routing decisions, not account credentials.
Use the least complicated setup that meets your needs. If most apps should use the VPN, an exclude list with a few deliberate exceptions may be easier to maintain. If only a small number need it, an include list may be clearer. These are organizational choices, not guarantees about performance or privacy: always read the client’s mode description and verify the actual route.
When testing is complete, reconnect once more and confirm that the VPN client reports the intended profile as active. Open at least one app assigned to each path and check its expected behavior. If you cannot verify a route, treat it as unknown rather than assuming that the interface label proves it. A clear, tested rule set is more useful than a long list of unexamined exceptions.