A desktop, a phone, maybe a tablet too - keeping the same Clash config consistent across multiple devices can be done more than one way. This article breaks down three practical approaches: unified subscription links, WebDAV backup and restore, and manual export/import. For each, we cover what actually gets synced, how much of it is automated, and which situations it fits best.
Before You Sync: Know the Two Layers of Config
Before picking a tool for keeping multiple devices in sync, the first step is understanding that config splits into two layers.
- Layer one: subscriptions and rules. Node lists, proxy rules, and policy group definitions come from the subscription file plus local overrides. This is the layer you actually want to sync.
- Layer two: local client settings. System proxy toggle, launch on startup, TUN mode, port numbers, log level - these belong to the current device's state. This layer doesn't need syncing at all.
Ports are a good example. A desktop's mixed port 7897 has nothing to do with a phone; TUN mode is a desktop feature, while Android relies on the system VPN service instead. Forcing layer two to match across devices just creates conflicts. So the sync goal is clear: keep layer one consistent, let layer two stay device-specific.
Option 1: Unified Subscription Links
The idea in one line: every device uses the same subscription URL, so node and rule updates are handled by the subscription provider, and each device just pulls the latest version on schedule.
Three steps:
- On each device's client, create a new profile and paste the same subscription URL.
- Turn on auto-update, with an interval of 24 hours being plenty.
- From then on, node changes and address updates are pushed by the subscription provider, and every device picks them up automatically - no need to touch each one individually.
Custom rules can land in place through two routes.
Route one: merge at the subscription side. Use a subscription converter tool (subconverter or a similar online service) to bake your personal rules into the conversion template, so every device's downloaded subscription already includes them. Change it once, and it applies everywhere, no matter how many devices you have.
Route two: override at the client. Clash Verge Rev's "Global Override Config" supports Merge syntax, letting you insert rules ahead of the subscription's own rules:
prepend-rules:
- DOMAIN-SUFFIX,internal.example.com,DIRECT
- IP-CIDR,192.168.31.0/24,DIRECT,no-resolveNote: overrides are stored locally, so they need to be set up again on a new device. If you have lots of rules and lots of devices, merging at the subscription side is the better choice.
Verdict. Pros: nodes always stay current, with virtually zero day-to-day maintenance. Cons: it depends on the subscription link staying reachable - if the link goes down, every device is affected at once; and if personal overrides are handled client-side, they still need to be maintained on each device separately.
Option 2: WebDAV Backup and Restore
Clash Verge Rev has built-in WebDAV backup, found under Settings → Backup. Just fill in the WebDAV server address, username, and password. Nutstore, Nextcloud, Synology NAS's WebDAV package, or any standard WebDAV server will work as storage.
The workflow:
- Device A: create a backup on the backup page. Config, subscription references, and overrides are all bundled and uploaded together.
- Device B: sign in with the same WebDAV account, and the backup uploaded from Device A shows up in the list.
- Device B: select that backup and restore it - the whole config migrates over in one go.
Understand the model: this is "backup and restore," not real-time two-way sync. If Device A's config changes, Device B won't pick it up automatically - you'll need to back up again and restore again. It's great for moving everything at once, not for staying aligned day to day.
Best for: switching computers, reinstalling the OS, or setting up a new device for the first time. Regular backups also double as an off-site copy of your config, so you can pull it back even if the local config gets corrupted.
Account Security Reminder
Backup archives contain subscription links and node authentication info. Use a strong password for your WebDAV account, and it's best to set up a dedicated account or app password just for backups rather than reusing your main cloud storage login.
Option 3: Manual Export and Import
The most basic - and most reliable - route: move the config file directly from one device to another, without relying on any online service.
Export. On Clash Verge Rev's "Profiles" page, right-click the target profile and use the edit file or file location option to get the raw yaml; alternatively, open the config directory from Settings and copy the entire config folder.
Transfer. A USB drive, LAN sharing, or a messaging app's file transfer all work. The file contains node addresses and authentication info, so only send it through a channel you trust.
Import. On the new device, use the "New" or "Import" option on the Profiles page and select the yaml file; for subscription-based profiles, it's even simpler to just paste the subscription URL again and rebuild it - same end result.
Best for: one-off migrations, switching devices, or setting up the same config for family or coworkers. Not ideal for keeping multiple devices in sync long-term, since every change means repeating the export, transfer, and import cycle.
Comparing the Three Options
| Option | What Gets Synced | Automation Level | Best For |
|---|---|---|---|
| Unified Subscription | Nodes, rules (subscription side) | High: scheduled pulls | Daily long-term use |
| WebDAV Backup/Restore | Config, subscription references, overrides | Medium: manual trigger | Switching devices, reinstalls, off-site archive |
| Manual Export/Import | Single config file | Low: fully manual | One-off migration, quick sharing |
Choose based on how many devices you have and how often rules change:
- One or two devices, rules rarely change: subscription sync alone is enough.
- Many devices, lots of custom rules: merge rules at the subscription side as your main approach, with WebDAV backups as a safety net.
- Setting someone up temporarily: manual export gets the job done in ten minutes.
These three options aren't mutually exclusive. A common combo: subscription sync for everyday use, WebDAV backup as a safety net, and manual export for emergencies.
Three Security Reminders for Syncing
- A subscription link is basically your account password. It carries provider identifiers and a personal token, so never post the full link in screenshots, group chats, or public repos.
- Exported yaml files contain node server addresses and authentication info. Transfer them only through trusted channels, delete them right after use, and don't leave copies on public computers.
- Keep your WebDAV account separate. Set up a dedicated account or app password just for config backups, isolated from your main account, so any leak has minimal impact.
The core of multi-device sync isn't moving files around - it's picking a source of truth: the subscription handles nodes, backups handle full migrations, and manual export handles emergencies. Once each layer has its job, config stays under control.