WindowsLinuxmacOS

Where Does NekoRay Store Profiles and Config?

NekoRay is portable, keeping profiles beside its binary on Windows and Linux, with Mac prefs in ~/Library/Preferences.

Last updated

NekoRay ships as a portable zip with no installer, so your profiles and settings live in the folder you extracted it to. Backing up means zipping that folder. There is no registry or AppData trail to chase.

One caution before committing: upstream archived the project as unmaintained and tells users to find an alternative. The app still runs, but new protocols and security fixes go to its forks and successors instead.

On Mac the preferences take the platform path under ~/Library/Preferences/nekoray, and TUN mode there needs root, so copy configs between normal and sudo launches deliberately.

Where NekoRay stores this, by platform

Windows
<nekoray folder>\ (portable, beside the exe)

Profiles, subscriptions, and generated sing-box configs live with the binary. Zip the whole folder to migrate. The updater replaces files in place, which behaves like malware to some antivirus, so expect false positives.

Linux
<nekoray folder>/ (portable, beside the binary)

Same portable layout, also available via AUR and Scoop. Copy the folder with the app closed and verify profiles load on the new machine before deleting the old copy.

macOS
~/Library/Preferences/nekoray/

Mac builds store configs here instead of beside the app. Strip the quarantine flag with xattr after downloading since the builds are unsigned. TUN mode needs sudo, which uses root's copy, so sync the two folders if you switch.

Frequently asked questions

How do I back up NekoRay?

On Windows and Linux, zip the extracted folder with the app closed. On Mac, copy ~/Library/Preferences/nekoray/. Subscription links re-fetch nodes anyway, so the critical part is any manual profile you cannot regenerate.

Is NekoRay still maintained?

No. The upstream repository is archived with a note to seek alternatives. Community forks continue the code. If you stay, pin a known good build and keep backups, since future breakage will not be fixed upstream.

Notice an outdated path? Let us know.