How do I disable WebRTC in Chrome?

Chrome doesn't have a built-in option to disable WebRTC. You need to use a browser extension like 'myip.foo WebRTC Blocker' (free, available on Chrome Web Store) or use the Chrome Privacy API through an extension to control WebRTC behavior.

How do I disable WebRTC in Firefox?

In Firefox, go to about:config in the address bar, search for 'media.peerconnection.enabled', and set it to 'false'. This completely disables WebRTC. You can also use a WebRTC blocker extension for easier toggling.

How do I fix a WebRTC leak?

The easiest fix is to install a WebRTC blocker browser extension. For Firefox, you can also disable WebRTC in about:config by setting media.peerconnection.enabled to false. Some VPNs like NordVPN offer browser extensions with built-in WebRTC leak protection.

WebRTC Leak Test

Free tool to check if your browser is leaking your real IP address through WebRTC - works on Chrome, Firefox, Edge, and Safari

Run WebRTC Leak Test

This test will detect all IP addresses your browser exposes via WebRTC. If you're using a VPN, only the VPN IP should be visible.

What is a WebRTC Leak?

WebRTC (Web Real-Time Communication) is a browser technology that enables peer-to-peer audio/video calls and data sharing directly between browsers, without requiring a server.

However, WebRTC can expose your real IP address even when using a VPN or proxy. This happens because:

Direct Connection: WebRTC tries to establish direct peer-to-peer connections
STUN Servers: WebRTC queries STUN servers to discover your public IP(s)
Bypasses VPN: These requests can bypass your VPN tunnel, exposing your real ISP IP
Automatic Behavior: This happens automatically in the background without user interaction

Privacy Risk: If you're using a VPN for privacy, a WebRTC leak can reveal your real IP address and location, defeating the purpose of the VPN.

How This Test Works

Our test uses the same WebRTC APIs that websites can use to detect IPs:

RTCPeerConnection: Creates a WebRTC connection
STUN Servers: Queries public STUN servers (Google STUN, Cloudflare STUN)
ICE Candidates: Collects all IP candidates exposed by your browser
Analysis: Compares detected IPs with your current connection IP

If multiple IPs are detected and one doesn't match your VPN IP, you have a WebRTC leak.

Test Results Explained

Leak Detected: WebRTC exposes a different public IP than your current connection. Your real IP is leaking!
No Leak: WebRTC only exposes your current VPN/proxy IP. You're protected.
WebRTC Appears Blocked: No IPs detected via WebRTC. Usually means WebRTC is blocked/disabled (good), but could also indicate network issues. See verification steps in the result.

Browser Compatibility

WebRTC is supported by all major browsers. Here's how each browser handles WebRTC and how to disable it:

Browser	WebRTC Support	Built-in Disable Option	Recommended Fix
Chrome	Full support	No	Use WebRTC Blocker extension
Firefox	Full support	Yes (about:config)	Set `media.peerconnection.enabled` to `false`
Edge	Full support	No	Use WebRTC Blocker extension
Safari	Full support	Limited	Develop menu → Experimental Features → WebRTC
Brave	Full support	Yes	Settings → Privacy → WebRTC IP Handling Policy
Opera	Full support	No	Use WebRTC Blocker extension

Learn More: Want to understand WebRTC in depth? Read our guide: What is WebRTC and Should You Disable It?

How to Fix WebRTC Leaks

1. Browser Extensions (Recommended)

myip.foo WebRTC Blocker - Our free, privacy-focused extension (no tracking, lightweight):

Chrome: Install from Chrome Web Store
Edge: Install from Edge Add-ons
Firefox: Install from Firefox Add-ons

Learn more: myip.foo WebRTC Blocker Details

2. Browser Settings

Firefox:

Go to about:config
Search for media.peerconnection.enabled
Set to false

Brave Browser:

Settings → Privacy and security
WebRTC IP Handling Policy → "Disable non-proxied UDP"

Chrome/Edge:

