Updated July 2026 · 6 min read
Enhance profiles with Merge
Merge exists for one reason: you want extra lines on top of a subscription without losing them every time it updates. It is a YAML fragment layered over the subscription, and an update cannot wash it away.
The problem it actually solves
Editing the subscription file directly does work, right up until the next update re-downloads the file and takes your changes with it. That single annoyance is the entire reason Merge exists.
It is a separately stored YAML fragment that gets layered over the subscription every time the config is generated. Create a Merge profile on the Profiles page, enable it, and it applies to whichever subscription is currently active while that subscription keeps updating as normal.
The three things people use it for
First, pushing your own rules to the very top of the rule table so they sit ahead of the thousands that came with the subscription. Second, appending custom proxy groups: a dedicated group for downloads or streaming, with rules pointed at it.
Third, overriding global fields such as the mixed port, allow-LAN, the log level or the whole DNS block. Writing one of those in Merge replaces the field of the same name from the subscription. This category is replacement rather than merging, so what you write is all that survives.
Merge is YAML, so indentation has to be spaces. One tab pasted in from somewhere else stops the whole config from being built, and the error often points at an unrelated line.
Where you insert decides what wins
A field can be replaced wholesale or appended to, and the two intentions have to be kept apart. Rules and proxy groups are normally appended, with rules going to the front. Ports and DNS are straight replacements that push the original value out.
If a rule went in but nothing changed, open the Rules page and look at the table that is actually live, checking that your lines really do sit ahead of the subscription ones. Reading the merged result beats guessing from the source files.
Saving is not applying
Editing a Merge only stores the fragment; what is running is still the config built last time. Go back to the Profiles page and apply the current subscription again so it is rebuilt and pushed to the core. Only then is the change live.
When the build fails, read the log from the very first error downward. The long tail after it is usually collateral, and the cause is normally indentation or a missing colon. If what you need is content generated conditionally, Merge is the wrong tool and Script is the right one.
What is the project?
Clash Verge Rev is a Tauri-based GUI for Mihomo with profile management, system proxy, TUN mode, rule editing and WebDAV backups.