Client Downloads and Installer Selection

V2Ray Client Download

Choose an installer based on the operating system and processor architecture. Use v2rayN on desktop platforms; on Android, choose between v2rayNG and v2flyNG. Version details on this page are updated from the same release list, but confirm the platform, architecture, and package format before downloading.

Free forever Open source Setup guides for four platforms Subscription and routing management

Platform Installers

Choose a client by operating system

Switch platforms to view the fixed client list, primary installer, alternative packages, and minimum requirements. Each tab lists only GUI clients supported on that system.

Windows x64

v2rayN Windows Installers

Windows offers the Desktop and classic WPF editions. Both manage the same types of subscriptions, server profiles, routing rules, and system proxy settings; the main differences are UI technology and workflow.

Recommended

v2rayN

Windows Desktop Client · Current version 7.24.1

The Desktop edition uses a modern cross-platform UI with a structure closer to the macOS and Linux versions. It suits first-time installations and users who want the newer interaction model. The classic WPF edition uses a traditional Windows desktop interface with menu paths familiar from long-running versions. The Desktop edition is generally recommended for a first installation; choose the classic edition if your existing workflow depends on the WPF interface.

Desktop edition

Modern cross-platform UI for Windows x64.

Download Desktop edition

Classic WPF edition

Traditional Windows interface and workflow for established usage habits.

Download classic WPF edition

Windows Requirements and Setup

Item	Requirement	Selection notes
Operating system	Supported 64-bit Windows desktop systems	Keep system components and the runtime environment available and up to date.
Processor architecture	x64	The Windows installers on this page target common 64-bit Intel or AMD processors.
Installation method	Extract, then run the installer	Fully extract the archive before launching its installer.
Initial configuration	Subscription link or individual server configuration	After installation, import a valid configuration; the client does not generate server details automatically.

Close any older instance before installation to prevent configuration files from being written simultaneously. After installation, open Subscription groups, add the subscription URL, and update it. Once the import succeeds, select a profile and set the routing mode and system proxy according to your needs. If the program launches but your browser does not use the proxy as expected, check the system proxy switch before reinstalling.

macOS Desktop

v2rayN macOS Installers

macOS installers are split by chip architecture. Choose arm64 for Apple M-series chips and x64 for Intel processors. The chip type must match the installer.

Recommended

v2rayN

macOS Desktop Client · Current version 7.24.1

The v2rayN macOS edition uses the same configuration-management model as the newer Desktop client, including subscription groups, server profiles, routing rules, and logs. Before downloading, open About This Mac from the system menu and check the Chip or Processor field. Choose Apple Silicon when an Apple M-series name appears, or Intel when an Intel name appears. A mismatched installer commonly fails to open or triggers an architecture-incompatibility warning.

Apple Silicon

For Apple M-series chips with the arm64 architecture.

Download Apple Silicon edition

Intel

For Intel processors with the x64 architecture.

Download Intel edition

macOS Requirements and Setup

Item	Requirement	Selection notes
Operating system	Supported 64-bit macOS	Complete available system maintenance updates before installing the current client.
Apple chip	arm64	Choose the Apple Silicon package when About This Mac shows an Apple M-series chip.
Intel chip	x64	Choose the Intel package when About This Mac shows an Intel processor.
Installation format	DMG	Open the disk image and complete the application installation using the system interface.

On the first launch, the system may ask you to approve network-related permissions. These permissions determine whether the app can create a local proxy and adjust the relevant system settings; they do not replace subscription import. After authorization, add a subscription group, update it, and then select a profile and routing mode. When moving to a device with a different chip architecture, download the matching installer again rather than copying the app from the old device.

Android Mobile

v2rayNG and v2flyNG Installers

v2rayNG is the preferred choice on Android; choose v2flyNG when you need the v2fly core branch. Both clients provide arm64 and universal installers.

Recommended

v2rayNG

Android Client · Xray Core · Current version 2.2.6

v2rayNG is the primary choice for Android, supporting subscription imports, configuration QR-code scanning, server-list management, and routing-mode switching. Most mainstream phones released after 2015 use arm64, so the arm64 build is preferred to reduce installer size. Choose the universal build if the device architecture is unknown, the model is older, or the arm64 package cannot be installed.

arm64 edition

For most newer Android phones and tablets.

