How to Disable WebRTC on Firefox (2026)
WebRTC (Web Real-Time Communication) is the browser technology behind video calls, voice chat, and file sharing without plugins. It's useful, but it has a well-known privacy problem: it can expose your real IP address even when you're connected to a VPN.
This is called a WebRTC leak. A site can use WebRTC to request a direct connection from your browser, bypassing the VPN tunnel and revealing the IP address your ISP assigned you. If you're using a VPN specifically to mask your IP, a WebRTC leak undermines that entirely.
Disabling WebRTC in Firefox takes about 30 seconds.
Method 1: Firefox about:config (recommended)
This is the cleanest fix — no extensions required.
- Open Firefox and type
about:configin the address bar, then press Enter. - Click Accept the Risk and Continue when the warning appears.
- In the search bar at the top, type
media.peerconnection.enabled. - Double-click the preference to toggle its value from
truetofalse. - Restart Firefox.
That's it. WebRTC is now disabled at the browser level. No extension needed, no ongoing maintenance.
Method 2: uBlock Origin
If you already have uBlock Origin installed, you can use it to block WebRTC IP leaks without fully disabling WebRTC — useful if you use video calling in Firefox and don't want to lose that functionality entirely.
- Click the uBlock Origin icon in your toolbar and open the Dashboard.
- Go to the Settings tab.
- Check Prevent WebRTC from leaking local IP addresses.
This blocks the leak without disabling WebRTC completely. It's a softer fix — effective for most cases, but the about:config method is more thorough.
Method 3: Disable WebRTC extension
If you want a toggle rather than a permanent change — for example, you switch between needing WebRTC on and off — a dedicated extension gives you that control.
Search for "Disable WebRTC" on the Firefox Add-ons site. Install it and it handles the toggle for you without needing to go back into about:config each time.
Check if it worked
Go to veilock.com/webrtc-leaks/ with your VPN connected. If the test shows no IP address under the WebRTC section — or only your VPN's IP — the leak is closed. If it shows your real IP, the fix didn't take and is worth revisiting.
Run this test any time you update Firefox or change your browser setup. Browser updates occasionally reset settings.
Does Veilock protect against WebRTC leaks?
Yes. Veilock handles WebRTC at the network level, preventing your real IP from being exposed through browser-based WebRTC requests. Combined with disabling WebRTC in Firefox directly, you get two layers of protection — neither one relies on the other to work.
Common questions
Does disabling WebRTC break anything?
It disables in-browser video and voice calls — Google Meet, Jitsi, and similar browser-based tools won't work. If you use those regularly in Firefox, the uBlock Origin method is a better fit since it blocks the leak without killing WebRTC entirely. For most users who don't use browser-based calling, the about:config method has no noticeable effect.
Does my VPN protect me from WebRTC leaks automatically?
Not always. Some VPNs handle WebRTC at the network level and block leaks automatically. Others don't. Veilock does. If you're unsure about your current VPN, run the leak test at veilock.com/webrtc-leaks/ to find out.
Do I need to redo this after Firefox updates?
The about:config change is persistent across updates in most cases. It's worth running a leak test after major Firefox version updates to confirm it's still in place.
Does this work on Firefox for Android?
Yes. Firefox for Android also has an about:config accessible from the address bar. The same media.peerconnection.enabled preference applies.
What about other browsers?
Chrome and Edge don't allow you to fully disable WebRTC through settings — you need an extension. Safari handles WebRTC differently and leaks are less common. Firefox is the only major browser that lets you disable it cleanly at the config level, which is one reason privacy-focused users prefer it.