How to Synchronize uBlacklist Rulesets Across Devices

Updated

uBlacklist can sync your rulesets across devices through Google Drive, Dropbox, OneDrive, WebDAV, or browser sync. You set this up once in the extension's options, and every device signed into the same sync account pulls the same rules. This works on Chrome, Firefox, Edge, and Safari, so you can mix browsers and still keep one consistent blocklist.

What "sync" actually covers

uBlacklist has two separate things people often confuse:

  • Your own rules — the sites, URL patterns, and title regexes you add yourself.
  • Subscribed public rulesets — shared blocklists you subscribe to, which update on their own.

Sync applies to your rulesets so that edits made on one device appear on the others. Subscriptions are a rule source: once you subscribe to a public ruleset, it feeds entries into your blocking setup, and you can rely on it instead of hand-maintaining every domain.

Sync methods available

Method Typical use
Google Drive You already live in Google's ecosystem
Dropbox Cross-platform, works well on desktop and mobile
OneDrive Microsoft account users
WebDAV Self-hosted or third-party storage you control
Browser sync Simplest option if you stay within one browser's account

Pick one and use it on every device. Mixing methods across devices is the most common reason rules look "missing."

Step-by-step setup

  1. Install uBlacklist on each device. Use the store for your browser — Chrome Web Store, Firefox Add-ons, Edge Add-ons, or the App Store (the Safari version is maintained by Group-Leafy).
  2. Open the extension's options page on the first device. This is where sync settings live.
  3. Choose a sync service from the list above and connect your account. The extension will ask you to authorize access to that storage.
  4. Add or import your rules on this device. If you already have a ruleset, this becomes the source of truth.
  5. Repeat the sync setup on your other devices, selecting the same service and account.
  6. Verify by adding a test rule on one device, then checking that it appears on another after the sync cycle completes.

Expected result: the same blocked sites and patterns apply everywhere, and a change on one device propagates to the rest.

Common snags

  • Different sync services per device. Rules won't merge — each service holds its own copy. Standardize on one.
  • Not signed in. Browser sync and cloud sync both require an active account session; a logged-out device won't pull updates.
  • Confusing subscriptions with your rules. A public ruleset you subscribe to updates independently. If a site is still blocked after you remove your own rule, check whether a subscription is supplying it.
  • Safari behaving differently. The Safari build is maintained separately, so confirm sync is configured there too rather than assuming it inherits desktop settings.

A practical setup

If you want minimal maintenance: subscribe to one or two reputable public rulesets for broad coverage, then use cloud sync (Drive, Dropbox, or OneDrive) for the handful of personal rules you add on top. That way the shared lists stay current on their own, and your custom entries follow you across every browser and device.