CLIENT PACKAGES · GUI

V2Ray Client Download and Platform Selection

Get v2rayN, v2rayNG, and v2flyNG installers for your operating system and processor architecture. Use v2rayN on desktop platforms, or choose between two core options on Android.

4 platforms 3 GUI clients Free forever Open source

PLATFORM MATRIX

Choose an operating system

Platform labels are reflected in the page URL. After switching, confirm the processor architecture and package format before downloading the matching installer.

WINDOWS · X64

Windows client

v2rayN offers Desktop and classic WPF interfaces. Both are GUI clients, but their configuration data and feature layouts differ.

v2rayN

v2rayN

Windows desktop GUI client

Recommended Release 7.24.1

The Desktop version offers a newer cross-platform UI for fresh installations and users who want a consistent desktop interface. The WPF version retains the classic Windows UI and usually matches menu paths in existing tutorials more closely. Both versions target x64 processors; installing both is unnecessary.

Recommended choice

Desktop edition

A newer cross-platform UI suited to first-time installations. The archive includes an installer; extract it, then run the installer.

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download Desktop version
Classic interface

WPF version

The classic Windows UI suits users who prefer familiar workflows or need to match the interface used in traditional v2rayN tutorials.

v2rayN-Setup-x64-7.24.1.zip

Download WPF version

Windows system requirements and installation guide

Check Requirement Selection guidance
Processor architecture x64 Supports common 64-bit Intel and AMD desktop processors.
Software format Desktop / WPF Desktop provides the newer interface, while WPF provides the classic one; Desktop is preferred for first-time users.
Before running Allow the current user to write to the configuration directory Extract the archive to a fixed directory before launching. Do not run the program from the archive preview window.

SELECTION LOGIC

Package selection order

Identify the platform first, then the processor architecture, and finally the package format. Do not guess from the filename length, file size, or device appearance.

01

Confirm the operating system

Use v2rayN on Windows, macOS, and Linux. On Android, start with v2rayNG; use v2flyNG when you specifically need the v2fly core route. Packages for different platforms cannot be installed interchangeably.

02

Confirm the processor architecture

The current Windows entry targets x64. On macOS, choose based on an Apple M-series chip or Intel processor. Most mainstream Android devices use arm64. Linux requires choosing between x64 and arm64.

03

Confirm the package format

macOS uses dmg, and Android uses apk. On Linux, deb and rpm correspond to different distribution families. The two Windows archives represent different interface routes, not processor architectures.

04

Complete the initial configuration

After installation, import a subscription or enter the server parameters manually, select a valid node, and start the connection. Configure the system proxy, routing mode, and DNS settings according to the network environment.

FIRST RUN

First checks after installation

If the client opens, the program has started successfully—but that does not confirm a usable connection. Availability also depends on the subscription, node parameters, system time, proxy mode, and local network. Keep the default routing settings initially, import the subscription, select a node, start the connection, and review the client log. Once the basic connection works, adjust routing, DNS, or TUN mode. This makes troubleshooting easier by avoiding several simultaneous configuration changes.

View setup guide Open troubleshooting handbook
first-run.checklist
  1. Launch the GUI client
  2. Import a subscription or configuration
  3. Select a valid node
  4. Start the connection
  5. Enable the system proxy if needed
  6. Review the log to confirm status

UPDATE RULE

Updates and configuration retention

Before updating the client, exit any running process and record the current subscription, routing mode, and custom settings. If the desktop client runs from an extracted directory, do not mix new files into an old directory from an unknown source. When updating on Android, confirm that the installation follows the same client route. After upgrading, check the subscription list and core settings before reconnecting. If something goes wrong, distinguish between a client update issue, a subscription update issue, and a problem with the node itself instead of resetting everything at once.

update.sequence 
stop connection
record current mode
exit client
install update
open client
check subscription
test one node

DOWNLOAD FAQ

Common download and installation issues

These questions focus on installer variants, architecture selection, and first launch. For connection timeouts, subscription failures, and DNS issues, see the troubleshooting handbook.

Should Windows users choose v2rayN Desktop or the WPF version?
The Desktop version uses a newer cross-platform interface and suits users who want a modern UI and a consistent desktop experience. The WPF version is the classic Windows client, with menus that map more directly to existing tutorials. Both target Windows x64; for a first installation, Desktop is preferred, and installing both is unnecessary.
How do you tell Apple Silicon from Intel on macOS?
Open About This Mac from the system menu and check the chip or processor field. Choose the Apple Silicon installer for an Apple M-series chip and the Intel installer when Intel is shown. Do not rely only on the device's year or appearance.
Should Android users download arm64 or the universal build?
Most mainstream Android phones released after 2015 use arm64, so start with the arm64 installer. If the architecture is unknown or the system explicitly reports incompatibility, switch to the universal build. It supports more architectures and is usually larger.
Should Linux users choose deb or rpm?
Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based systems, and distributions using RPM package management. Run uname -m to confirm the architecture: x86_64 maps to x64, and aarch64 maps to arm64.
Why can't I connect immediately after installing the client?
The client manages configuration, routing, and the system proxy, but installation alone is not enough. Import a valid subscription or enter the server parameters manually, then select a node, start the connection, and enable the system proxy if needed. If network access still fails, check the system time, subscription status, node parameters, and client log.
How should you choose between v2rayNG and v2flyNG?
On Android, v2rayNG with the Xray core is usually the first choice. Choose v2flyNG when you need the v2fly core ecosystem or compatibility with a specific configuration. The two apps keep separate subscriptions, routes, and local settings, so review the configuration again after switching.