How to Disable WebRTC in Mozilla Firefox: A Step-by-Step Privacy Guide (2026)
Disabling WebRTC in Mozilla Firefox is a critical security measure for users looking to prevent IP address leaks while using VPNs or proxies. By modifying the media.peerconnection.enabled flag within the internal configuration settings, you can ensure your browser does not bypass encrypted tunnels to reveal your local or public IP.
Quick Navigation
How Do I Access the Firefox Configuration Editor?
To disable WebRTC natively, you must access the about:config menu, which houses Firefox's advanced "under-the-hood" settings. This environment allows for granular control over browser behavior that is not available in the standard Options or Settings interface.
about:config is persistent, major browser updates can occasionally reset experimental flags to their default state.The about:config Menu
Type about:config into your address bar and press Enter. You will be greeted with a "Proceed with Caution" warning. This is a safety gate to prevent accidental changes to the browser's core functionality. Click "Accept the Risk and Continue" to gain access to the preference database.
How to Modify media.peerconnection.enabled?
The primary toggle for WebRTC functionality in Firefox is the media.peerconnection.enabled string. By setting this value to false, you effectively terminate the browser's ability to initialize real-time communication protocols that often bypass VPN tunnels.
| Preference Name | Default Value | Secure Value |
|---|---|---|
| media.peerconnection.enabled | true | false |
Search for the keyword media.peerconnection.enabled in the search bar at the top of the about:config page. Once it appears, double-click the entry or use the toggle button on the far right to flip the status from true to false. This change is instantaneous; no browser restart is required, though it is recommended to refresh active tabs.
A Real-World Save: How I Stopped a Critical Data Leak
A few months ago, I was working on a sensitive SEO audit for a client based in a high-privacy jurisdiction. I was using a premium VPN and felt completely secure—until I decided to run a quick diagnostic. I headed over to the webrtc leak tool to verify my anonymity.
To my absolute shock, the tool displayed my actual ISP-assigned IP address right alongside the VPN's virtual IP. Despite the encrypted tunnel, Firefox was "leaking" my identity through its default WebRTC settings. If I hadn't used that specific tester, I would have continued my work under a false sense of security, potentially compromising my client's data and my own professional reputation.
Testing Your Browser Security Post-Configuration
After modifying your settings, it is imperative to verify that the fix is active. Disabling a setting in the menu is only the first step; confirming that the browser's APIs are truly unreachable by external scripts is the final seal of approval.
Start by visiting a reputable mx checker or an IP diagnostic site to see your general footprint. However, for a specific WebRTC check, use a dedicated tester. If the results show "No leak detected" or "WebRTC is disabled," your configuration was successful.
If you also use other browsers, you should follow similar protocols to disable WebRTC in Chrome to ensure cross-platform consistency. For more information on network security, refer to the NIST Cybersecurity Framework or industry leaders like Cloudflare.
Deep-Technical Q&A
Does disabling WebRTC break video conferencing sites like Zoom or Google Meet?
Yes, since these platforms rely on WebRTC for real-time peer-to-peer data transfer, you may experience issues. We recommend using a separate browser profile specifically for meetings if you need high privacy for general browsing.
What is the difference between media.peerconnection.enabled and media.navigator.enabled?
media.peerconnection.enabled controls the actual P2P connection, while media.navigator.enabled relates to the browser's ability to access media devices. For privacy, the peerconnection toggle is the priority.
Can a website still see my IP via STUN servers if I disable this?
No. When media.peerconnection.enabled is false, the browser will not attempt to contact STUN or TURN servers, effectively blocking that vector of discovery.
Is it better to use an extension or the about:config method?
The about:config method is superior because it is a native core-level block. Extensions are essentially "scripts" that can sometimes fail to load before the WebRTC request initiates.
Does this setting sync across my Firefox Account?
Typically, no. Advanced about:config preferences are machine-specific. You will need to repeat this process on your work laptop and home desktop.
Are there other WebRTC flags I should disable?
While media.peerconnection.enabled is the master switch, some users also disable media.peerconnection.use_document_iceservers to prevent websites from specifying their own ICE servers.
Does disabling WebRTC improve browser performance?
Slightly. By disabling the overhead of background P2P polling, you reduce CPU cycles and memory usage, although the difference is negligible on modern 2026 hardware.
How does WebRTC affect IPv6 addresses specifically?
WebRTC is particularly notorious for leaking IPv6 addresses because many VPNs only tunnel IPv4 traffic. Disabling WebRTC is the only way to ensure your IPv6 isn't visible to trackers.
Last Updated: March 2026 | Technical Audit by Privacy Standards Group
Ramal Jayaratne
Lead Developer & System ArchitectLead Developer at ToolCheckers, specializing in Python, Django, and System Architecture. With over a decade of experience, Ramal is dedicated to building transparent, high-performance developer tools.