Dashboard: Settings
Collapse the placeholder space left behind when some elements like an image or a frame get blocked by network filtering.
Displays how many blocked network requests are on the web page in uBlock Origin (uBO)'s badge toolbar icon.
If checked, this permits uBO to add items in the browser's context menu to improve convenience.
See Cloud storage documentation.
Checking this will disable prefetching in your browser. When prefetching is enabled, the browser can establish connections to remote servers even if the resources from these remote servers were supposed to be blocked by uBO.
It prevents the browser from bypassing uBO's filtering engine before establishing a connection to remote servers.
Mozilla's "Link prefetching FAQ":
Privacy implications Along with the referral and URL-following implications already mentioned above, prefetching will generally cause the cookies of the prefetched site to be accessed.
On Chromium 51 and above (including browsers based on Chromium 51 and above), disabling prefetching is unreliable because it does not cause DNS lookups, preconnections and prefetches to be reliably blocked since Chromium allows web pages to override that user setting. For details, see:
- https://github.com/gorhill/uBlock/issues/3219
- https://issues.chromium.org/issues/40549991
- Example of different behavior with Firefox: https://github.com/uBlockOrigin/uBlock-issues/issues/435
Checking this will prevent hyperlink auditing. Hyperlink auditing is best summarized as a "phone home" feature (or even more accurately, "phone anywhere") meant to inform one or more servers of which links you click on (and when). Here are the well-explained details, and the case of why such a feature is harmful to users is well-argued here.
Option removed from desktop browsers in uBO v1.38.
Browsers now obfuscate LAN addresses by mDNS:
- Firefox: "Enable mDNS hostname obfuscation"
- Chromium: "mDNS service for IP handling in WebRTC"
The option is still available in Firefox for Android because obfuscation is still not implemented. See: "Support mDNS hostname obfuscation on Android"
Details
Background info: STUN IP Address requests for WebRTC
Test case: Prevent WebRTC from leaking local IP address
Keep in mind that this feature prevents leakage of your non-internet-facing IP address. The purpose of this feature is not to hide your current internet-facing IP address. Make sure you do not misinterpret the test results above. For example, if you use a VPN, your internet-facing IP address is that of the VPN, so your ISP-provided IP address should not be visible to the outside world with this setting checked. Your ISP-provided IP address will be visible regardless of this setting if you are not behind a VPN or proxy.
Caveats:
In 1.31.3rc1, blocking CSP reports was enabled in Firefox to mitigate fingerprinting attempts described in LiCybora/NanoDefenderFirefox#196.
You can block network requests made as a result of your browser reporting Content Security Policy violations ("CSP reports") to a remote server (which can be 3rd-party to the site where the violation occurred).
Important: disabling CSP reporting is not something that will break web pages. The purpose of CSP reporting is strictly a development tool for websites.
Consider this excerpt from Reporting API / Privacy Considerations (my emphasis):
9.4. Disabling Reporting
[...]
That said, it can’t be the case that this general benefit be allowed to take priority over the ability of a user to individually opt-out of such a system. Sending reports costs bandwidth, and potentially could reveal some small amount of additional information above and beyond what a website can obtain in-band ([NETWORK-ERROR-LOGGING], for instance). User agents MUST allow users to disable reporting with some reasonable amount of granularity in order to maintain the priority of constituencies espoused in [HTML-DESIGN-PRINCIPLES].
There is no easy way to toggle CSP reporting in either Chromium or Firefox. This per-site switch is to address this shortcoming.
The behind-the-scene network requests that are actual CSP reports will get filtered out by this setting. So if you globally disable CSP reporting in uBO, this will also apply to behind-the-scene network requests.
Note that the blocking of CSP reports is implemented as a per-site switch internally in uBO so that an advanced user could create rules in the My rules pane in the dashboard to allow for more granular control of the blocking of CSP reports. For example:
no-csp-reports: example.com false
The above rule means CSP reports would not be blocked on example.com when CSP reports are blocked globally. The reverse will also work:
no-csp-reports: example.com true
The above rule means CSP reports would be blocked on example.com when CSP reports are not blocked globally.
From uBO 1.34.0 and above, you can enable/disable the uncloaking of canonical names. This setting is default enabled.
Before 1.34.0, this was an advanced setting since 1.25.0.
See "What's CNAME of your game? This DNS-based tracking defies your browser privacy defenses" for background information.
The setting will be disabled on platforms not supporting this feature. It is currently supported only on Firefox.
In some edge cases, it might be necessary to disable this setting to prevent network-related issues. For example, "Pages load slowly when uBlock Origin is installed" occurred when funneling network requests through a proxy.
Important note when using extension-based proxy service: Extension-based proxy services usually are performed on the fly through a browser API. In such a case, uBO's DNS queries to uncloak canonical names will NOT be caught and proxied by an extension-based proxy service. So you may want to disable this setting when using an extension-based proxy service.
Allows choosing between light and dark interface themes. The "auto" option will adapt to the theme selected in the browser. Related discussions: Dark Mode support + Dark UI.
Allows choosing the custom leading color for user interface elements.
Note it will be automatically adjusted to keep proper contrast between interface elements.
Currently most useful for users who checked "I am an advanced user" (see below).
Changes color coding of blocked/allowed/nooped connections in the overview panel and logger to be more accessible for people with color vision deficiency.
Turns off the popup bubbles with text descriptions when hovering the mouse cursor over user interface elements.
Please see: "Per site switches"
If you check this, this will enable uBO's dynamic filtering, and the dynamic filtering pane will become available from uBO's popup UI.
Unchecking this disables dynamic filtering, and the associated pane in the popup UI will no longer be available.
Advanced user mode also gives access to the advanced settings (usually hidden) and enables filtering behind-the-scene network requests.
You should avoid playing with advanced features and settings unless you fully understand what you are doing.
The bottom-most section is for you to conveniently backup/restore/reset settings in uBO.
uBO saves a text file with the following information to the location specified by your browser for the backup.
- All settings modified from the default
- Identifiers of selected filter lists
- Addresses of custom filter lists
- Contents of "My filters"
- Contents of "My rules"
- Contents of "Trusted sites"
Recommend that you backup all your settings regularly.