--- layout: evergreen title: Browser Recommendations description: "These are our current web browser recommendations, settings, and add-ons you can use to preserve your privacy." --- {% assign browser = site.browsers | where:"name","Firefox" %} {% for post in browser %} {% include recommendation-card.html %} {% endfor %} {% assign browser = site.browsers | where:"name","Tor Browser" %} {% for post in browser %} {% include recommendation-card.html %} {% endfor %}
When you visit a web page, your browser voluntarily sends information about its configuration, such as available fonts, browser type, and add-ons. If this combination of information is unique, it may be possible to identify and track you without using cookies. EFF created a Tool called Panopticlick to test your browser to see how unique it is.
You need to find what most browsers are reporting, and then use those variables to bring your browser in the same population. This means having the same fonts, plugins, and extensions installed as the large installed base. You should have a spoofed user-agent string to match what the large userbase has. You need to have the same settings enabled and disabled, such as DNT and WebGL. You need your browser to look as common as everyone else. Disabling JavaScript, using Linux, or even using the Tor Browser Bundle, will make your browser stick out from the masses.
Modern web browsers have not been architected to assure personal web privacy. Rather than worrying about being fingerprinted, it seems more practical to use free software plugins to regain control. They not only respect your freedom, but your privacy also. You can get much further with these than trying to manipulate your browser's fingerprint.
While software like NoScript prevents this, it's probably a good idea to block this protocol directly as well, just to be safe. Note: This disables browser-based call functionality that is used for webapps like Discord, Hangouts, Jitsi, etc.
In short: Set "media.peerconnection.enabled" to "false" in "about:config".
Explained:
If you want to make sure every single WebRTC-related setting is really disabled change these settings:
Now you can be 100% sure WebRTC is disabled.
Safari is far stricter with WebRTC than other major browsers, and it does not leak your IP address in its default configuration. If you'd like, you can follow these steps just to double-check your browser:
WebRTC cannot be fully disabled in Chrome; however, it is possible to change its routing settings (and prevent leaks) using an extension. Two open-source solutions include WebRTC Leak Prevent (options may need to be changed depending on the scenario), and uBlock Origin (select "Prevent WebRTC from leaking local IP addresses" in Settings).
Chrome on macOS and Internet Explorer do not implement WebRTC yet. But we recommend using Firefox on all devices.
{% include hr.html %} {% include legacy/sections/browser-addons.html %} {% include legacy/sections/browser-tweaks.html %}