Skip to content
Get Started
G2G2
4.7/5
Excellent
Trustpilot

What Is a WebRTC Leak?

A WebRTC leak is when a website learns your real IP address through WebRTC, the browser technology behind video calls, even though the browser's normal traffic goes through a proxy. It happens because WebRTC gathers network addresses on its own, outside the proxy connection.

  • Session Control
  • High Speed
  • Privacy First
Best fit for WebRTC leakStatic ISP Proxiesfrom$0.75/IP
how it works

How WebRTC leaks work

To set up a peer-to-peer call, WebRTC uses ICE to collect every address another peer might reach you on. These are called candidates: host candidates are your device's local addresses, and server-reflexive candidates are learned by asking a STUN server over UDP which public IP it sees.

That STUN request is the leak. Browser proxy settings cover web requests, and HTTP proxies carry TCP only, so the UDP request goes straight out of your real connection. The STUN server answers with your real public IP, and any page script can read the candidate with a few lines of JavaScript, without a permission prompt and without starting a call.

Current browsers hide local addresses behind random .local mDNS names, so the private IP leak of older browsers is mostly gone. The public IP leak through STUN remains unless WebRTC is restricted.

why it matters

Why WebRTC leaks matter for proxy users

A site that sees one IP on the connection and another in the WebRTC candidates knows the visitor is behind a proxy, and it now has your real address as well. If you run separate browser profiles to manage your own accounts, that mismatch undoes the point of giving each profile its own IP. Test every new profile with the WebRTC leak test after you set up its proxy.

CleanProxies static ISP proxies give each browser profile its own dedicated US carrier IP that stays the same all month, and they plug into profile tools such as Multilogin with a host, port, username and password.

WebRTC leak: what it means for you
  • Chrome and Edge: set the WebRTC IP handling policy to disable_non_proxied_udp, which makes WebRTC use the proxy or nothing. The other values, default, default_public_and_private_interfaces and default_public_interface_only, still let UDP leave outside the proxy.
  • Firefox: set media.peerconnection.ice.proxy_only to true in about:config, or turn WebRTC off with media.peerconnection.enabled.
  • Anti-detect browsers usually have a per-profile WebRTC setting; set it to follow the proxy and test again.

Static ISP proxies from $0.75/IP

The CleanProxies proxy that fits best here, with a $4.99 trial to test it first.

Dedicated IPs on US carrier ASNs with unlimited bandwidth and threads, never shared.

starting from$0.75/IP

Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.

Guides from the blog

Setup guides and best practices from the CleanProxies blog.

Get the latest insightsAll Blogs

Related terms

Terms that come up alongside WebRTC leak.

All glossary terms

WebRTC leak FAQs

Straight answers about WebRTC leak.

Not on its own. Browser proxy settings cover web requests, but WebRTC gathers addresses over UDP outside the proxy, so you also need to restrict WebRTC in the browser or profile.

Got more questions?All FAQs