Where Does v2rayN Store Config and Subscriptions?
v2rayN keeps nodes, subscriptions, and routing in guiNConfig.json in its program folder. Copy it to migrate.
Last updated
Everything v2rayN knows lives in guiNConfig.json in the program folder: nodes, subscription URLs, routing rules, and UI prefs. The core binaries sit beside it, which is why zipping the whole folder is the recommended backup.
Migration is deliberately low tech. Quit fully from the tray, copy the folder, unzip a fresh build on the new machine, and overwrite with your saved guiNConfig.json. The file holds every node key in plain text, so treat backups like passwords and encrypt archives headed to cloud storage.
Where v2rayN stores this, by platform
<v2rayN folder>\guiNConfig.json
Nodes, subscriptions, routing, and settings. Quit from the tray before copying or the file may be half written. Safer still, zip the entire program folder so cores and custom rules travel too.
<v2rayN folder>/guiNConfig.json
Same file beside the binary in deb, rpm, and portable installs. Same procedure: quit, copy, overwrite onto a fresh build on the new machine, then update subscriptions once.
<v2rayN folder>/guiNConfig.json
Same layout as other desktops. Node keys in this file equal passwords, so encrypt any backup you store online rather than uploading it in plain text.
Frequently asked questions
How do I move v2rayN to a new computer?
Exit v2rayN completely, copy guiNConfig.json (or the whole folder), and overwrite it onto a fresh official build on the new machine. Launch, confirm nodes are present, and run one subscription update.
Can I use my own core config instead of the GUI settings?
Yes. Add it as a custom config server under Servers, pointing at your JSON file. v2rayN then hands that file to the core untouched, and the GUI routing and DNS options stop applying to it.
Notice an outdated path? Let us know.