Juggling Multiple Profiles: Switching, Updating, Local Fallbacks

Having more than one subscription is the norm: a main provider, a backup, plus a local config you wrote yourself. The Profiles page in Clash Verge keeps them side by side, but only one is active at a time.

Switching and updating

Click a card and you're switched — the core hot-reloads, no app restart. The right-click menu on each card carries the useful bits:

• Update — pull the latest content from the subscription URL right now;
• Edit — change the name, URL and auto-update interval (1440 means once a day);
• Open in editor — read the raw YAML of that profile, invaluable when debugging.

If the browser is still glued to the old node after switching, close those connections on the Connections page. Import basics are in importing a subscription.

SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes

Don't put customisations in the subscription

Editing the downloaded profile is wasted effort — the next auto-update overwrites it. Anything meant to last belongs in the global extended config, which exists independently of any subscription and is layered on top of whichever profile is active.

Keep a local config as a fallback

When a subscription URL dies, a provider disappears or an update simply won't download, a "local" type profile with a handful of known-good nodes written in by hand will get you back online. Create one on the Profiles page, forget about it, and switch to it in one click when things go wrong — far better than hunting through docs mid-outage. Failed updates are covered in subscription update failures.