How to Disable WebRTC

Step 1 — Confirm the WebRTC leak

Open MyIPScan WebRTC Leak Test with your VPN active. The test collects WebRTC ICE candidates from your browser. If any candidate shows an IP that belongs to your real ISP rather than your VPN, that IP is being exposed to every site that runs WebRTC JavaScript.

Note which browser you are using — the fix is different for each one.

Step 2 — Firefox

Firefox is the easiest to fix: it provides a native toggle to disable WebRTC entirely.

1. In the Firefox address bar, type about:config and press Enter.
2. Click "Accept the Risk and Continue".
3. In the search box, type media.peerconnection.enabled.
4. The preference will appear with the value true. Double-click it to change it to false.
5. No restart required. The change takes effect immediately.

Note: This fully disables WebRTC. Google Meet, WhatsApp Web, and other WebRTC-based video calls will not work in Firefox until you re-enable it. Consider using a separate browser profile with WebRTC enabled for those services.

Step 3 — Chrome

Chrome does not provide a built-in toggle to disable WebRTC. The recommended approach is uBlock Origin.

1. Install uBlock Origin from the Chrome Web Store if you do not already have it.
2. Click the uBlock Origin icon in your toolbar and open the Dashboard (the gear icon or "Open the dashboard" link).
3. Go to the Settings tab.
4. Check the box: "Prevent WebRTC from leaking local IP addresses".
5. Save the settings.

Note: This prevents local IP exposure but may not prevent all public IP leaks in Chrome. If you need stronger WebRTC protection in a Chromium-based browser, switch to Brave (see Step 4).

Step 4 — Brave

Brave provides a built-in WebRTC IP handling policy — the strongest option available in any Chromium-based browser without extensions.

1. Open Settings (menu > Settings, or type brave://settings).
2. Go to Privacy and security.
3. Find "WebRTC IP handling policy".
4. Select "Disable non-proxied UDP" from the dropdown.

This setting prevents WebRTC from using any UDP connection that bypasses the system proxy or VPN, blocking IP leaks while keeping WebRTC functional for connections that go through the VPN tunnel.

Step 5 — Edge

Edge does not have a native WebRTC IP handling control in its settings UI.

1. Install uBlock Origin from the Microsoft Edge Add-ons store.
2. Open the uBlock Origin dashboard (extension icon > open dashboard).
3. Go to Settings and check "Prevent WebRTC from leaking local IP addresses".
4. Save the settings.

Edge also supports edge://flags but WebRTC-specific flags vary by version. The uBlock Origin method is the most reliable cross-version approach.

Step 6 — Safari

Safari on iOS and macOS has a more restricted WebRTC implementation than Chromium-based browsers. It does not expose local LAN IPs through WebRTC by default, and the public IP exposure is limited. However, if the WebRTC Leak Test shows your real IP in Safari:

• macOS Safari: There is no direct user toggle. Disabling JavaScript in Safari (Preferences > Security > uncheck "Enable JavaScript") blocks WebRTC, but breaks most websites. The practical option is to use Firefox with WebRTC disabled for privacy-sensitive browsing.
• iOS Safari: WebRTC is significantly restricted on iOS due to platform limitations. Test with the WebRTC Leak Test to see your specific iOS Safari exposure.

Step 7 — Verify the fix

After applying the change, return to the WebRTC Leak Test and run it again. The ICE candidates section should be empty or show only your VPN's IP address. If your real IP still appears:

• Confirm the setting was saved (check about:config or the extension dashboard)
• Reload the test page (do not use a cached version)
• Restart the browser if the change was made to a persistent setting

Related guides and tools

Frequently asked questions