V2Ray Client Download and platform installers

Desktop version: Uses a modern cross-platform interface with a structure, settings navigation, and overall experience more consistent with other desktop systems. It suits first-time v2rayN users and those who prefer the current desktop direction.

Classic WPF version: Retains the traditional Windows client layout. Navigation for server lists, subscription groups, system proxy, and routing settings follows familiar older workflows, making it suitable for users accustomed to the classic interface.

Both options target 64-bit Windows. If the device runs current Windows desktop apps normally, start with the Desktop version. If existing tutorials, configuration steps, or habits rely on the WPF interface, the classic WPF version makes menu locations easier to follow.

Apple Silicon version: For devices with Apple M-series chips; the package architecture is marked arm64. This is the native architecture for most newer Macs.

Intel version: For devices that show an Intel processor in About This Mac; the package architecture is marked x64.

After downloading the DMG, open the disk image and complete installation through the system interface. On first launch, macOS may ask you to confirm an application downloaded from the internet. Verify the file source and client name, then continue as prompted. Import subscriptions, choose servers, and configure the system proxy inside the client.

v2rayNG uses the Xray core and lets you manage subscription groups, individual share links, routing rules, and local proxy settings. It offers broad support for common configurations such as VLESS, VMess, Trojan, Shadowsocks, and REALITY, making it a solid default for Android.

arm64-v8a: For mainstream Android phones released after 2015. The package contains only components for the target processor architecture and should generally be preferred.

universal: The universal version supports a wider range of architectures and is usually larger. Use it when the device architecture is unknown, the arm64 package reports incompatibility, or the same installer must be kept for devices with different architectures.

v2flyNG uses the V2Fly core and suits users who need V2Fly configuration semantics, already have matching subscription content, or want to follow V2Fly documentation when configuring routing and transport parameters. The main difference from v2rayNG is the core family, not the installation process.

The architecture guidance is the same as for v2rayNG: choose arm64-v8a first for mainstream devices; use the universal version if the architecture is unknown or installation reports a mismatch.

Most devices need only one primary client. Frequently importing the same subscription into both clients can make connection permissions, background execution policies, and the active configuration difficult to track. When comparing core behavior, record the client and configuration conditions used for each test.

deb: For Debian, Ubuntu, and distributions using the Debian package system. Typical 64-bit desktop PCs use amd64; ARM devices use arm64.

rpm: For Fedora, RHEL, Rocky Linux, AlmaLinux, and distributions using the RPM package system. Typical 64-bit desktop PCs use x86_64; ARM devices use aarch64.

Before installation, run uname -m to check the architecture: choose amd64 deb or x86_64 rpm for x86_64, and arm64 deb or aarch64 rpm for aarch64. The package format must match the distribution’s package system; do not rely on the architecture in the filename alone.