CLIENT RELEASE INDEX · 2026

V2Ray Client Downloads and Platform Selection

Choose a package by operating system, processor architecture, and desktop release line. Use v2rayN on desktop platforms, v2rayNG as the preferred Android client, and v2flyNG as an alternative for the V2Fly ecosystem.

Free forever Open source GUI CLIENTS Xray · V2Fly

PLATFORM CATALOG

Browse packages by platform

Your tab selection is synced to the page URL. Copy a URL with the platform marker to return directly to the corresponding download group.

WINDOWS · X64

v2rayN desktop releases

Windows offers Desktop and classic WPF versions. Both are v2rayN, but their UI technologies, runtime dependencies, and migration paths differ; the two archives should not be treated as identical builds.

v2rayN

7.24.1

Recommended

The Desktop version uses a newer cross-platform UI and is the preferred choice for the current desktop release line. The classic WPF version is Windows-only and suits users who want to keep familiar menus, configuration directories, and workflows. For first-time use, start with Desktop; when migrating from an older version, record subscription groups, routing rules, and system proxy status first.

Desktop

A cross-platform UI architecture for new installations and a consistent desktop experience.

WPF

The classic Windows interface for users who prefer the established WPF workflow.

Download v2rayN Desktop Download classic WPF

Windows requirements and selection guide

Item	Applies when	How to choose
Processor	64-bit x86 processor	The Windows packages on this page are x64 builds. Confirm the system type in System Information first.
Desktop version	New installation or cross-platform desktop use	Uses the Avalonia cross-platform UI architecture and differs from the WPF interface.
WPF version	Classic Windows release line	For users familiar with the established WPF menus, tray behavior, and configuration workflow.
Before upgrading	Existing subscriptions or custom rules	Record subscription groups, routing configuration, and local ports. Do not overwrite the original directory when switching release lines.

MACOS · DMG

v2rayN processor variants

macOS packages are split between Apple Silicon and Intel. Processor architecture is the only reliable choice; the macOS version name, device appearance, and purchase year are only supporting clues.

v2rayN

7.24.1

Desktop version

Open System Information and check the Chip or Processor field. Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. After downloading, use the matching DMG package; do not infer architecture from file size or numbers in the filename.

ARM64

For devices with Apple M-series chips.

X64

For devices with Intel processors.

Download Apple Silicon Download Intel

macOS requirements and selection guide

System Information field	Package to choose	Notes
Chip: Apple M series	Apple Silicon	Choose the arm64 DMG to match the device processor architecture.
Processor: Intel	Intel	Choose the x64 DMG; do not use it with an Apple Silicon build.
First launch	System security confirmation	If the system asks you to confirm the app's source, review the specific prompt in the security settings.
Upgrade migration	Preserve configuration records	Record subscriptions, routing mode, and local listener settings before upgrading to avoid overwriting a configuration directory still in use.

ANDROID · APK

v2rayNG and v2flyNG

The Android section lists v2rayNG, which follows the Xray ecosystem, first, followed by v2flyNG, which uses the V2Fly core. Their use cases are similar, but core branches, setting names, and configuration compatibility boundaries differ.

v2rayNG

2.2.6

Recommended

v2rayNG is the preferred graphical client for Android and follows the Xray ecosystem. Most mainstream phones released after 2015 can use arm64; choose Universal when the architecture is unknown, the device is older, or the dedicated package will not install. Save existing subscription URLs and per-app proxy settings before installation.

ARM64

For most newer 64-bit ARM phones and tablets.

UNIVERSAL

Broader coverage for devices with an unknown architecture.

Download v2rayNG arm64 Download v2rayNG Universal

v2flyNG

1.10.31

Alternative

v2flyNG uses the V2Fly core and suits users who specifically need that core branch, already have compatible configuration, or want to keep an established workflow. The architecture rules are the same as for v2rayNG: prefer arm64 on newer mainstream devices and choose Universal when the architecture is unknown. Recheck routing and DNS settings when moving between clients.

ARM64

A dedicated build for 64-bit ARM devices.

UNIVERSAL

A universal build for multiple Android processor architectures.

Download v2flyNG arm64 Download v2flyNG Universal

Android requirements and selection guide

Item	Preferred choice	When to switch
Client	v2rayNG	Choose v2flyNG when you specifically need the V2Fly ecosystem or already have compatible configuration.
Newer mainstream devices	arm64	Most mainstream phones released after 2015 use a 64-bit ARM architecture.
Unknown architecture	Universal	Use it when the processor type cannot be checked or the arm64 package reports incompatibility.
Background operation	Allow the VPN service to keep running	The manufacturer's battery-saving policy may terminate background connections. Adjust the app's battery settings as prompted by the system.

LINUX · DEB / RPM

v2rayN package formats and architectures

Linux packages must match both the package format and processor architecture. Debian and Ubuntu systems generally use deb, while Fedora and RHEL systems generally use rpm. Choose x64 for common desktop computers and arm64 for ARM devices.

v2rayN

7.24.1

Desktop version

First identify the distribution's package management system, then confirm the machine architecture. Most Intel and AMD desktops use x64; devices with 64-bit ARM processors use arm64. If the package type is wrong, the package manager will usually report a format or architecture mismatch. Do not fix it by changing the extension.

DEB

For Debian, Ubuntu, and derivatives using deb package management.

RPM

For Fedora, RHEL-based systems, and distributions using RPM package management.

Download x64 deb Download x64 rpm

