DNS Leak Checker

How to Fix a WebRTC Leak in Any Browser

WebRTC leaks expose your real IP address even when you're using a VPN. The good news is that every major browser can be configured to prevent this. Below are step-by-step instructions for each browser, plus recommended extensions that make it effortless.

Is your connection leaking right now?Run the free DNS, IP and WebRTC leak test. It takes about 3 seconds.Run the leak test →

Not sure if your DNS is leaking? Find out in seconds.

Run a Free DNS Leak Test Now

Firefox — The Easiest Fix

Firefox is the only major browser that lets you fully disable WebRTC without an extension. This is the gold standard for WebRTC leak prevention.

  1. Type about:config in the address bar and press Enter
  2. Click "Accept the Risk and Continue" on the warning page
  3. Search for media.peerconnection.enabled
  4. Double-click the entry to set it to false
  5. Close the tab — the change takes effect immediately, no restart needed

This completely disables WebRTC in Firefox. Video calling sites like Google Meet will not work until you re-enable it. For a detailed walkthrough, see our Firefox-specific guide.

Chrome — Extension Required

Chrome does not provide a built-in way to disable WebRTC for regular users. You need a browser extension to prevent the leak.

  1. Install WebRTC Leak Prevent from the Chrome Web Store
  2. Click the extension icon → set "IP handling policy" to Disable non-proxied UDP
  3. Alternatively, install uBlock Origin → go to Settings → Privacy → check "Prevent WebRTC from leaking local IP addresses"

Enterprise administrators can also enforce this via Chrome policy. Read the full Chrome WebRTC fix guide for all available methods.

Safari

Safari provides partial protection by default — it only enables WebRTC for sites you've granted camera or microphone permission. For full protection:

  1. Open Safari → Settings (or Preferences) → Advanced
  2. Check "Show Develop menu in menu bar"
  3. In the menu bar, click Develop → Experimental Features
  4. Uncheck WebRTC related options
  5. Alternatively, go to Settings → Websites → Camera/Microphone → set "When visiting other websites" to "Deny"

Microsoft Edge

Edge is built on Chromium, so the same extensions work. You also have a built-in flag option:

  1. Type edge://flags in the address bar
  2. Search for "WebRTC" and look for "Anonymize local IPs exposed by WebRTC"
  3. Set it to Enabled
  4. Restart Edge
  5. For stronger protection, install "WebRTC Leak Prevent" from the Edge Add-ons store

Brave

Brave blocks WebRTC fingerprinting by default. To verify: go to Settings → Privacy and Security → WebRTC IP Handling Policy → select "Disable non-proxied UDP". Brave is the most privacy-friendly Chromium browser for WebRTC out of the box — no extension needed.

Recommended Extensions

The Easiest Solution: Use a VPN With Built-In Protection

If you don't want to manually configure each browser, the simplest approach is a VPN that blocks WebRTC leaks at the network level. This protects every browser on your device automatically — no extensions or settings changes required.

Verify Your Fix

After applying any of the fixes above, run our WebRTC Leak Test to confirm your browser is no longer exposing your IP. Then run a DNS Leak Test to ensure your DNS queries are also protected.

Not sure if your DNS is leaking? Find out in seconds.

Run a Free DNS Leak Test Now

Related Guides

WebRTC Leak TestCheck if your browser is leaking your real IPWhat Is a WebRTC Leak?Understand how WebRTC exposes your IPWebRTC Fix: ChromeDisable WebRTC leaks in ChromeWebRTC Fix: FirefoxDisable WebRTC in FirefoxWebRTC Test ToolQuick WebRTC IP exposure checkVPN Not Working?Diagnose why your VPN isn't protecting youDNS Leak CheckerTest your DNS, IP & WebRTC privacy

Frequently asked questions

Will disabling WebRTC break video calls?

Yes. Fully disabling WebRTC will break browser-based video calling services like Google Meet, Zoom (in-browser), Discord, and Facebook Messenger. If you need video calls, use a VPN with built-in WebRTC leak protection instead of disabling WebRTC entirely.

Do I need to fix WebRTC in every browser?

Yes. WebRTC settings are per-browser. Disabling it in Firefox doesn't protect Chrome. If you use multiple browsers, configure each one separately — or use a VPN that handles it at the network level for all browsers simultaneously.

Is a browser extension enough to prevent WebRTC leaks?

Extensions like WebRTC Leak Prevent are effective for most use cases. However, they can be bypassed by sophisticated scripts in some edge cases. For maximum protection, combine an extension with a VPN that blocks WebRTC at the network level.

Does incognito/private mode prevent WebRTC leaks?

No. Incognito mode does not disable WebRTC or prevent IP leaks. Your browser still executes WebRTC requests normally in private mode. You need to explicitly disable WebRTC or use a protective extension regardless of whether you're in incognito mode.

Stop leaks for good

A VPN with private DNS on every server, a kill switch and WebRTC protection closes every leak this site tests for.

Get NordVPN →

30-day money-back guarantee · We may earn a commission