CLIENT PACKAGES / GUI

V2Ray Client Downloads and Platform Selection

Choose an installer based on your operating system and processor architecture. Desktop platforms use v2rayN, Android users should generally choose v2rayNG, and v2flyNG is available when the V2Fly core is required.

Free forever Open source Chinese documentation Four platforms

View the subscription import guide →

package.select

01 Platform Windows / macOS / Android / Linux

02 Processor architecture x64 / arm64 / universal

03 Install and import Installer → Subscription → Server → Connect

GUI CLIENTS · XRAY / V2FLY FAMILY

PLATFORM SELECTOR

Choose an installer by platform

Confirm the operating system first, then verify the processor architecture. Switching platforms updates the page URL, so reopening the link takes you directly back to the corresponding download section.

WINDOWS PACKAGES

Windows：v2rayN

Windows offers two x64 installers: Desktop and WPF. Both support subscription management, server selection, system proxy, and routing configuration; the main difference is the UI technology and operating style. Choose Desktop for a first experience with the newer client, or WPF if you prefer the classic Windows interface.

v2rayN

Current version 7.24.1

Recommended

v2rayN is a graphical desktop client with bulk subscription updates, server filtering, latency testing, routing rules, DNS settings, and TUN mode. After installation, you still need to import a valid subscription or server configuration; the client does not include servers.

Desktop Edition Next-generation cross-platform UI for first-time installations and the latest interface.

Download the Desktop x64 installer

Classic WPF Edition Classic, stable interface for Windows users familiar with the older layout.

Download the WPF x64 installer

Windows Requirements and Edition Selection

Item	Recommendation	Details
Processor	x64	Both Windows installers provided on this page are x64 versions.
Interface	Desktop first	Desktop uses the next-generation cross-platform interface; WPF retains the classic Windows workflow.
Installation permissions	Allow writing to the application directory	If the installer will not start, check system permissions and security prompts, then run the installer again.

MACOS PACKAGES

macOS：v2rayN

macOS installers are split between Apple Silicon and Intel. Before installing, check the Chip or Processor field in About This Mac. Choosing the wrong architecture may prevent the installer from opening or require an additional compatibility layer to run.

v2rayN

Current version 7.24.1

Recommended

The macOS version of v2rayN follows the same desktop configuration workflow: manage subscriptions, switch servers, configure the system proxy, and edit routing rules. Matching the chip architecture is the key installation step; the app’s features do not change between installer architectures.

Apple Silicon For devices whose system information shows an Apple M-series chip.

Download the Apple Silicon installer

Intel For devices whose system information explicitly shows an Intel processor.

Download the Intel installer

macOS Chip Detection and Installation

Check	Displayed value	Matching installer
Chip	Apple M-series	Apple Silicon
Processor	Intel	Intel
Installation format	DMG	After opening the disk image, move the app to the Applications folder, then launch it from there.

ANDROID PACKAGES

Android: v2rayNG and v2flyNG

The Android section lists v2rayNG followed by v2flyNG. Start with v2rayNG in most cases; choose v2flyNG when you need the V2Fly core, want to test subscription compatibility, or need to follow an existing configuration workflow. Both clients provide arm64 and universal installers.

v2rayNG

Current version 2.2.6

Recommended

v2rayNG is a graphical Android client built on the Xray core. It supports QR-code scanning, clipboard link import, subscription groups, routing modes, per-app proxy rules, and local DNS settings. Most mainstream phones released after 2015 should use arm64 for a closer architecture match.

arm64 Edition Recommended for mainstream Android phones released after 2015.

Download v2rayNG arm64

Universal Edition Use when the processor architecture is unknown, the device is older, or arm64 cannot be installed.

Download the v2rayNG universal version

v2flyNG

Current version 1.10.31

Alternative

v2flyNG uses the V2Fly core and is suited to existing V2Fly configurations, comparing behavior across cores, or subscription services that explicitly document V2Fly usage. Its import and connection flow is similar to common Android clients, but supported protocols should follow the current configuration requirements.

arm64 Edition For mainstream Android devices with 64-bit ARM processors.

Download v2flyNG arm64

Universal Edition For unknown architectures or situations requiring broader device compatibility.

Download the v2flyNG universal version

Choosing an Android Installer

Scenario	Recommended installer	Approach
Recent mainstream phones	arm64	Prefer the arm64 version of the selected client.
Architecture unknown	Universal version	Try the universal version first to avoid installation failure caused by an architecture mismatch.
Updating an existing app	The same client	Confirm that the app name matches, and save the subscription URL and important settings before updating.

LINUX PACKAGES

Linux：v2rayN

A Linux installer must match both the distribution’s package system and the processor architecture. Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based systems, and distributions using RPM package management. Standard desktop computers are usually x64, while ARM devices use arm64.

v2rayN

Current version 7.24.1

Recommended

The Linux version of v2rayN provides a graphical desktop interface for managing subscriptions, testing servers, switching the system proxy, and maintaining routing configuration. Before downloading, confirm the package format in your distribution’s software documentation, then check the processor architecture through system settings or a command.

deb · x64 x64 desktop devices running Debian, Ubuntu, or derivatives.

Download the x64 deb installer

rpm · x64 x64 systems using Fedora, RHEL, or RPM package management.

Download the x64 rpm installer

arm64 Installer For devices with 64-bit ARM processors; the package format must still match the distribution.

arm64 deb arm64 rpm

