2dust/v2rayN
Productivity & UtilitiesA cross-platform GUI client that manages proxy cores like Xray and sing-box for desktop users.
Overview
v2rayN is a desktop GUI client for Windows, Linux and macOS that manages proxy cores such as Xray and sing-box, with a wider list of supported cores documented in the wiki. It targets desktop users who need a graphical way to configure proxy servers, subscriptions and routing rules instead of editing core configuration files by hand. The application is written in C# and licensed under GPL-3.0.
Download and first run
- Open the Releases page and download the package matching your OS and architecture: Windows supports x64, x86 and arm64; Linux supports x64, arm64, riscv64 and loong64; macOS supports x64 and arm64. See the release files introduction for minimum OS requirements.
- Verify the downloaded files using the GPG fingerprint published in the README (
7694 5E9F 3E9A 168F 8070 F195 805D 661C 134D FAF6 8903 C199 463C 31E5 AE90 3AE0) to detect mirror, ISP or CDN tampering. - Extract and launch the client, then follow the wiki to add servers or subscription links and start the core.
The mobile counterpart is a separate project, v2rayNG.
Constraints
- The client depends on external cores such as Xray and sing-box; core availability and compatibility determine which protocols work.
- Proxy configuration requires a working server or subscription, which this project does not provide.
- Platform and architecture coverage is uneven: 32-bit x86 is only available on Windows, and riscv64/loong64 only on Linux.
- Release files are signed with GPG, so you need a GPG toolchain to verify them.
HotRepo's take
There are no recorded rank snapshots, star-curve samples or discussion threads for this repository in HotRepo, so no trend or community-reception claim can be made from site data. The observable facts are the project's long history since 2019, its broad platform matrix, and a large fork count relative to most desktop utilities — useful signals that this is a widely copied or independently built desktop proxy client rather than a single-platform tool. Readers should judge it on the documented core support and release verification process.
Written by AI from the project's README, updated . The project's own docs are the source of truth.