What is a WebRTC IP leak, and should you worry?
A WebRTC leak is when your browser reveals an IP address you thought was hidden, usually your real address while you are using a VPN or proxy. If you do not use a VPN, there is little to leak. If you do, it takes two minutes to check.
Updated
Try text chatOpens videomegle in Text mode · free · no sign-up
What the term means
WebRTC is the technology built into browsers that makes video calls, voice calls and some file transfers work without plug-ins. To connect two devices directly, it has to work out every address at which your device might be reachable and share that list with the other side. The IETF standard on WebRTC IP handling, RFC 8828, acknowledges that this can reveal more about your network than an ordinary web page would see.
"WebRTC leak" is the name for the cases where that process exposes an address you meant to keep private. There are three main kinds:
- Your real public IP address while you use a VPN or proxy. This is the one people usually mean, and RFC 8828 calls it the most significant concern.
- Your local network address, such as an address beginning 192.168. On its own it is not much use to anyone, but it was once widely used to help track people across websites.
- An IPv6 address that your VPN does not tunnel. IPv6 addresses are often publicly routable, so one appearing outside the tunnel can identify your connection.
How a leak happens
Before a call, your browser sends a small request to a STUN server, which replies with the public address your request came from. The browser also lists the addresses of your own network interfaces. These are packaged as "candidates" and sent to the other person's browser. A web page's own code can also start this process and read the candidates, which is why leak-test pages can show your addresses without placing a call.
Whether that exposes your real address depends on how your privacy tool works.
- Browser proxy extensions, including many free "VPN" extensions, often only redirect ordinary web traffic. The STUN request can go out directly instead, so it returns your real address. This is the most common source of genuine leaks.
- Split-tunnel VPNs, which send only some apps or traffic through the tunnel, can let WebRTC reach the internet the normal way. RFC 8828 specifically describes this case.
- A full-device VPN sends everything through the tunnel, including the STUN request, so the address discovered is the VPN server's. This is generally not leaky, as long as the VPN also handles IPv6 or blocks it.
There is one more subtlety. RFC 8828 recommends that, by default, browsers only use the same network route as normal web traffic. Browsers can use more of your network interfaces once you have given a site camera or microphone permission, because they treat that as a sign of trust. That is why a site you have allowed to use your camera may see more candidates than a site you have not.
What browsers already do about it
Leaks of local addresses were common a few years ago and are now much rarer. Starting in 2019, Chrome began replacing local IP addresses in WebRTC candidates with random names ending in ".local", resolved privately on your own network using a technique called mDNS. Other major browsers adopted the same approach. The main exception is pages that hold camera or microphone permission, which may still see real local addresses.
None of this hides your public address. It cannot, because a direct call has to know where to send the media. If you want the other person in a call not to see your real public address, the address has to be replaced before it leaves your device, which is what a properly configured VPN does.
Should you worry?
- If you do not use a VPN or proxy: there is nothing extra to leak. The public address WebRTC finds is the same one every website you visit already sees. In a peer-to-peer call, the other person can see it too; our guide on IP addresses in video chat explains what that does and does not reveal.
- If you use a full-device VPN: probably not, but test it once, especially if your network has IPv6.
- If you use a browser extension "VPN" or a split tunnel: yes, assume a leak until a test shows otherwise.
- If your safety depends on your location staying hidden, for example because you are avoiding a specific person, do not rely on any single tool. Test your setup and use text-only chat where you can.
How to test for a leak
- With your VPN off, search "what is my IP" and note your real public address.
- Turn the VPN on and confirm that the same search now shows the VPN's address.
- Search for "WebRTC leak test" and open a test page from a well-known privacy or VPN company. If your real address from step one appears anywhere in the results, including as an IPv6 address, you have a leak.
- For the technically curious, Chrome's internal page at chrome://webrtc-internals shows the candidates your browser gathers during a real call.
How to fix it without breaking calls
- Use a full-device VPN app rather than a browser extension, and turn on any leak protection or kill-switch option it offers.
- Turn off split tunnelling for your browser, or make sure the browser is inside the tunnel.
- Check IPv6 handling. Choose a VPN that tunnels IPv6, or one that blocks it while connected.
- Use browser settings carefully. Brave includes a WebRTC IP handling setting in its privacy options, and some extensions offer the same control in Chrome. The strictest settings, or turning WebRTC off entirely in Firefox's advanced configuration, will stop leaks but will also stop video and voice calls working in that browser.
On videomegle, video and voice connect peer-to-peer, so the other browser learns whichever public address your connection appears from: your own, or your VPN's if all your traffic goes through it. Text chat is relayed by our server and never exposes your address to the other person. Our guide on using a VPN for video chat covers the speed trade-off, what WebRTC is explains the technology in plain terms, and the anonymous chat page sets out what we see.
Sources
Frequently asked questions
Does a WebRTC leak reveal my home address?
No. At worst it reveals your real public IP address, which points to your internet provider and an approximate area, not a street address or name.
Does my VPN stop WebRTC leaks?
A full-device VPN that tunnels all traffic, including IPv6, usually does. Browser extension proxies and split-tunnel setups often do not. Run a WebRTC leak test with the VPN on to be sure.
Should I disable WebRTC?
Only if you never use browser-based calls. Disabling it stops leaks but also stops video and voice chat in that browser. Fixing your VPN setup is the better option for most people.
What are mDNS or .local candidates?
They are random names that browsers use in place of your local network address, so web pages cannot read it. Chrome began using them in 2019 and other browsers followed.