Topic guides
Multiple Provider Subscription Merge
Merge subscription URLs from multiple proxy providers into one output URL for Clash or Mihomo clients.
On this page
When to use it
- You use multiple proxy providers and do not want many subscription URLs in your client.
- You want one Clash or Mihomo-compatible output.
- You need to organize nodes from different sources quickly.
Notes
Node names from different providers may collide. Use prefixes or templates when needed so the client can distinguish sources.
For a source list that needs ongoing maintenance
Use one-time merging when you only need a downloaded file. This page addresses a different task: maintaining one subscription entry when source A changes, source B expires and you also have a node on your own server.
A dynamic subscription combines configurations you are authorized to use. It does not merge provider accounts, balances, billing or concurrency limits. Anyone holding its generated URL may be able to retrieve the node credentials, so treat it as an access secret rather than an ordinary public page.
A maintainable three-source example
| Source | Purpose | Check before updating |
|---|---|---|
| A: your first subscription | Everyday nodes | The URL still returns node content |
| B: your backup subscription | Alternative routes | Expiry, quota or required client |
| C: one manually entered node | Your own server | Changes to server credentials |
No working shared subscriptions are supplied here. Preview your authorized sources separately with Node Inspector or conversion. Record a baseline, for example two SS nodes from A, one Hysteria2 node from B and one VLESS node from C. These counts help compare results; they say nothing about a provider's speed.
From creation to client updates
- Sign in and open Dynamic Subscriptions. Give the subscription a recognizable purpose and enter its sources and manual nodes.
- Choose a default output that your actual client core supports. Hysteria2 and TUIC support is not identical across all applications with Clash in their name.
- Review the template and prefix. Without a separate override, the effective personal or site settings apply. A subscription-specific selection must then be maintained here. A prefix is used only by compatible output formats.
- Save, validate and preview. Compare protocols, counts and diagnostics with the source baseline before copying the URL into a client.
- The client must refresh the subscription to read the current URL response. Saving a web form does not instantly push changes to every device. A static download does not become dynamic automatically.
Locate where a protocol disappears
Preview one source, then compare the combined output. If the upstream no longer returns the protocol, the merger cannot recreate it. If the source has it but parsing does not, retain a redacted example and format information. If parsing sees it but output does not, examine target compatibility and diagnostics. If the output contains it but a group does not show it, inspect selection filters and template grouping.
An identical name does not mean an identical node, and a shared endpoint does not mean shared credentials. Avoid deduplicating on those assumptions. A personal rule with a fixed group name may conflict with a new template; fix the reference rather than repeatedly changing the subscription secret.
Preview source, template or filter changes in a newly created test configuration before modifying an actively used subscription. Forwarding does not remove provider expiry or device limits. A client cache may temporarily retain the old list, so record both source-fetch and client-refresh times when comparing results.