WebRTC is the browser feature behind in-page video calls — but it can also expose your real IP address to websites, even while you're connected to a VPN. If you want to stop that in Chrome, there's one thing to clear up first: Chrome no longer has a built-in way to turn WebRTC off.
Why the Old Method No Longer Works
For years, guides told you to open chrome://flags, search for "WebRTC IP Handling Policy," and disable it. Google removed that flag, so those instructions are now dead ends. Don't waste time hunting for a toggle that isn't there — here's what actually works.
Option 1: Block the Leak With an Extension
The simplest fix is an extension that stops WebRTC from revealing your IP while keeping calls working where possible:
- uBlock Origin: open its Settings → Privacy and enable "Prevent WebRTC from leaking local IP addresses." This is the recommended route since many people already run uBlock Origin.
- WebRTC Network Limiter (published by Google) restricts which addresses WebRTC can use without fully disabling it.
- WebRTC Leak Prevent exposes WebRTC's IP-handling modes directly.
After installing one, restart Chrome and re-test.
Option 2: Managed/Enterprise Devices
On a managed device, an administrator can set the WebRtcIPHandling policy (for example, to disable_non_proxied_udp) to prevent the leak organization-wide. This is the closest thing to a real off-switch, but it's only available through enterprise policy, not normal settings.
Option 3: Use a Leak-Protecting VPN
If you actually use video calls, blocking WebRTC entirely is counter-productive. Many reputable VPNs include built-in WebRTC leak protection that hides your real IP while keeping calls working. For most people this is the most practical balance.
Verify Your Real IP Is Hidden
Connect your VPN, then run our WebRTC leak test. If your real public IP no longer shows up, you're protected. For the full background on how this leak works, read what WebRTC is and how it exposes your IP.