Topic guides
Clash Subscription Merge
Merge multiple Clash or Mihomo subscription URLs into one refreshable Clash-compatible subscription URL.
On this page
When to use it
- You have multiple Clash or Mihomo subscriptions and want one URL in your client.
- You want to apply one template, rule setup, and node handling flow.
- You need a refreshable subscription URL for long-term use.
Tip
Paste one subscription URL per line and keep the default Clash target. Preview the output before copying the generated subscription URL.
Merge nodes, not two complete YAML documents
Two Clash configurations may both define DNS, rules, listener ports and groups with identical names. Concatenating them creates duplicate root keys; a client may reject the result or read only one value. Nodebuf parses nodes from each source and generates a new output using the selected format, template and prefix. It does not promise to combine every original routing setting.
For a one-time file, open Multi-source Converter and enter authorized subscription URLs, one per line. Preview each source first to rule out login or error pages, then combine them and select Mihomo or Clash. These are two separate minimal example inputs; do not paste their two proxies roots into a single YAML document.
Source A:
proxies:
- name: Demo
type: ss
server: 192.0.2.81
port: 8388
cipher: aes-128-gcm
password: demo-a
Source B:
proxies:
- name: Demo
type: ss
server: 192.0.2.82
port: 8388
cipher: aes-128-gcm
password: demo-b
Both names are Demo, but the server and password differ. They must remain two nodes. The converter adds a suffix for a name collision, for example Demo and Demo (2). A shared name is not evidence of duplicate credentials, and renamed nodes may not fit a source's original name-based grouping rules. The example addresses and passwords are fictional.
Three checks after merging
- Count: note how many nodes each source parses and compare that with the combined result and conversion diagnostics. A successful download does not mean every unsupported node was retained.
- Fields: inspect protocols, endpoints and TLS or transport options. Conversion cannot give a target core a protocol it does not implement. Do not rename XHTTP to WebSocket to hide an error.
- References: groups must reference existing nodes or groups, and rule targets must exist. Node-only output is not a complete main configuration. A complete configuration still needs template group names to agree with personal rules.
Separate source errors from configuration errors
If A loads and B fails, check B alone: HTTP status, access permissions, quota and expiry. Some sources choose a format from the User-Agent, so a browser and proxy client may receive different content. Share redacted status and error codes for support, not secret-bearing subscription URLs.
If both parse but the client rejects the result, reduce the test to one node from each source and a basic configuration. Restore the template and custom rules gradually. A missing rule-target error usually concerns a group reference, not whether a node server is online.
A downloaded file is a snapshot. For saved sources and a reusable updating URL, read Multi-source dynamic subscriptions. For separate updates within Mihomo, read Provider files and the main configuration.