Four-platform client packages

V2Ray Client Downloads and package selection

Choose a package based on your operating system, processor architecture, and interface needs. Use v2rayN on desktop systems; on Android, choose between v2rayNG and v2flyNG according to the kernel family.

Free forever Open source Graphical interface Chinese configuration guides
Selection order

Choose the platform first, then check the architecture and package format

The x64, arm64, and universal labels in package names indicate different processors or compatibility ranges. Desktop systems also distinguish interface editions and package formats. If you are unsure, do not rely on the filename alone: check the processor type in system information and compare it with this guide.

  1. Confirm the systemWindows, macOS, Android, or Linux
  2. Confirm the architecturex86_64, Apple Silicon, arm64, or universal
  3. Choose a clientInstall it after downloading, then import a subscription or server configuration
Platform packages

Choose a client by operating system

The four platforms below list the applicable client, primary package, and alternative package. Switching tabs updates the page address, so you can copy the current URL and return directly to that platform.

Windows

v2rayN for Windows

Windows offers the Desktop and classic WPF editions. Both serve the same client purpose, but their interface technology and layout differ. For a first installation, download the Desktop edition; choose WPF if you have used the classic interface for a long time or need to retain an established configuration workflow.

Recommended

v2rayN

64-bit graphical client for Windows. The Desktop edition uses a modern cross-platform UI, while the classic WPF edition retains a mature Windows layout. Install either one; both are not required.

7.24.1
Desktop edition

Best for first-time installations and users who want the modern interface; it is the preferred choice on this site.

v2rayN-Desktop-Setup-x64-7.24.1.zip
Download the Desktop edition
Classic WPF edition

Best for users familiar with the legacy menu structure who want to continue using the classic Windows interface.

v2rayN-Setup-x64-7.24.1.zip
Download the WPF edition

Windows requirements and installation

Check Recommendation
System Use a 64-bit Windows 10 or Windows 11 release that is still supported by Microsoft, and install the required system updates.
Processor The Windows packages on this page target x64 processors. Confirm this under System type in Windows Settings.
Installation method Extract the downloaded archive to a fixed directory, then run the installer or launcher inside it. Do not run the program from the archive preview window.
Initial setup After launching, import a subscription or server configuration, select a node, and configure system proxy or TUN mode for your intended scope of use.

The package handles client deployment; establishing a connection still requires importing a subscription, selecting a node, and configuring the proxy mode.

Three configuration steps after downloading

After installation, obtain a valid subscription link or server parameters from your service provider and import them into the client. Then update the subscription group and select a configuration for a real connection test. Finally, choose system proxy or TUN mode based on whether the apps you use follow system proxy settings. If a webpage will not open, check the runtime logs and system time first, then inspect DNS and routing rules instead of repeatedly changing packages.

View the setup guide Read the full documentation
Subscription group Manually update the group after adding a link Update
System proxy Let apps that follow system settings use the client
Log level Keep the necessary details when troubleshooting connections warning
How to choose

Client, architecture, and package format

The model name, processor architecture, and package format describe different layers. Assessing them separately is more reliable than looking only at the filename.

01

The client model determines the interface and kernel family

v2rayN targets Windows, macOS, and Linux desktop environments; v2rayNG and v2flyNG target Android. v2rayNG uses the Xray kernel, while v2flyNG uses the V2Fly kernel. For ordinary installations, follow the recommended order on this page; compare kernel differences only when the configuration source explicitly requires specific kernel behavior.

02

Processor architecture determines whether the program can run

x64 or x86_64 is typically used by mainstream Intel and AMD desktop processors; arm64 is used by Apple M-series chips, modern Android devices, and some ARM Linux devices. The Android universal edition covers a broader combination of processors. A wrong architecture commonly causes installation failure, package parsing errors, or failure to launch.

03

The file format determines how the system installs it

DMG is a common macOS installation image, APK is used to install Android apps, and deb and rpm correspond to different Linux package systems. The Windows page provides compressed installation files, which should be fully extracted to a fixed directory after downloading. Formats cannot be mixed across systems or converted by changing the file extension.

04

Distinguish program issues from configuration issues before updating the client

When the client launches but cannot connect, check the subscription, node parameters, system time, DNS, routing, and proxy mode. Update the client first only when it cannot launch, features are missing, or the current version no longer supports the system. Recording the specific log error first can prevent aimless reinstalls.

Common download questions

Package selection and first-time installation

These questions focus on how versions, architectures, package formats, and post-install configuration relate to one another.

Should Windows users download the v2rayN Desktop edition or the classic WPF edition?

For a first installation, the Desktop edition is preferred because it uses a modern cross-platform interface and makes it easier to maintain consistent habits across desktop systems. Choose WPF if you know the classic menus and want to keep the familiar workflow. Both editions target 64-bit Windows; installing both is unnecessary and does not improve connection performance.

How do you choose between the Apple Silicon and Intel package on macOS?

Open About This Mac from the system menu and check the chip or processor field. Choose Apple Silicon for an Apple M-series chip and the Intel package for an Intel processor. Do not decide by appearance or purchase year alone, since similar models may use different processors. After downloading the correct architecture, follow the DMG window instructions to install it.

What is the difference between Android arm64 and universal packages?

The arm64 package contains components for 64-bit ARM devices and suits most modern phones. The universal package supports a wider range of architectures and is useful when the processor type is unknown. Most mainstream phones released after 2015 should use arm64 first. If Android reports that the package is incompatible, switch to universal rather than installing both variants.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and derivatives use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. After choosing the format, confirm the architecture: uname -m returns x86_64 for x86_64, and aarch64 or arm64 for arm64.

Why can't a connection be established immediately after installing the client?

The client package contains only the graphical application and runtime components, not a ready-to-use server configuration. After installation, import a valid subscription or add server parameters manually, update the subscription group, select a node, and enable system proxy or TUN mode as needed. After connecting, check the client logs, browser access, and terminal requests separately to confirm that traffic follows the expected path.