WebRTC is a technology that allows users to communicate with video and audio directly in the browser without any plugins installed. An unfortunate side effect is that your real IP is at risk to being exposed, stripping you of your anonymity.
However, you can disable WebRTC. Learn more about WebRTC on Wikipedia.
Visit our Am I Mullvad website to check whether or not your browser uses WebRTC. You're safe if the WebRTC box is green. If it's red, then follow our instructions below for disabling WebRTC.
Please note that disabling WebRTC will cause some websites that use it to not work properly. You might therefore want to re-enable it when you're not using Mullvad.
Please use Firefox instead, as there is currently no known working solution for Chrome other than a plugin that is easily circumvented.
iOS users: Chrome on iOS does not seem to implement the vulnerable parts of WebRTC yet.
Advanced users: read our Advanced options section.
Desktop and Android users can use the Disable WebRTC plugin for Firefox. Click on the "Add to Firefox" button and follow the instructions to install the plugin.
Once installed, it will disable WebRTC by default. You can check by looking for the plugin's 'W' icon in the Firefox toolbar. The plugin is working if the icon is green. Click it and it will turn red, meaning that WebRTC is enabled again.
Use these instructions if you wish to manually disable WebRTC:
To enable WebRTC again, follow the instructions until the Value column changes back to "true".
Internet Explorer does not yet implement WebRTC.
There is currently no way to disable WebRTC in Edge, however you can prevent it from leaking your local IP address. To do this navigate to "about:flags" tick the box next to “Hide my local IP address over WebRTC connections”.
macOS users: WebRTC is implemented in Safari for High Sierra (10.13). Unfortunately, there is no reliable way to disable it. We therefore recommend that you instead use Firefox as your browser and follow our instructions for disabling WebRTC in Firefox.
iOS users: WebRTC is implemented in Safari for iOS 11. Unfortunately, there is no reliable way to disable it, and the alternative Firefox method doesn't work.