No built-in option - use browser extension

3. Use a VPN with WebRTC Protection

Some VPN providers offer built-in WebRTC leak protection. We recommend:

NordVPN - Browser extension with WebRTC leak protection
ExpressVPN - Browser extension with leak protection
ProtonVPN - App-level protection

Tip: Even with VPN protection, we recommend using a dedicated WebRTC blocker extension like myip.foo WebRTC Blocker for maximum privacy.

Note: Disabling WebRTC will prevent video/audio calls in your browser (e.g., Zoom, Google Meet, Discord). Consider using a separate browser for these activities.

Frequently Asked Questions

Does WebRTC leak affect all VPNs?

Yes, WebRTC leaks can affect all VPN providers because it's a browser-level issue, not a VPN issue. However, some VPN apps offer browser extensions that specifically block WebRTC leaks.

Can websites detect my real IP through WebRTC?

Yes, any website can use the same WebRTC APIs to detect your local and public IP addresses. This is a legitimate browser feature for video calls, but it can be abused for tracking.

Is disabling WebRTC safe?

Yes, disabling WebRTC is safe and won't affect normal web browsing. However, you won't be able to use browser-based video/audio calling services (Zoom, Google Meet, Discord web). You can still use their desktop apps.

What if I see multiple IPv6 addresses?

Multiple IPv6 addresses are normal due to privacy extensions (RFC 4941). As long as they're all in the same prefix range as your VPN, it's not a leak.

Can I use this test on mobile?

Yes! This test works on mobile browsers (Safari, Chrome, Firefox). However, mobile browsers have different WebRTC implementations and may behave differently than desktop browsers.

What does "WebRTC Appears Blocked" mean?

This result means no IP addresses were detected via WebRTC, which usually indicates WebRTC is disabled or blocked in your browser (good for privacy). Most likely causes:

You have a WebRTC blocker extension installed (e.g., myip.foo - WebRTC Blocker)
WebRTC is disabled in browser settings (Firefox: media.peerconnection.enabled = false)
Your VPN or firewall is blocking WebRTC/STUN traffic

Less common: Network issues, strict corporate firewall, or temporary connectivity problems. To rule out network issues, try testing from a different network (e.g., mobile hotspot).

Why do I get different results on different test sites?

Different WebRTC leak test sites may use different STUN servers, timeouts, or detection methods. Our test uses Google and Cloudflare STUN servers with a 2.5-second timeout. If you want to verify, try testing from a different network or device to see if results are consistent.

Does a VPN protect against WebRTC leaks?

Not automatically. A VPN encrypts your traffic, but WebRTC operates at the browser level and can bypass VPN tunnels. Some VPN providers like NordVPN offer browser extensions with built-in WebRTC leak protection. For maximum security, combine your VPN with a dedicated WebRTC blocker.

What's the difference between a DNS leak and a WebRTC leak?

A DNS leak occurs when your DNS queries bypass the VPN and go to your ISP's DNS servers, revealing which websites you visit. A WebRTC leak exposes your actual IP address through browser APIs. Both can compromise your privacy, so you should test for both. Use our DNS Leak Test to check for DNS leaks.

Will disabling WebRTC break video calls?

Yes, disabling WebRTC will prevent browser-based video calls (Google Meet, Zoom in browser, Discord web). However, dedicated desktop apps for these services will still work because they have their own WebRTC implementations. Many users keep WebRTC disabled for general browsing and use a separate browser or app for video calls.

How do I know if my WebRTC blocker is working?

Run this WebRTC leak test! If your blocker is working correctly, you should see "WebRTC Appears Blocked" or "No Leak Detected" (showing only your VPN IP). If you still see your real ISP IP address alongside your VPN IP, your blocker isn't working properly.

Related Privacy Guides

Guide

Need to check your DNS too?

WebRTC isn't the only way your privacy can leak. Check for DNS leaks as well:

Run DNS Leak Test

Learn more about WebRTC privacy: