A WebRTC leak lets websites see your real IP even with a VPN. Here is how to prevent one in each major browser. Run the WebRTC leak test before and after so you can see the fix work.
Firefox
- Type about:config in the address bar and accept the warning.
- Search for media.peerconnection.enabled and set it to false.
This turns WebRTC off completely. Browser video calls will stop working until you turn it back on.
Chrome
Chrome has no built-in switch. Use one of these:
- WebRTC Network Limiter, Google’s own extension. Pick “Use my proxy server (if present)”.
- WebRTC Leak Shield or a similar extension that sets WebRTC to use only the proxied connection.
- Your VPN’s browser extension, if it has a WebRTC protection option.
Microsoft Edge
Edge uses the same extensions as Chrome. Install one from the Chrome Web Store or Edge Add-ons and test again.
Brave
- Open Settings > Privacy and security.
- Set WebRTC IP handling policy to “Disable non-proxied UDP”.
Safari
Safari does not expose local IP addresses through WebRTC by default. Run the test to confirm your public IP matches your VPN.
On mobile
Mobile browsers have fewer settings. Use your VPN’s app (not an extension), which tunnels all traffic, then run the WebRTC leak test on your phone.
Does WebRTC Leak Shield work?
Extensions like WebRTC Leak Shield change your browser’s WebRTC policy so it only uses the proxied connection. They work well for most people. Always test after installing one.