CLIENT PACKAGE INDEX
Choose a graphical client for your operating system. Use v2rayN on desktop systems, and choose between v2rayNG and v2flyNG on Android. Confirm the processor architecture and installer type before downloading.
PLATFORM PACKAGES
The tabs are reflected in the page URL. Copy a URL with a platform identifier to open the corresponding download section directly.
WINDOWS PACKAGE
Two interface editions are available: Desktop and classic WPF. Choose Desktop for a first installation; if you are accustomed to the WPF workflow, you can continue using the classic edition.
Current version 7.24.1
Windows desktop graphical client. Supports subscription import, server management, system proxy settings, routing rules, TUN mode, and runtime log viewing. Both entries belong to the same client family; the main differences are the interface technology and layout.
| Check | Recommendation | How to check |
|---|---|---|
| Processor architecture | x64 | Go to “Settings → System → About” and check the system type. This page provides a 64-bit desktop installer. |
| Interface edition | Desktop is recommended for new users | Choose Desktop for the newer cross-platform interface; choose WPF if you are familiar with the classic menus. |
| Installation permissions | Allow installation for the current user | The installer needs to write to the application directory. Managed devices may require administrator approval. |
MACOS PACKAGE
The two installers target different processor architectures. Choose Apple Silicon for M-series chips and the Intel version for Intel processors.
Current version 7.24.1
macOS desktop client. Check the chip type before downloading and installing. Choosing the wrong architecture may result in an installer that will not open, an app that will not launch, or a compatibility warning from the system.
| Check | Choose | How to check |
|---|---|---|
| Apple M-series chip | Apple Silicon | Open “About This Mac” and check the chip field for an Apple M-series model. |
| Intel processor | Intel | Open “About This Mac” and check the processor field for an Intel model. |
| First launch | Confirm system permissions | Follow the system prompts to launch the app and configure network-related permissions, then import your subscription. |
ANDROID PACKAGES
Start with v2rayNG in most cases. Choose v2flyNG when you need a v2fly core compatibility path. Mainstream phones released after 2015 generally use arm64.
Current version 2.2.6
Android graphical client built on the Xray core. Supports QR scanning, clipboard import, subscription updates, per-app proxying, routing settings, and connection logs. Most newer devices should use the arm64 package.
Current version 1.10.31
Android client built on the v2fly core. Suitable for users who need V2Fly configuration compatibility, already use the corresponding configuration workflow, or need consistency with other V2Fly environments.
| Check | Recommendation | Details |
|---|---|---|
| Client edition | v2rayNG is usually the first choice | v2rayNG uses the Xray core; choose v2flyNG when you need a v2fly core compatibility path. |
| Processor architecture | Choose arm64 for mainstream devices | Mainstream phones and tablets released after 2015 generally use 64-bit ARM processors. |
| Architecture unknown | Choose the universal edition | The universal edition contains components for more architectures. It is larger but supports a wider range of devices. |
LINUX PACKAGES
Choose deb or rpm according to the distribution's package-management system, then choose x64 or arm64 based on the processor.
Current version 7.24.1
Linux desktop graphical client. x64 is common on desktop computers; arm64 is common on ARM workstations, development boards, and some lightweight desktop devices. The package format and processor architecture must both match.
| Distribution or device | Package format | Architecture |
|---|---|---|
| Debian, Ubuntu, and related derivatives | deb | Choose x64 for standard Intel or AMD desktops, and arm64 for ARM devices. |
| Fedora, Rocky Linux, AlmaLinux, and others | rpm | Choose x64 for standard Intel or AMD desktops, and arm64 for ARM devices. |
| Confirm the architecture | Independent of the system package manager | Run uname -m in a terminal. Choose x64 for x86_64 and arm64 for aarch64. |
PACKAGE DECISION
Platform, client edition, processor architecture, and package format are four separate dimensions. Check them in order to avoid downloading a package that cannot be installed.
Windows, macOS, Android, and Linux use different installation formats and cannot be installed across platforms. The platform tabs at the top group downloads by system. Open the tab for the current device instead of guessing from similar-looking filenames.
Desktop systems use v2rayN. Android defaults to v2rayNG; choose v2flyNG when you need a v2fly core configuration compatibility path. The client edition affects the core family, configuration compatibility, and some feature locations, while subscription import, server selection, and connection workflows are broadly similar.
x64, arm64, and universal describe the machine instructions included in the program. A mismatched architecture usually prevents installation or launch. Newer Android devices generally use arm64; macOS requires a choice between Apple M-series and Intel processors; Linux architecture can be checked in system information or with a terminal command.
Linux deb and rpm packages belong to different package-management systems. Windows Desktop and WPF differ in interface implementation, not processor architecture. Choose Desktop for a first Windows installation, or WPF to keep the classic workflow.
AFTER DOWNLOAD
Installing the client does not establish a connection by itself. You still need to import server information, choose a running mode, and check the connection status.
Complete the installation for your system. Fully extract a Windows compressed package before running its installer; open the macOS disk image and follow the system workflow; open the Android package for the matching architecture; use your Linux distribution's package manager to install the deb or rpm file.
On first launch, the system may ask for permission related to networking, notifications, background execution, or virtual network interfaces. Enable only permissions required by the features you use. If you plan to use TUN mode, also allow the client to create a virtual network interface.
Copy a valid subscription URL, create a subscription in the client's subscription management section, and run an update. You can also import an individual server through a QR code, clipboard content, or manually entered parameters. After importing, check that the server list appears and that the protocol, address, port, and transport settings are complete.
The subscription URL and server configuration come from the service provider; the client installer does not contain connection information. If the list is empty after an update, first check that the URL is complete and its response is accessible, then confirm that the client version supports the subscription format.
Select the server to use, then configure the system proxy, routing rules, or TUN mode according to the scope of applications. The system proxy suits programs that follow the operating system's proxy settings; TUN mode captures more traffic through a virtual network interface but needs additional permissions and may conflict with other network tools.
For an initial test, use the client's default routing settings and adjust custom rules only after the basic connection works. When rules involve domains, IP addresses, processes, and inbound types, change one condition at a time and watch the logs instead of changing everything at once.
After starting the connection, check the client status and core logs. A normal startup usually shows configuration loading, the listening port, and runtime status. If the client exits immediately, start with the first error in the log. Port conflicts, incompatible configuration fields, malformed subscription content, and insufficient system permissions are common causes.
Latency tests reflect only a specific test path and do not equal actual download speed. To assess whether the connection works, combine a real connection test, actual webpage access, and log results rather than relying on one number. For detailed steps, continue with the quick-start guide and protocol and core technical reference.
DOWNLOAD FAQ
These questions cover versions, architectures, installation formats, and initial configuration. Expand an item to see how to determine the right choice.
Desktop is the next-generation cross-platform interface for users who want a consistent desktop experience; WPF is the classic Windows interface for users who prefer the familiar workflow. Both are v2rayN editions and serve the same core purpose for subscriptions and server configurations. Choose Desktop for a first installation, or WPF if you already follow a fixed workflow.
Open “About This Mac” or System Information and check the chip or processor field. Choose Apple Silicon for an Apple M-series chip, or the Intel version for an Intel processor. The installer architecture must match the device processor. If you chose incorrectly, delete the incomplete installer files and download the matching version.
The arm64 installer contains only commonly used 64-bit ARM components, so it is smaller and suits mainstream Android phones and tablets released after 2015. The universal edition includes components for multiple architectures, supports more devices, and is usually larger. Choose it when the processor architecture is unknown or the system reports the arm64 build as incompatible.
Debian, Ubuntu, and derivatives generally use deb packages; Fedora, Rocky Linux, AlmaLinux, and similar distributions generally use rpm. After confirming the package format, choose x64 or arm64 for the processor. Run uname -m to check: x86_64 corresponds to x64 and aarch64 to arm64.
After installing the client, import a valid subscription or add a server configuration manually. Then select a server, configure the system proxy or routing mode, and start the connection. The installer contains only the client and no server configuration. If no server list appears after importing, check the subscription URL, response format, client version, and network reachability.
Android users generally start with v2rayNG, which uses the Xray core. Choose v2flyNG when you need the v2fly core or its configuration compatibility path. Both provide subscriptions, server management, and connection features, but core families, protocol extensions, and supported configuration fields may differ. When an existing configuration requires a specific core family, follow its documentation.