To prevent the potential of a leak caused by the WebRTC exposed IP addresses, it is recommended to disable WebRTC.

Disabling WebRTC may not affect normal web browsing. However, there are some sites that utilize WebRTC and disabling it may affect the functionality of the site.


To check if you experiencing a WebRTC leak, please check the link:


Disabling WebRTC in Mozilla Firefox:

Step 1: Type “about:config” into the address bar of Firefox.

Step 2: Click the Accept the Risk and Continue button.

Step 3: Type “media.peerconnection.enabled” in the search bar.

Step 4: Double-click to change the Value to false.

Disabling WebRTC in Google Chrome:

WebRTC leaks can be blocked in Chrome by the following two extensions.


uBlock Origin is a general all-purpose blocker that blocks ads, trackers, malware, and has an option to block WebRTC. WebRTC Network Limiter is an official Google add-on that specifically stops IP leaks without totally blocking WebRTC.


Disabling WebRTC in Safari:

There’s no need to disable WebRTC in Safari. Safari’s permissions model is stricter than those of most browsers. By default, no IP addresses are made available to websites except the one you use to access the site. Therefore you shouldn’t need to take any additional action to prevent WebRTC leaks in Safari. Note, however, that if you grant any particular site permission to use audio or video capture, you might expose your IPs.


Disabling WebRTC in Microsoft Edge:

Unfortunately, there’s currently no way to completely disable WebRTC in Microsoft Edge. However, you can set your browser to hide your local IP address if you:

Step 1: Type ”about:flags” into the address bar.

Step 2: Check the option marked Hide my local IP address over WebRTC connections.


As mentioned above, revealing your local IP address is not a threat to your privacy, so the steps above offer little benefit.