Disable WebRTC in Chrome, Brave & Edge

Quick answer

If our WebRTC Leak Test shows your real IP leaking past your VPN, the fix is to block or restrict WebRTC. Here’s how on the Chromium-based browsers — Chrome, Brave, and Edge — which share the same underlying engine.

Chrome and Edge: use an extension

Chrome and Edge don’t offer a built-in switch to disable WebRTC, and they removed the old flags that once did. The reliable route is a reputable extension — the well-known “WebRTC Network Limiter” (from Google) or a privacy extension that includes WebRTC control. Install it, set it to prevent WebRTC from using non-proxied connections, and re-test.

Be selective about extensions: a privacy extension has broad access, so stick to well-reviewed, widely-used ones rather than obscure single-purpose add-ons.

Brave: it’s built in

Brave includes a native control, which is one of its privacy advantages. Go to Settings → Privacy and security → WebRTC IP Handling Policy and choose a more restrictive option such as “Disable Non-Proxied UDP.” That stops WebRTC from revealing your real IP outside the VPN/proxy path without breaking video calls entirely.

The trade-off to know

Fully disabling WebRTC can break browser-based video/voice calls (some web conferencing, certain chat features) that rely on it. The “limit” or “non-proxied UDP” options are usually the sweet spot — they stop the IP leak while keeping legitimate WebRTC working through the proxy. If a call tool breaks, loosen the setting for that site.

Verify it worked

With your VPN on, re-run the WebRTC Leak Test. A “no leak” result — only local/private addresses or a masked .local name, no real public IP — means it’s sealed. Test again whenever you change browsers or update your VPN.