VPN Works in Browser but Not in Apps: 2026 Checklist

If websites load fine in your browser but Telegram, YouTube, Discord, your email, banking app or a game still "can't see the internet," the problem usually isn't a single magic toggle. In 2026, this kind of failure is more often tied to split tunneling, DNS, system filters, Always-on VPN mode, or how a specific app builds its connection. Below is a safe diagnostic checklist — no breaking the law, no shady scripts, no "wipe everything" advice.

This guide is useful if your VPN is already connected, your browser shows pages normally, but native apps hang on "connecting," don't load media, won't sign in, or only work once you disconnect the VPN. If you need a service for everyday secure connectivity, start from the FoliVPN landing page, and use this article as a device-side troubleshooting map.

Why the browser can work while apps don't

A browser and a standalone app don't always reach the internet through the same route. The browser may use its own DNS, HTTP/3, built-in proxy settings, an extension, stored cookies or a different network library. A Telegram, Discord, YouTube, banking client or game launcher may need UDP, WebSocket, push channels, system DNS, the local network, certificates, background permissions and separate domains for authentication.

That's why the symptom "everything opens in the browser" doesn't prove the VPN works correctly for the whole system. It only proves that one specific browser managed to open one specific site. Apple explicitly warns that VPNs and other network software can block parts of connectivity: internet, Wi‑Fi, App Store, iCloud, AirPlay, Continuity and local-network device sharing. Google's Android help highlights advanced network parameters separately: proxy, Private DNS, network metering, certificates and Wi‑Fi settings. And VPN provider documentation on split tunneling reveals another common cause: some apps may be intentionally or accidentally excluded from the tunnel.

The core diagnostic idea is simple: first figure out whether the issue is system-wide or limited to one app; then check routing, DNS and exclusions; and only after that change servers or reinstall the client.

Quick decision tree: what exactly isn't working

Before changing anything, pin down the scenario. It saves time and helps VPN support understand the issue faster.

If the failure started right after an app or system update, don't rush to change everything at once. Run one test, record the result, move to the next. Otherwise you won't know what actually helped.

Step 1. Make sure it's not a "browser-only VPN"

A common trap: the user thinks they enabled a VPN for the whole device, while in fact only an extension in Chrome, Firefox or another browser is active. In that case, sites load inside the browser, but apps go directly through the regular connection or don't get the right route at all.

Check:

1. The VPN is enabled in a dedicated app or in system settings, not just in a browser extension.
2. On your phone, the system VPN indicator is visible in the status bar.
3. The VPN client isn't set to "selected apps only" mode.
4. There's no separate proxy/VPN extension in the browser creating a false sense that the whole system is protected.

For adjacent browser-side diagnostics, you can use the article "VPN doesn't work in Chrome". But if the browser is exactly what's working, your main focus is system routing and apps.

Step 2. Check split tunneling

Split tunneling lets you route only part of your traffic through the VPN. It's convenient: for example, a video service goes through the VPN, while your local bank goes directly. But one wrong checkbox can create exactly your symptom: the browser goes through the VPN while the app bypasses it, or, conversely, the app is forced into the tunnel where DNS or region interferes with it.

Mullvad's documentation clearly warns: excluded apps use the regular internet connection and expose your real IP. Their Windows section also describes conflicts with other network software and a limitation: some Windows Store apps are hard or impossible to exclude. NordVPN's split tunneling help separately notes a DNS issue: the app may show the regular ISP IP, but the computer still uses the VPN service's DNS. This creates a mismatch that occasionally makes services behave oddly.

What to check:

• Open VPN app settings → Split tunneling / Exclusions.
• Look at both modes: "use VPN only for selected apps" and "exclude selected apps from VPN."
• Remove the problem app from exclusions and fully restart it.
• If the app runs through a launcher, add or remove not just the main .exe, but also the launcher/updater. For Discord on Windows, some VPN docs specifically mention Update.exe as an important companion process.
• On Linux, keep in mind that some clients' allowlist works not by app but by ports, port ranges or subnets.

More on the logic of these scenarios is in our article "VPN Split Tunneling in 2026".

Step 3. Untangle DNS: system, private and browser

DNS isn't a "minor detail." An app may fail to open a service if the domain resolves somewhere the server doesn't expect, or if DNS queries take one route while the connection itself takes another.

On Android, Google states that Private DNS protects only DNS queries and responses, not all internet traffic. It's enabled by default for networks that support it, and Google doesn't recommend disabling it without a reason. For diagnostics this means: don't permanently disable Private DNS, but you can temporarily check whether it conflicts with the VPN client, a corporate profile or a specific app.

On Windows and macOS, a similar role can be played by Secure DNS in the browser, third-party DNS clients, antivirus, filters, parental controls, corporate profiles and old proxy settings.

Safe test:

1. Open the problem app with the VPN on.
2. If it doesn't work, switch the VPN server within the same mode.
3. If that doesn't help, temporarily set DNS back to "auto" in the VPN client or system.
4. On Android, check "Settings → Network & internet → Private DNS": for the test, switch between "Auto" and "Off" and revert afterward.
5. In the browser, disable Secure DNS only for comparison, if the browser is behaving differently from your apps.

Important: don't use random public DNS servers "from the comments" as a permanent solution. That changes privacy, the geography of resolution and sometimes breaks banking, government and corporate services.

Step 4. Android: Always-on VPN, Private DNS and background limits

On Android, a common scenario looks like this: the browser opens sites, while Telegram, YouTube, Discord, mail or a marketplace shows "no connection." The cause may not be blocking, but a combination of system settings.

Check:

• Always-on VPN. If "Block connections without VPN" is enabled, apps can't reach the network even during brief tunnel reconnects.
• Private DNS. If it's set manually and unreachable from the current network, apps may "not see" domains.
• Data Saver and battery optimization. Some skins aggressively cut background data, making push, media and authentication unstable.
• Work profile / MDM. Managed devices may forbid changes to DNS, VPN and certificates.
• Background network permission for the specific app.

If the problem only happens on LTE/5G, use the related checklist "VPN doesn't work on mobile internet". It covers APN, Wi‑Fi vs. LTE differences and