How to Prevent WebRTC IP Leaks in 2026

Even the most expensive VPN software cannot prevent WebRTC leaks if your web browser continues to dispatch unproxied STUN queries through your default network adapter. Follow this step-by-step guide to harden your browser configuration.

1. Hardening Mozilla Firefox (Complete Native Disabling)

Unlike Chromium-based browsers, Firefox allows users to completely disable the WebRTC peer connection API directly without needing external extensions:

1. Open Firefox and type about:config in the address bar. Accept the warning.
2. In the search filter box, type: media.peerconnection.enabled.
3. Double-click the toggle button to change its value from true to false.
4. Restart Firefox and verify with our Live WebRTC Leak Test.

2. Hardening Google Chrome, Brave & Microsoft Edge

Chromium browsers do not offer a native about:config toggle to disable WebRTC entirely because core Google Workspace services (such as Google Meet) rely on it. However, you can restrict WebRTC UDP routing to proxy interfaces:

• Install WebRTC Control Extension: Open the Chrome Web Store and install "WebRTC Control" or "uBlock Origin". In uBlock Origin settings, check the option: "Prevent WebRTC from leaking local IP addresses".
• Use Brave Browser's Built-In WebRTC Policy: Navigate to brave://settings/shields and locate "WebRTC IP Handling Policy". Set it to "Disable Non-Proxied UDP".

3. Apple Safari (macOS & iOS)

In Safari on macOS:

1. Go to Safari > Settings > Advanced.
2. Check the box for "Show features for web developers".
3. In the top menu bar, click Develop > Experimental Features.
4. Uncheck "WebRTC mDNS ICE candidates" or ensure that Safari's private relay handles peer connections.