Skip to content
ScanMyPrivacy
Menu

Privacy how-tos

How to Stop WebRTC Leaks

Updated · 2 min read

Written by the ScanMyPrivacy team. How we write and check guides · Report a correction

WebRTC can reveal your real IP address even when a VPN is on. The fix depends on your browser. Before you start, run the WebRTC leak test with the VPN connected so you have a baseline to compare with afterwards.

Firefox

  1. Type about:config in the address bar and accept the warning.
  2. Search for media.peerconnection.enabled and set it to false.

This switches WebRTC off completely, which also stops video calls in Firefox. If you need calls, leave it on and rely on your VPN's leak protection, or search for media.peerconnection.ice.default_address_only and set it to true to restrict which addresses WebRTC offers.

Brave

Go to Settings → Privacy and security → WebRTC IP handling policy and choose Disable non-proxied UDP. This is the strongest option, and WebRTC still works through your proxy or VPN where possible.

Chrome and Edge

Chrome and Edge have no built-in switch. Google publishes an official extension called WebRTC Network Limiter that sets the browser's policy to avoid exposing your real address. Install only that extension from the official store, and avoid unknown "WebRTC blocker" extensions, which can be spyware or can change other behaviour. After installing, set its option to use only the default public interface.

Safari

Safari has no WebRTC toggle, but it hides local network addresses unless a site has camera or microphone permission, and it requires permission before gathering the most revealing details. Keep Safari updated, and do not grant camera or microphone access to sites you do not trust.

Use a VPN that handles WebRTC

Many VPN apps and browser extensions include WebRTC leak protection, and a VPN that routes all traffic through the tunnel, including UDP, closes the most common leak. Enable the kill switch and any "block IPv6" or "leak protection" settings. IPv6 is a common route for leaks: see IPv4 vs IPv6.

Check that it worked

  1. Reload the WebRTC leak test. The result should say no leak, or "no public address revealed".
  2. Run the full privacy scan to confirm nothing else is leaking.
  3. If it is still failing, try the test in a private window with other extensions disabled, because a conflicting extension can override your settings.

What you give up

Disabling WebRTC breaks browser-based video calls, screen sharing and some games. A practical approach is to use a dedicated browser or profile with WebRTC restricted for private browsing, and a normal one for calls.

Tools that can help

Privacy-focused browsers

What it does: Block many trackers by default and reduce some fingerprinting. What it does not do: Make you anonymous. Logging in, cookies you accept and unusual settings can still identify you.

  • FirefoxFreeNo commissionOpen-source browser with tracking protection built in. Visit site
  • BraveFreeNo commissionChromium-based browser with built-in tracker and ad blocking and some fingerprinting defences. Visit site

We list free and built-in options first. How we choose.

Keep reading

Frequently asked questions

Does a VPN stop WebRTC leaks?

Not automatically. A good VPN client prevents the leak, but a VPN that only changes your IP for web traffic can still leak through WebRTC. Always test.

Is it enough to disable WebRTC in one browser?

The setting applies only to that browser. Apps with embedded browsers or other browsers on the same device need their own settings.