Linux Package Formats and Architectures

System type	Package format	Architecture identifier
Debian and Ubuntu family	deb	x64 corresponds to amd64; 64-bit ARM corresponds to arm64.
Fedora and RHEL family	rpm	x64 corresponds to x86_64; 64-bit ARM corresponds to aarch64.
Other distributions	Confirm the package management system first	Do not identify the package solely by the desktop environment; check the distribution’s package documentation.

SELECTION CHECKLIST

Verify three items before downloading

The client name, installer architecture, and subscription configuration are three separate layers. Confirm them in order to reduce the chance of startup or connection failures after installation.

Choose the client

Choose v2rayN for Windows, macOS, and Linux. Android users should generally choose v2rayNG; switch to v2flyNG only when configuration requirements, core preferences, or compatibility testing specifically point to V2Fly. Clients differ in configuration entry points and core capabilities, so keep the product name consistent when updating.

Match the architecture

Desktop devices require a choice between x64 and arm64; macOS also requires a direct match for Apple Silicon or Intel. If the Android architecture is unknown, use the universal version. Architecture determines whether the processor can run the installer, not its feature level, and should not be inferred from file size.

Prepare a subscription

Installers contain only the client program. On first launch, import a valid subscription URL, individual server link, or configuration file, then update the server list. After importing, select a server, start the connection, and use an actual web visit and the client logs to verify the configuration.

INSTALL NOTES

Install, upgrade, and make the first connection

Downloading the installer is only the first step. Keeping the existing configuration, updating the subscription, choosing a routing mode, and checking the system proxy determine whether the client works as expected.

First installation

Close any running client with the same name before launching the installer. When a desktop system requests permission, verify the app name and the action being performed. After Android installation, launch the client from the app list instead of repeatedly tapping the installer file. Linux users should use package tools that match their distribution for deb or rpm.

After opening the client, go to subscription management or the import entry point. When pasting a subscription URL, ensure it has no leading or trailing spaces; for QR imports, confirm that the scanned content is a server configuration or subscription. If the list is empty after updating, check the subscription URL first instead of repeatedly reinstalling the client.

In-place upgrade

Before upgrading, record the subscription URL, group names, routing mode, DNS settings, and custom outbounds. In most cases, you can install the new version directly, but major versions may change the configuration structure or interface locations. After upgrading, do not check only whether the program starts; also verify that the subscription remains, the intended server is selected, and the system proxy is in the expected state.

If configuration loading fails after an upgrade, exit the client and confirm that the old configuration directory still exists. When restoring configuration, avoid combining and overwriting files from different periods, as old fields may affect the new version’s behavior.

CONNECT.SEQUENCE Subscription → Update → Server → Mode → Connect → Verify

Import a subscription: Add and save the URL through the client’s subscription management entry point. Name it according to its purpose or service source.
Update the list: Run a subscription update and confirm that server entries actually appear in the main list. If the update fails, check the URL’s validity period, network status, and update method.
Choose a server: Select a server first, then start the connection. Latency results are only a screening aid; verify actual availability with a connection test.
Set the mode: Choose the system proxy, TUN, or another takeover method provided by the client as needed, and verify that the routing rules match the current scenario.
Verify the connection: Visit a commonly used site and review the client logs. If only certain domains fail, continue checking DNS, routing matches, and rule data instead of immediately changing the installer.

View the complete usage guide Open the advanced setup manual

DOWNLOAD FAQ

Common Download and Installation Questions

These questions cover version selection, processor architecture, package formats, and first launch. Complete instructions for subscriptions, routing, and DNS are available in the usage guide and advanced manual.

Should Windows users choose v2rayN Desktop or the WPF version?

Desktop is the next-generation cross-platform interface for first-time installations, users who want the newer layout, or anyone seeking a similar workflow across desktop systems. WPF is the classic, stable Windows edition for users familiar with the traditional v2rayN interface and menu layout. Both manage subscriptions, servers, the system proxy, and routing configuration. Choose based on interface preference; there is no need to install both.

How can I tell whether my Mac uses Apple Silicon or Intel?

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, or the Intel installer for an Intel processor. Do not rely only on the purchase year, since the same product line may have changed processors. Once the architecture matches, the client’s features and configuration workflow are the same.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is preferred. If the device is older, the system cannot identify its processor architecture, or the arm64 installer reports incompatibility, use the universal version. The universal package covers more devices, but the installer choice does not change subscription content; connection capability still depends on the client version, core support, and server configuration.

How should I choose between v2rayNG and v2flyNG?

Most Android users should start with v2rayNG, which uses the Xray core and covers common subscription and routing scenarios. v2flyNG uses the V2Fly core and suits existing V2Fly configurations, services that explicitly specify that core, or compatibility testing. Manage configurations separately in each app; do not directly overwrite one client’s data directory with the other’s.

Should Linux users choose deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based systems, and environments using RPM package management. After confirming the package format, check the processor: standard x64 desktops use the amd64 or x86_64 entry, while 64-bit ARM devices use arm64 or aarch64. If the distribution is unfamiliar, first review its package management documentation.

What should I do if there is no server list after installation?

The client does not generate server configurations automatically. After installation, add a valid subscription URL, import an individual server link, or load a supported configuration file. Save the subscription and run an update manually; once server entries appear, select one and connect. If the update fails, check in order that the URL is complete, the subscription has not expired, the current network can reach the update address, and whether updating through a proxy is required.