← All guides

WebRTC leaks: how your browser can reveal your IP

4 min read · 17 November 2026

WebRTC is what makes video calls and direct file transfers work inside a browser. To find the shortest route between two people, it gathers your PC’s addresses, your local Wi-Fi address and sometimes your public one. Any web page can read that list without showing anything on screen.

To test your browser, connect the tunnel and open a WebRTC test page such as browserleaks.com/webrtc. Compare the Public IP line with the address your tunnel gives you. If you see your own provider’s address there, the browser is giving it away. A local address like 192.168.1.20 showing up is normal and says very little. Your real public address is what matters.

Turning it off in the browser

In Firefox, type about:config in the address bar, accept the warning and set media.peerconnection.enabled to false. That switches WebRTC off entirely, so browser video calls won’t work until you turn it back on. Chrome and Edge have no built-in option, so use a trusted extension such as Google’s own WebRTC Network Limiter. In Brave, go to Settings → Privacy and security and set WebRTC IP handling policy to Disable non-proxied UDP.

A browser setting only covers that one browser, and it’s gone if you reinstall. Neshta’s Egress Firewall covers the worst case: if the tunnel drops, nothing gets out over your normal connection, WebRTC included. It’s worth having both, the browser setting for while the tunnel is up and the firewall for when it drops.