CLIENT PACKAGES / STABLE CHANNEL

V2Ray client downloads and installer selection

Choose a client based on the operating system, processor architecture, and interface type. Use v2rayN on desktop platforms; on Android, choose between v2rayNG and v2flyNG based on the kernel ecosystem.

Stable release v2rayN 7.24.1 v2rayNG 2.2.6 v2flyNG 1.10.31
package selector ready
  1. 01
    Confirm the operating system

    Start by opening the matching panel from the four platform tabs below.

  2. 02
    Determine the processor architecture

    For desktop devices, distinguish between x86_64 and arm64; on Android, check arm64 compatibility first.

  3. 03
    Download and complete the installation

    Close the running older version, keep a configuration backup, then install or upgrade.

PLATFORM REGISTRY

Choose a client by platform

The platform tab is reflected in the address bar. Copy the page address with its platform marker to open the corresponding download panel directly.

platform: windows / arch: x86_64

Windows：v2rayN

Desktop clients

Windows offers Desktop and classic WPF interface versions. Desktop is the next-generation cross-platform UI, with an organization suited to new installations and use across desktop systems. WPF retains the classic Windows layout, with menus, configuration editing, and tray controls closer to established workflows. Both target 64-bit Windows. Quit the old client before installation to prevent its local listening port from remaining occupied.

v2rayN
Recommended

v2rayN

7.24.1

The Desktop and WPF versions use different interface technologies. For a first installation, Desktop is the preferred choice. If upgrading from the classic version and keeping the existing workflow matters, continue using WPF.

Desktop edition Next-generation cross-platform interface, ideal for first-time installation.
Download Desktop edition
Classic WPF edition Classic Windows interface, ideal for keeping the existing workflow.
Download classic WPF edition

Windows system requirements and selection criteria

Check Recommendation Action
Processor architecture 64-bit x86 processor Confirm x64 under System type in System Information.
Interface version Prefer Desktop for a new installation If you are familiar with the classic menus, choose WPF, and avoid launching both versions at once.
Upgrade preparation Quit the old client from the system tray Back up subscriptions, routing rules, and local settings before installing.
First connection Check the system proxy status Import the configuration and choose a node before enabling proxy mode for the required scope.

INSTALLATION NOTES

Four checks before installation

Whether the installer works correctly mainly depends on the platform, architecture, configuration source, and system proxy status. Complete these checks first to reduce repeated installations and overwritten settings.

01 / PLATFORM

Platform and package format

Use the corresponding desktop installer on Windows, dmg on macOS, apk on Android, and deb or rpm on Linux according to the distribution. If the file format does not match, the system cannot install it through the normal package workflow. Linux users should also identify the distribution's package-management system rather than relying only on the desktop environment name.

02 / ARCH

Processor architecture

Architecture determines which machine instructions the program contains. Apple Silicon on macOS uses arm64 and Intel uses x64; most recent mainstream Android devices use arm64; common Linux desktop computers use x86_64, while ARM devices show arm64 or aarch64. A mismatch usually appears as an installation failure, an immediate exit after launch, or a system format error.

03 / BACKUP

Configuration and subscription backups

Before upgrading, record the current client version, subscription groups, routing mode, listening port, and system proxy status. Client settings may include manually added nodes, bypass rules, and custom DNS settings, which are harder to recreate than the program itself. When switching interface versions, save separate restorable configuration copies.

04 / RUNTIME

Running state and ports

Before installing, fully quit the old client from the tray or application menu; closing the main window may leave a background process running. If the connection fails after upgrading, first check whether the old process still occupies the local proxy port, then confirm that the new client has selected the correct node and that system proxy or TUN is enabled as expected.

CLIENT SCOPE

Boundaries of the three clients

The client names are similar, but their platform coverage, kernel ecosystems, and interface focus differ. Choose the operating system first, then check configuration compatibility; there is no need to install every client on the same device.

v2rayN
v2rayN desktop

For Windows, macOS, and Linux desktop systems. Core tasks include subscription management, node selection, routing rules, system proxy, TUN, and configuration editing. Windows offers Desktop and classic WPF interfaces, while macOS and Linux require an installer selected by architecture or package format. Desktop users generally need only this client.

v2rayNG
v2rayNG android / xray

The usual choice for Android, built around the Xray kernel ecosystem. It can manage multiple nodes through a subscription URL and directly import vmess and vless share links. Connections use the system VPN interface, so the required permission must be approved on first launch. Background stability is also affected by battery policies and app sleep settings.

v2flyNG
v2flyNG android / v2fly

The v2fly-kernel client for Android, suited to subscriptions or manual configurations that explicitly depend on v2fly behavior. Before choosing it, review the provider's notes on protocols, transports, and kernels. Without a specific compatibility requirement, start with v2rayNG; before switching, disconnect the current client's VPN connection.

DOWNLOAD FAQ

Common download and installation questions

These questions cover versions, architectures, package formats, and first connections. For complete instructions on importing configurations and routing modes, see the Getting Started guide.

Should Windows users download v2rayN Desktop or the WPF version?

Desktop uses a next-generation cross-platform interface and suits first-time installations or users who want similar layouts across Windows, macOS, and Linux. WPF retains the classic Windows interface, with menu organization, tray access, and settings paths closer to earlier versions. If you have used WPF for a long time and its configuration is stable, you can stay with the classic version; for a new installation, Desktop is usually the better choice. They may use the same local proxy port, so do not run both simultaneously.

How do I tell whether a Mac uses Apple Silicon or Intel?

Open the system menu in the upper-left corner of the screen, select About This Mac, and check the Chip or Processor field. If it shows an Apple M-series chip, download the Apple Silicon arm64 package; if it shows Intel, download the Intel x64 package. Do not guess from the model or purchase date, as similarly designed devices may use different processors. A mismatched installer architecture usually prevents the app from launching correctly.

Should Android users choose arm64 or the universal version?

Most mainstream Android phones released after 2015 can use arm64 first; the file contains only the content needed for the target architecture. If the processor architecture cannot be confirmed from device information, or the arm64 package reports incompatibility during installation, use the universal version. The universal version supports a broader range of devices, but its client role is the same as the arm64 version. When choosing v2rayNG or v2flyNG, also confirm that the subscription matches the relevant kernel ecosystem.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and derivatives generally use deb; Fedora, RHEL, and derivatives generally use rpm. After choosing the format, determine the processor as well: common desktop computers are usually x86_64, while ARM desktop devices or development boards may show arm64 or aarch64. Package format and processor architecture are independent requirements; choosing either one incorrectly can cause installation failure.

Do I need to remove the old version before installing a new one?

Most upgrades within the same client type can be performed directly, but first fully quit the old client and back up subscriptions, nodes, routing, and DNS settings. When switching from WPF to Desktop on Windows, changing package systems on Linux, or moving between desktop systems, treat the configuration as separate data rather than assuming every setting will migrate automatically. After upgrading, check subscription groups and the local listening port before enabling the system proxy.

Why can't I connect immediately after downloading the client?

The installer contains only the client program. After installation, import a valid subscription URL or node share link, update the subscription, choose an available node, and enable system proxy or TUN for your use case. If the client reports a connection but apps cannot access the network, check the node configuration, system time, local port, proxy mode, and routing rules in order instead of reinstalling the client.

Next: import a subscription and choose a proxy mode

After downloading and installing the appropriate client, finish importing a subscription, choosing a node, configuring the system proxy, and verifying the connection.

View Getting Started Open the Complete Installation Guide