client packages

V2Ray client download

Choose a package based on the device's operating system and processor architecture. Use v2rayN on desktop systems, and choose between v2rayNG and v2flyNG on Android.

Free forever Open source Four platforms Chinese documentation

platform selector

Choose a device platform

The platform selection is reflected in the page URL. Copy the current address to return directly to the same platform's download section.

windows

Windows：v2rayN

Windows offers Desktop and the classic WPF interface. For a first installation, Desktop is usually the better choice; users who have relied on WPF or want to keep its familiar menus can continue with the classic version.

Recommended Windows desktop

v2rayN

Current version 7.24.1

v2rayN is a graphical Windows desktop client for importing subscriptions, switching configurations, managing routing rules, controlling the system proxy, and viewing runtime logs. Both installers follow the same version line; the main difference is the UI technology and layout.

Desktop edition

A newer cross-platform UI for first-time installations, users who want the latest interface, or anyone seeking a similar workflow across desktop systems.

Download Desktop edition

Classic WPF edition

The classic Windows interface with its established menus and workflow. Suitable for users familiar with the older v2rayN experience or those who want to preserve existing desktop habits.

Download classic WPF edition

Windows requirements and selection

Item	Recommendation	How to check
Operating system	Use a 64-bit Windows version that is still supported	Open “Settings → System → About” to view the version and system type
Processor architecture	x64	Use this page's package when the system type shows “64-bit operating system, x64-based processor”
Installation permissions	Allow the current user to install desktop applications	Managed devices must follow the organization's software installation rules
Handling an older version	Exit the client before running the new installer	Confirm that v2rayN is no longer running in the taskbar notification area

After installation, launch the client first and then import the subscription. If another network tool controls the system proxy, exit the conflicting program first to prevent multiple applications from changing proxy settings at once.

macos

macOS：v2rayN

macOS installers are provided for Apple Silicon and Intel. Client features are identical, but you must choose based on the chip or processor shown in About This Mac.

Desktop Dual architecture

v2rayN for macOS

Current version 7.24.1

The v2rayN macOS desktop edition supports subscription updates, configuration management, the system proxy, routing modes, and log viewing. Before downloading, confirm only the chip type; no other variant is needed based on system language or device model.

Apple Silicon

For devices with Apple M-series chips. Choose this package when About This Mac shows Apple M1, M2, M3, M4, or a later chip in the same family.

Download Apple Silicon version

Intel

For devices whose processor field in About This Mac explicitly shows Intel. The processor name usually includes the specific series and clock speed.

Download Intel version

macOS requirements and selection

Item	Apple Silicon	Intel
Chip identifier	Apple M series	Intel processor
Package format	DMG，arm64	DMG，x64
Installation method	Open the disk image and follow the window instructions to place the app in the Applications folder	Open the disk image and follow the window instructions to place the app in the Applications folder
First launch	Follow the system prompts to confirm app launch and network permissions	Follow the system prompts to confirm app launch and network permissions

If you downloaded the wrong architecture, the app may not start. Delete the incorrect app copy and download the DMG matching your chip. Re-import the subscription URL after launching the correct version.

android

Android: two clients

Choose v2rayNG first if you prefer the Xray core. Choose v2flyNG when you need the V2Fly core path. Both clients offer arm64 and universal packages; for everyday use, keep only one installed.

Recommended Xray core

v2rayNG

Current version 2.2.6

v2rayNG is a commonly used graphical client for Android, supporting subscription imports, QR-code imports, configuration switching, routing settings, and connection logs. Most mainstream phones released since 2015 can use the arm64 version directly.

arm64 version

For 64-bit ARM devices, including recent mainstream Android phones and tablets. Choose this package when the architecture is known.

Download v2rayNG arm64

Universal version

Provides broader architecture coverage. Choose it when the processor type is unknown or the arm64 version cannot be installed.

Download universal v2rayNG

Alternative V2Fly core

v2flyNG

Current version 1.10.31

v2flyNG is for Android users who need the V2Fly core path. It also supports subscriptions, configuration management, and routing. Before switching clients, save the subscription URL and any manual settings that must be retained.

arm64 version

For mainstream devices with 64-bit ARM processors. Choose this version when the processor architecture is known.

Download v2flyNG arm64

Universal version

For devices with an unknown architecture or arm64 incompatibility; this package offers broader coverage.

Download universal v2flyNG

Android requirements and selection

Item	Recommendation	Details
Primary client	v2rayNG	Suitable for most Android users and common subscription configurations
Alternative client	v2flyNG	For configurations that specifically require the V2Fly core path
Processor architecture	Prefer arm64 on mainstream devices	Use the universal version when the architecture is unknown
Installation permissions	Allow installation from this source when prompted by the system	Restore the original permission settings after installation if needed

