Compare VPN behavior in normal and private tabs

Your VPN seems to work in a normal browser tab, but you are not sure whether a private tab uses the same connection. The answer depends on how your VPN is set up. A VPN app and a browser extension can behave differently, and private browsing does not automatically route traffic through a VPN.

Test both tabs separately with the VPN Leak Test. It checks whether your real IP address appears through IPv6 or WebRTC while the VPN is on. The comparison can help you spot a routing difference and decide what to check next.

Compare the two tabs

1. Connect to your VPN and open the VPN Leak Test in a normal browser tab. Let the test finish and note the result, including whether it identifies an IPv6 or WebRTC leak.
2. Open a private or incognito window in the same browser. For Chrome or Edge, use Ctrl + Shift + N on Windows or Command + Shift + N on a Mac. In Firefox, use Ctrl + Shift + P or Command + Shift + P.
3. Open the VPN Leak Test in that private window and run it with the VPN still connected. Note the results separately from the normal tab.
4. Compare what each test reports. If the results differ, repeat both tests once, without changing VPN servers or network settings in between.

Keep the VPN connected throughout the comparison. If you disconnect it between tests, you are comparing different network conditions rather than normal and private browsing.

What the result means

Both tabs show the same VPN connection

This suggests that both contexts are routing through the VPN in the same way at the time of the tests. It does not prove that every app or every kind of traffic is covered, but it is a useful sign that private browsing is not bypassing the connection checked by the test.

The normal tab shows the VPN, but the private tab shows your usual public IP

This can happen when you use a browser VPN extension that is allowed in a normal window but not in private browsing. The private tab may be connecting directly instead of using the extension. Check the extension's private-window permission and retest.

The private tab shows the VPN, but the normal tab shows your usual public IP

The extension or browser profile may be configured differently in the normal window, or another setting may be changing its route. Check which VPN is active in that profile. Also make sure you did not connect to a different network or change VPN settings between tests.

The reported VPN addresses differ, but neither looks like your usual IP

A VPN may use different exit servers or addresses for separate connections. A different address alone does not prove a leak. Look for a result that identifies your real public IP through IPv6 or WebRTC, and repeat the comparison before drawing a conclusion.

Only one test reports a possible leak

Treat that difference as a reason to investigate, not as proof that all your browsing is exposed. Retest both tabs, check the VPN's connection status, and confirm that the private window has the permissions its extension needs. For more background, see how to check whether your VPN leaks your IP address.

How to fix a difference

1. Allow the VPN extension in private windows. In Chrome, open Extensions › Manage extensions, find the VPN extension, and turn on Allow in incognito. In Edge, use Extensions › Manage extensions and enable Allow in InPrivate. In Firefox, open Add-ons and themes › Extensions, select the VPN extension, and allow it to run in private windows. The wording can vary by browser version.
2. Check which VPN is active. Some people have both a VPN app and a browser extension. Confirm which one is connected, and avoid assuming that an extension protects traffic from other apps. If both are active, test with one at a time so you know which route you are checking.
3. Check the VPN app's connection. Disconnect and reconnect in the VPN app, then rerun both tests. If the app has options for IPv6, WebRTC, or leak protection, review its help information before changing them.
4. Check system VPN settings. On Windows 11, open Settings › Network & internet › VPN and confirm the expected VPN connection is active. On macOS, open System Settings › VPN and check the connection there. If your VPN is controlled by a separate app or workplace profile, check that app or contact your administrator.
5. Check for split tunneling. Split tunneling sends selected apps or traffic outside the VPN. Review the VPN app's settings to see whether your browser, a browser profile, or IPv6 traffic is excluded. Change one option at a time, reconnect, and test both tabs again.
6. Restart the browser and retest. Close all browser windows, reconnect the VPN, then open a new normal window and a new private window. This clears some stale connections that may otherwise make the comparison confusing.

Why private tabs can behave differently

A private window mainly separates browsing history, cookies, and temporary site data from your regular session. It does not create a separate internet connection by itself, and it does not automatically turn a VPN on or off.

A system-wide VPN app usually routes traffic from the whole device, including both kinds of browser window, unless its settings exclude some traffic. A browser VPN extension works inside the browser and may need permission to run in private windows. Some VPN apps also use split tunneling, so the browser or a specific type of connection can take another route.

The test checks network information that the browser can expose, including possible IPv6 or WebRTC leaks. A private or local network address is not the same as your public IP address. Focus on whether the test identifies your real public address, and do not treat every difference in displayed address as a leak.

Run both tests again after changing one VPN or browser setting, so you can tell which change affected the result.