uMatrix for Opera: Essential Rules and Presets to Block Trackers Effectively

uMatrix for Opera: How to Install and Configure Powerful Script & Request Blocking

uMatrix is a granular point-and-click firewall for your browser: it lets you control which sites can run scripts, load iframes, make requests, set cookies, and more. Opera doesn’t have an official uMatrix build in its extension store, but you can install compatible builds or alternatives that provide the same request‑blocking and matrix-style rule UI. This guide shows a practical, step‑by‑step way to get a uMatrix-like experience in Opera and configure it for strong script and request blocking.

1) Options for Opera users

• Install uMatrix (if available): Some community builds (or legacy versions) may be installable if you enable developer-mode extension installation or use the Chrome Web Store for Opera.
• Use uBlock Origin (with advanced mode and dynamic filtering): uBlock Origin’s dynamic filtering UI provides near‑equivalent matrix controls and is the recommended, actively maintained alternative.
• Use a fork or compatible extension: There are uMatrix forks or similar “matrix” extensions that replicate the original UI; availability varies.

This guide assumes you’ll use uBlock Origin’s dynamic filtering in Opera because it’s maintained, readily available in the Chrome Web Store, and offers the same fine‑grained controls.

2) Install uBlock Origin in Opera

1. Open Opera → Settings → Extensions → Get extensions.
2. If needed, enable “Install Chrome extensions” (Opera’s addon page has instructions).
3. Visit the Chrome Web Store page for uBlock Origin and click “Add to Opera”.
4. Confirm installation; the uBlock Origin icon appears next to the address bar.

3) Configure core settings for matrix-style control

1. Click the uBlock Origin icon → click the gear icon (Dashboard).
2. In the “Settings” tab:
   • Check “I am an advanced user” to enable dynamic filtering (matrix UI).
   • Optionally enable “Disable cosmetic filtering” if you only want request-level blocking.
3. In the “Filter lists” tab:
   • Enable default lists (e.g., EasyList, EasyPrivacy).
   • Add extra privacy/security lists if desired (e.g., Peter Lowe’s, Malware domains).
4. In the “My rules” / “My filters” area you can save custom rules (covered below).

4) Using the dynamic filtering (matrix) UI

1. Open any webpage.
2. Click the uBlock Origin icon → click the “eye” or the large rectangle to open the dynamic filtering pane.
3. The matrix shows columns for rules (local, medium, global) and rows for resource types / domains:
   • leftmost column = local rules (per-site)
   • middle column = temporary rules (for current session)
   • rightmost column = global rules
4. Click cells to set permissions:
   • Green (allow) — permit requests of that type for that domain.
   • Red (block) — block requests.
   • Gray (neutral/unspecified) — follow higher-level rules or defaults.
5. Common useful settings:
   • Block 3rd‑party scripts and iframes by default: set 3rd‑party script/iframe cells to red on global column.
   • Allow first‑party scripts for functionality: set local first‑party script cell to green when a site needs it.
   • Use temporary rules while testing: set rules in the middle column (temporary) and commit them to “My rules” when satisfied.

5) Example starter configuration (recommended)

• Global column:
  • block 3rd‑party scripts — Red
  • block 3rd‑party frames — Red
  • block 3rd‑party XHR/fetch — Red (optional; may break some site features)
  • allow images, stylesheets — Green (to preserve layout and readability)
• Local column (per-site):
  • Allow first‑party scripts — Green (if the site needs it)
  • Allow analytics/tracker domains only if needed — Red by default
• Save durable rules: after testing, click “Commit” in the dashboard’s “My rules” to make temporary rules permanent.

6) Creating and editing rules manually

• In the uBlock Dashboard → “My rules” you can write rules like:
  • example.com 1p-script allow
  • example.com 3p-script block
• Use wildcards and domain separators to target subdomains:
  • ||example.com^ 3p-script block
• Always commit rules and click “Save” to persist.

7) Troubleshooting common issues

• Site broken after blocking scripts:
  • Temporarily allow first‑party scripts (local column) and refresh.
  • Look at the logger (uBlock Origin’s logger) to see which blocked requests cause errors.
• Video players or logins fail:
  • Allow necessary domains (CDN or auth domains) in local column.
• Extensions or updates not appearing:
  • Ensure Opera’s “Install Chrome extensions” is enabled if using the Chrome Web Store.

8) Best practices and tips

• Start conservative: block 3rd‑party scripts globally, then allow what you need per site.
• Use the logger for diagnostics before blindly allowing domains.
• Regularly update filter lists in Dashboard → Filter lists.
• Export “My rules” as backup after configuring.
• Combine with HTTPS Everywhere (or Opera’s HTTPS setting) and an ad/privacy‑focused search engine for stronger privacy.

9) If you want the original uMatrix UI

• Search for maintained forks or community builds (availability changes). If you find a compatible extension:
  • Install via the same Chrome Web Store flow or by loading it as an unpacked extension (developer mode).
  • Follow the same matrix paradigms: block 3rd‑party scripts, allow first‑party when needed.
• Warning: original uMatrix is no longer actively maintained; prefer maintained alternatives for security.

10) Quick checklist to finish setup

1. Install uBlock Origin.
2. Enable “I am an advanced user”.
3. Enable core filter lists.
4. Set global 3rd‑party script/frame/XHR to block.
5. Visit sites and allow first‑party scripts as needed.
6. Commit useful temporary rules to “My rules” and save.