Download v2rayNG arm64

Universal edition

For devices with an unknown architecture or broader compatibility requirements.

Download universal v2rayNG

Alternative

v2flyNG

Android Client · v2fly Core · Current version 1.10.31

v2flyNG targets Android use cases that require the v2fly core branch, with configuration management similar to common mobile clients. The choice mainly depends on whether the subscription protocols and server configuration are better suited to the v2fly compatibility path. If no specific core is required, most users should start with v2rayNG above.

arm64 edition

For most modern Android devices, with a more compact installer.

Download v2flyNG arm64

Universal edition

For devices with an unclear architecture or those unable to install the arm64 version.

Download universal v2flyNG

Android Requirements and Setup

Item	Requirement	Selection notes
Processor architecture	arm64 or universal architecture package	Most mainstream devices released after 2015 should start with arm64.
Installation format	APK	Open the downloaded installer using the system installation interface.
Client selection	v2rayNG or v2flyNG	Choose v2rayNG by default; choose v2flyNG when you specifically need its core branch.
First connection	System network connection authorization	When starting a connection, approve the client’s local network connection request if prompted by the system.

After installation, import a subscription link from the clipboard or use the client’s QR-code scanner to import an individual profile. Update the subscription first, then check whether valid entries appear in the server list. The mobile connection switch only indicates that a local network channel has been established; usability also depends on configuration parameters, server status, routing rules, and DNS settings. If a subscription update fails, check the link’s accessibility, the current network, and whether the update request must use an existing proxy.

Linux Desktop

v2rayN Linux Installers

Linux installers vary by distribution package format and processor architecture. Choose deb for Debian-based systems and rpm for RHEL-based systems, then match x64 or arm64 to the device.

Recommended

v2rayN

Linux Desktop Client · Current version 7.24.1

The v2rayN Linux edition provides GUI management for subscriptions, servers, routing, and logs. Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. Common desktop PCs use x64, while ARM-based devices use arm64. Check the package format first, then the architecture, to avoid an installer compatibility error.

deb x64

For common x64 Debian, Ubuntu, and derivative distributions.

Download deb x64

rpm x64

For common x64 Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions.

Download rpm x64

ARM64 installers

Choose the following entry only when the system architecture shows aarch64 or arm64. The package format must still match the distribution.

Download deb arm64 Download rpm arm64

Linux Requirements and Setup

Distribution or device	Package	Architecture selection
Debian, Ubuntu, and derivatives	deb	Choose x64 for standard Intel or AMD desktops and arm64 for ARM devices.
Fedora, Rocky Linux, AlmaLinux, and RHEL-based systems	rpm	Choose x64 for `x86_64` and arm64 for `aarch64`.
Desktop environment	A desktop session capable of running GUI applications	On a minimal server environment, confirm that a graphical desktop and its dependencies are installed first.
Network settings	Desktop system proxy or in-app proxy	After installation, verify through the desktop environment that the system proxy is actually active.

Run uname -m in a terminal to check the architecture: the common output x86_64 corresponds to x64, while aarch64 corresponds to arm64. If the package manager reports missing dependencies, install them from the current distribution’s repositories before retrying. After the client starts, subscription import and profile selection work much like on other desktop versions, but the system proxy entry may vary by desktop environment. If the in-app connection works while the browser does not, check whether the proxy settings were written correctly for the current desktop environment.

Post-install Configuration Paths

From Installer to First Connection

Installing the client is only the preparation step. Subscription import, profile selection, routing mode, and the system proxy together determine whether the app works as expected.

Confirm the platform and architecture

Select the platform tab based on the operating system, then verify the chip or processor architecture. This page offers x64 installers for Windows; macOS is split between Apple Silicon and Intel; Android between arm64 and universal; and Linux between deb, rpm, x64, and arm64. Do not choose based only on the version number in the filename.

Complete the client installation

Install desktop clients with the installer or package manager; on Android, open the APK through the system installation interface. Before upgrading an existing version, exit the running client so its configuration files are not in use. After installation, confirm that the client opens normally before importing a configuration.

Import a subscription or individual profile

Subscription links are useful for centrally managing multiple servers, while individual share links or configurations suit one-off imports. When pasting a subscription URL, remove extra spaces and line breaks and confirm that the link is still valid. After updating the subscription, check that recognizable profiles appear in the client list.

