Everything lives in one folder
All of your Clash Verge data sits in a single config directory: the subscription list, the profiles, interface settings, hotkeys. Back up that one folder and you have backed up everything.
Do not memorize the path. Installer builds, portable builds and package-manager builds all land in different places, so the reliable move is to click Open Config Directory inside the app and let it jump there. Roughly speaking it is %APPDATA%\io.github.clash-verge-rev.clash-verge-rev on Windows, a folder of the same name under Application Support on macOS, and the same name under ~/.local/share on Linux. Directory names can differ between versions, so treat the location that button opens as authoritative.
Quit fully before copying
Config files may be mid-write while the app runs, and a copy taken then can contain half-written content.
Two ways to make the copy
- 1
Copy the folder by hand
Exit from the tray, confirm the icon is gone, then copy the whole config directory somewhere else and put the date in the archive name. This copy is the safest one you own because it depends on no online service.
- 2
Upload through the built-in WebDAV
Fill in the server address, account and password in settings, save, then upload. Your config lands on storage you control. To restore, pick an entry from the backup list and pull it back. Restart the app afterwards, since config is read at startup.
- 3
Move to a new machine
Install the same version, quit it completely, overwrite the config directory with your backup, then start it. When moving across platforms, for example Windows to macOS, carry only subscriptions and custom rules. Anything path-dependent should be set up fresh.
Reading WebDAV errors by status code
WebDAV fails for a small number of reasons, and the status code separates them cleanly. A 401 is authentication: most often you typed the web login password, while these services usually require a separately generated app password. A 404 is the path: either the address is missing its trailing segment, or the directory does not exist on the server yet and you need to create it. If you get no status code at all and the request just hangs until it times out, the problem is at the network layer.
One detail people miss: the backup contains your subscription links, and those carry tokens. Before you drop it on a shared drive or company storage, check who that folder is shared with.
- App fully closed before copying, with no icon left in the tray
- WebDAV address includes the trailing path segment, not just the domain
- App restarted after the restore, not just closed out of the dialog
Common questions
WebDAV keeps reporting failure. How do I tell which part is broken?
Sort it by status code. A 401 means authentication failed, so generate an app-specific password in your provider console and use that instead of your login password. A 404 means the path is wrong, so copy the full WebDAV address from the provider documentation, since the trailing segment is the piece people drop. If you see neither code and the request only spins, check whether your current rules are sending that domain through a node that cannot reach it.
Subscriptions came back after the restore, but my theme and hotkeys are still the old ones.
You most likely did not restart. Interface settings are read once at startup, so the restore replaced the files on disk while memory still held the old values. Quit and reopen and they should appear. If a restart does not fix it, the backup you restored was taken before you changed the theme.