How to Disable WebRTC in Every Major Browser

Firefox

Worth knowing: WebRTC has shipped by default in Chrome, Firefox, and Edge since around 2013, which is why disabling it requires a manual setting change rather than a simple toggle in most browsers.

1. Type about:config into the address bar and press Enter
2. Click through the "Proceed with Caution" warning
3. Search for media.peerconnection.enabled
4. Double-click it to set the value to false

This fully disables WebRTC in Firefox. Set it back to true if you need video calling features again.

Chrome

Chrome does not include a built-in setting to fully disable WebRTC. The standard approach is installing a browser extension specifically built to block WebRTC's IP-revealing behavior, since no internal flag provides an equivalent full disable.

Safari

Safari doesn't expose a user-facing setting to disable WebRTC either. On macOS, enabling the Develop menu (Safari → Settings → Advanced → "Show features for web developers") gives access to experimental feature toggles, including WebRTC-related options, though this route is intended for developers and can change between Safari versions.

Opera

1. Open Opera Settings
2. Go to Advanced → Privacy & Security
3. Find the WebRTC section
4. Select "Disable non-proxied UDP" to limit the leak, or disable WebRTC entirely depending on the version

Opera has historically offered more direct WebRTC controls than Chrome, since it's built on a similar engine but with additional privacy settings layered on top.

Edge

Microsoft Edge, built on the same engine as Chrome, similarly lacks a direct built-in toggle to fully disable WebRTC. As with Chrome, a dedicated leak-blocking extension is the practical way to address it.

The Trade-Off: Disabling Breaks Video Calls

WebRTC is the technology behind many browser-based video calling and screen-sharing tools. Fully disabling it, where possible, closes the leak completely but also breaks those features until WebRTC is turned back on — worth remembering if you use browser-based video calls regularly.

A Lighter-Touch Alternative

If losing browser-based video calling isn't acceptable, a dedicated leak-blocking extension is generally a better fit than a full disable, since it targets the specific IP-revealing behavior rather than removing WebRTC's functionality entirely. This trades a small amount of completeness for keeping legitimate features working.

Verifying the Fix Worked

Settings and extensions can be undone by an update, a reset, or simply forgetting they were changed. Re-testing periodically, rather than assuming a fix made months ago is still in place, is the only way to know your current setup is actually still closing the leak.

Doing This Across Multiple Browsers

If you regularly use more than one browser — say, Chrome for work and Firefox personally — each one needs its own separate fix, since a setting or extension applied in one doesn't carry over. Keeping a short mental checklist of which browsers you've actually addressed avoids assuming coverage that isn't really there.