ARM64 PACKAGES Download arm64 deb Download arm64 rpm

Linux requirements and selection guide

Distribution environment	Package	Architecture notes
Debian / Ubuntu family	deb	Choose x64 for standard Intel or AMD desktops and arm64 for 64-bit ARM devices.
Fedora / RHEL family	rpm	x86_64 corresponds to x64; aarch64 corresponds to arm64.
Desktop session	Graphical environment	v2rayN is a graphical client. Complete setup and tray operations in an available desktop session.
Upgrade handling	Use the same package management system	Stay on the same deb or rpm release line and exit the running client before upgrading.

INSTALLATION NOTES

Four decision layers for package selection

The client model is only the first layer. Platform, processor, package format, and configuration migration together determine whether installation goes smoothly.

Platform boundaries

v2rayN supports Windows, macOS, and Linux desktops; v2rayNG and v2flyNG target Android. Letters in a name cannot replace platform checks, and a shared subscription URL does not make packages interchangeable across operating systems. Identify the device operating system first, then open the matching tab to reduce selection errors.

platform

Processor architecture

x64 is common on Intel and AMD desktops, while arm64 is common on Apple M-series devices, mainstream Android phones, and some ARM Linux systems. A mismatch can prevent an installer from launching or cause the package manager to reject the package. Android Universal is for cases where the architecture is unknown; it does not replace the guidance for dedicated builds.

architecture

Release lines and package formats

The Windows Desktop and WPF versions use different UI technology paths; Linux deb and rpm packages target different package management systems; the two macOS DMGs are separated by processor architecture. A file extension describes the distribution method, not a decorative suffix. Use system information and distribution documentation rather than file size to choose.

package

Configuration migration scope

Client upgrades usually retain existing settings, but fields and UI options may differ across release lines, clients, or core ecosystems. Before migrating, record subscription URLs, group relationships, custom DNS, routing rules, local ports, and system proxy mode. Restoring items individually after installation makes differences easier to identify than copying the entire old directory.

migration

AFTER DOWNLOAD

Installation and first-time setup after download

The package only deploys the client. Importing subscriptions, choosing a routing mode, and configuring the system proxy still need to be completed after first launch.

STEP 01

Exit the old process

Before upgrading, exit normally from the client menu and check that the tray icon disappears. On Windows and Linux desktops, closing the window does not always end the background process. If the installer reports a file lock, use Task Manager or the system monitor to confirm that the relevant process has stopped before continuing.

STEP 02

Record key configuration

At minimum, keep the subscription URL, active configuration, routing mode, DNS rules, per-app proxy scope, and local listening ports. Exported configuration may contain device-specific paths and should not be copied wholesale to another system. For manual rules, record their order as well, since match order in the array affects traffic routing.

STEP 03

Complete installation and permissions

Open the package using the operating system's standard installation process. The first time a mobile client starts the VPN service, the system displays a connection confirmation; enabling the system proxy on desktop may also require a security prompt or desktop-session permission. Confirm only the explicit items shown by the current system, and do not apply steps from another platform.

STEP 04

Import and verify configuration

After importing a subscription, update it manually once and confirm that groups and nodes appear correctly. Then choose the routing mode and active configuration. After connecting, check the client log for address, port, DNS, or certificate errors. If system apps still cannot connect as expected, verify the system proxy and routing rules instead of repeatedly reinstalling the client.

For complete steps covering subscription import, mode selection, connection checks, and common errors, continue with the getting-started documentation.

Read the Getting Started guide

DOWNLOAD FAQ

Common download and installation questions

These questions focus on version, architecture, and migration decisions. Detailed explanations of configuration fields, DNS, and routing rules are covered in the complete configuration reference.

View the complete configuration reference

Should you choose the Desktop or WPF version of v2rayN on Windows?

The Desktop version uses a newer cross-platform interface for users who want the current desktop release line; the WPF version is Windows-only and stays closer to familiar workflows. New installations can usually start with Desktop. If you are migrating an existing WPF configuration, record subscription groups, routing rules, and local ports first, and do not overwrite the old directory without a configuration backup.

How do you know whether to download the Apple Silicon or Intel version on macOS?

Check the Chip or Processor field in System Information. Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. The device model and purchase date may help, but cannot replace System Information. Do not judge by package size; the processor field is the definitive guide.

Should you choose arm64 or Universal on Android?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is the preferred choice. Use Universal when the architecture is unknown, the device is older, or arm64 installation fails. Universal supports more processor types and is useful when compatibility is unclear, but it should not automatically take priority over a dedicated build.

Should you choose a deb or rpm package on Linux?

Debian, Ubuntu, and their derivatives generally use deb; Fedora, RHEL-based systems, and distributions using RPM package management generally use rpm. After choosing the format, check the processor architecture: common Intel and AMD desktops use x64, while 64-bit ARM devices use arm64. Both format and architecture must match.

How should you choose between v2rayNG and v2flyNG?

v2rayNG is the preferred Android client and follows the Xray ecosystem; v2flyNG uses the V2Fly core and is an alternative when that ecosystem or configuration compatibility is required. Their subscription and routing interfaces differ. Before switching clients, save the original subscription URL and recheck DNS, per-app proxy, and routing options.

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

You can usually upgrade directly within the same release line. For migrations between Desktop and WPF, between clients, or across major configuration structures, export subscriptions and custom routing information first. If the installer says the app is running, exit the client and its background processes before trying again. After upgrading, check the configuration before deciding whether to remove the old directory.