If a client with the same name is already installed, the system determines whether an overwrite is allowed based on the app signature and version state. Record the subscription URL before upgrading; when moving between clients, re-importing the subscription is usually clearer than copying settings one by one.

linux

Linux：v2rayN

Choose the Linux desktop package by package system and processor architecture. Debian and Ubuntu systems generally use deb; Fedora and RHEL systems generally use rpm. Standard PCs are usually x64, while ARM desktops and development boards use arm64.

Desktop deb / rpm

v2rayN for Linux

Current version 7.24.1

The v2rayN Linux desktop edition provides graphical subscription management, configuration switching, the system proxy, and routing controls. First identify the distribution's package system, then choose x64 or arm64 based on the system architecture.

deb · x64

For 64-bit PCs running Debian, Ubuntu, or common derivatives.

Download x64 deb

rpm · x64

For 64-bit PCs running Fedora, RHEL, or another distribution using RPM packaging.

Download x64 rpm

arm64 architecture packages

Choose these only when the system reports aarch64 or arm64. The package format must still match the distribution.

Download arm64 deb Download arm64 rpm

Linux requirements and selection

Distribution	Package format	Architecture
Debian, Ubuntu, and derivatives	deb	Choose x64 for x86_64 and arm64 for aarch64
Fedora and RHEL-based distributions	rpm	Choose x64 for x86_64 and arm64 for aarch64
Desktop environment	A working graphical desktop session is required	Tray display depends on the desktop environment and extension support
Installation permissions	Package installation usually requires administrator authorization	Grant the requested permission only when prompted during installation

When the package manager reports missing dependencies, refresh the current distribution's repository index first, then let the package manager resolve them. Do not mix deb and rpm, or use an x64 package on an arm64 system.

package selection

Package selection order

Choose in this order: operating system, processor architecture, then package format. The same platform name does not mean packages are interchangeable: macOS requires a chip choice, Android requires arm64 or a universal package, and Linux also requires matching the distribution's package system.

If the system information does not match the package name, pause the installation and check the device details. Trying different packages repeatedly will not improve compatibility; matching each package to the system fields is a faster way to identify the issue.

01
Confirm the platform
Choose the current device from Windows, macOS, Android, or Linux.
02
Confirm the architecture
Check system information on desktop systems; use the universal version on Android when the architecture is unknown.
03
Confirm the package format
On Linux, choose deb or rpm based on the distribution; other platforms use their corresponding installer format.
04
Exit the old version
Close the running client before installation, and save your subscription and custom rules.

after install

Post-install configuration order

After installing the client, avoid changing several settings at once. First import the subscription, update it manually once, select a configuration, and enable the system proxy. This separates and verifies the download, installation, subscription, and connection stages.

If the list is empty after importing a subscription, first check that the URL is complete and then update it again. If configurations appear but cannot connect, check the local network, system time, service parameters, and routing mode instead of repeatedly reinstalling the client.

View configuration guide Open troubleshooting manual

Import the subscription URL

Copy the complete URL, add a new group in the client's subscription manager, and save it.

Update the subscription manually

Run one update and confirm that the configuration list has loaded successfully.

Choose a routing mode

Start with a clearly defined basic mode, then add custom split-routing rules once it is stable.

Check the system proxy

Confirm that the current client manages the proxy, and prevent other tools from taking control at the same time.

download faq

Common download and installation issues

These questions cover version, architecture, package format, and upgrade choices. For subscription imports and connection problems, continue to the guide and troubleshooting manual.

Should Windows users choose v2rayN Desktop or the WPF version?

Desktop is the newer cross-platform interface for users who want the latest UI and a consistent workflow; WPF is the classic Windows interface for users familiar with the older layout or established habits. Do not run both at the same time.

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 Apple Silicon for an Apple M-series chip, or the Intel package for an Intel processor. The architecture must match; client features are identical.

What is the difference between the arm64 and universal Android versions?

The arm64 package targets 64-bit ARM devices and contains only the needed architecture files, making it suitable for mainstream Android phones and tablets released since 2015. If the architecture is unknown or arm64 installation fails, use the universal version. There is no need to install both.

Should Linux users download deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL, and distributions using RPM packaging. Also select x64 or arm64 based on the processor architecture, which you can check with uname -m.

Do I need to delete the existing configuration before installing a new version?

Usually not. Before upgrading, exit the running client and back up your subscription URLs, custom routing rules, and local configuration. When switching interface versions, export the configuration first so differences can be quickly restored if needed.

What should I configure after the download finishes?

After installing and launching the client, import the subscription URL from your provider, update it once manually, select an available configuration, and enable the system proxy. For connection issues, check the local network, system time, subscription, and routing settings in that order.