A WebRTC leak lets websites see your real IP even with a VPN. Here is WebRTC leak prevention for 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.
Why WebRTC leaks happen
WebRTC lets browsers make video calls and share files directly between two people. To do that, the browser asks a public server for its own IP addresses and shares them with the website. If your VPN does not cover that request, or if you use a VPN browser extension that only proxies web pages, the website can learn your real IP. Our WebRTC leak test shows exactly which addresses your browser reveals.
Which fix should you choose?
- Use the VPN app, not just an extension. A VPN app tunnels all traffic from your device, including WebRTC. This is the simplest fix and keeps video calls working.
- Turn on your VPN extension’s WebRTC protection. Most VPN extensions include it. It limits WebRTC to the VPN’s address.
- Change your browser’s WebRTC policy. Brave and some other browsers let you choose how much WebRTC may share.
- Turn WebRTC off completely. The strongest option, but browser-based video calls and some chat apps will stop working.
Check after every browser update
Browser updates can reset settings and change how WebRTC behaves. After an update, run the WebRTC leak test again with your VPN on. It takes a few seconds and confirms that your fix still works.
WebRTC and privacy extensions
Some privacy extensions, such as uBlock Origin, include an option to stop WebRTC from exposing your local IP addresses. These can help, but they do not replace a VPN app. Extensions can be turned off by updates or by mistake, and each browser needs its own setup. After you install any extension that claims to block WebRTC leaks, run the WebRTC leak test to check that it really works. If you use several browsers, repeat the fix and the test in each one.
FAQ
Will preventing WebRTC leaks break video calls?
Using the VPN app or limiting WebRTC keeps calls working. Turning WebRTC off completely stops calls in the browser, such as Google Meet or Discord on the web.
Do I need to prevent WebRTC leaks without a VPN?
No. Without a VPN, websites already see your real IP. WebRTC protection matters when you use a VPN or proxy to hide it.