Choose routing and the system proxy

Select a profile, then set the routing mode. For everyday use, start with rule-based routing and change modes only when needed. Desktop clients also require the system proxy to be enabled; the first mobile connection requires system network authorization. After changing routing or DNS, reload the configuration so old settings no longer remain active.

View the complete setup guide Open troubleshooting

How to Choose a Client

Where v2rayN, v2rayNG, and v2flyNG fit

The three names belong to different platforms and core ecosystems. Choose the device platform first, then check protocol compatibility; there is no need to install every client on the same device.

v2rayN: Desktop platforms

v2rayN covers Windows, macOS, and Linux and is the primary desktop client on this page. It provides GUI access to subscription groups, server lists, routing rules, system proxy settings, logs, and core configuration. Windows users can choose between the modern Desktop and classic WPF editions; macOS and Linux users select installers by chip, architecture, and package format.

v2rayNG: Preferred on Android

v2rayNG suits everyday configuration management on Android and uses the Xray core for the relevant protocol and transport settings. It can import subscriptions, share links, and QR codes, then handle proxy traffic through the system network connection mechanism. For mobile users without a specific core requirement, the v2rayNG arm64 edition is usually the best starting point.

v2flyNG: Alternative for the v2fly branch

v2flyNG also targets Android but uses the v2fly core branch. It is better suited to cases where the server configuration, subscription format, or protocol combination has been confirmed to require that branch. Similar client names do not guarantee identical behavior; after switching, recheck subscription parsing, routing rules, and DNS settings.

Version Updates and Configuration Migration

Version updates may change the interface, protocol capabilities, runtime environment, or bug fixes. Before upgrading, note the current subscription groups, routing mode, and system proxy status. If desktop configuration migration is needed, confirm the configuration directory and export function in the old version, then restore it through the import path provided by the new client. Do not edit the same configuration directory while old and new clients are running simultaneously.

When switching from v2rayNG to v2flyNG on Android, or back again, treat it as a client migration rather than a simple overwrite installation. Reimport the subscription and check the entry count, protocol fields, transport parameters, and routing rules. A subscription being importable does not mean every profile in it suits the current core branch.

Download Questions

Installer and First-Use FAQ

These questions cover the most common decision points involving platform architecture, package format, and initial configuration.

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

The Desktop edition uses a modern cross-platform interface and suits first-time installations, users who want the newer workflow, or anyone seeking a similar experience across macOS and Linux. The classic WPF edition is built on native Windows desktop technology, with menu paths closer to the traditional version maintained over time, and suits users already familiar with that interface.

Both target Windows x64 and support subscription, configuration, routing, and system proxy management. Without an established preference, choose the Desktop edition; choose the classic edition when an existing workflow depends on WPF menu locations.

How do I choose between the Apple Silicon and Intel installer on macOS?

Open About This Mac from the system menu and check the Chip or Processor field. Choose the Apple Silicon arm64 build when an Apple M-series chip is shown, or the Intel x64 build when an Intel processor is shown. The wrong architecture will usually stop the installer from launching or cause the system to report that the app is incompatible with the device.

Should Android users download the arm64 or universal build?

Most mainstream Android phones released after 2015 use arm64, so the arm64 build is preferred. It includes only the components required for that architecture and is usually smaller. Use the universal build if the device architecture is unknown, the device is older, or the arm64 build cannot be installed.

The architecture choice does not change subscription contents or the main workflow; it only determines whether the installer matches the processor. If the arm64 build is already installed successfully, there is no need to install the universal build as well.

Should Linux users choose a deb or rpm package?

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. After identifying the format, check the processor architecture. If uname -m shows x86_64, choose x64; if it shows aarch64, choose arm64.

Package format and processor architecture are independent requirements. Even with the correct deb or rpm package, the wrong architecture will still cause installation to fail.

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

The client only manages configuration, routing, and the system proxy. After the first launch, import a valid subscription link or individual server configuration, update the subscription, select an available profile, and enable the system proxy or mobile network connection for your use case.

If the client is running but apps cannot connect as expected, check in order whether the subscription parsed successfully, the selected profile works, the routing mode is appropriate, the system proxy is active, and the DNS settings match. See the troubleshooting page for the complete diagnostic process.