Client Packages

V2Ray Client Downloads and Version Selection

Choose a package by operating system, processor architecture, and interface version. Use v2rayN on desktop platforms; Android users can choose v2rayNG or v2flyNG.

Free forever Open source Subscription import Split routing TUN mode

Platform Downloads

Choose your current device platform

Switching platforms updates the page URL. Copy the platform-specific URL and reopen it to jump directly to the matching package.

Windows：v2rayN

The same client is available in Desktop and classic WPF editions. Choose Desktop for a first install; keep the classic interface if you already rely on the WPF workflow.

Recommended

v2rayN

Current version 7.24.1

Windows desktop client with subscription groups, node filtering, system proxy, routing rules, DNS settings, and TUN mode. The two packages use different interface technologies while remaining part of the same product line.

Recommended choice

Desktop edition

Next-generation cross-platform UI with a layout closer to the macOS and Linux editions, suited to new installations and cross-platform use.

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download Desktop edition

Classic interface

Classic WPF edition

A familiar, stable Windows interface for users who prefer the legacy menu structure and established workflow.

v2rayN-Setup-x64-7.24.1.zip

Download WPF edition

Windows System Requirements and Selection

Item	Requirement	Selection guide
Processor	x64	Supports common 64-bit Intel and AMD desktop processors.
Package format	ZIP archive	Extract the download to a fixed directory, then run the installer or launch program.
Interface edition	Desktop / WPF	New users should choose Desktop; choose WPF if you are familiar with the classic Windows interface.
Network permissions	Grant permissions as needed	Windows may ask you to confirm network-related permissions when enabling TUN or changing the system proxy.

Installation tip: After extracting the client, place it in a stable directory instead of running it long-term from the browser’s temporary download folder. This makes future updates and configuration management clearer.

macOS: Download v2rayN by Chip

Packages are provided separately for Apple Silicon and Intel. Match the package to your chip; the interface and core configuration features are the same.

Desktop Client

v2rayN

Current version 7.24.1

The macOS edition uses a cross-platform desktop interface for managing subscriptions, nodes, routing, DNS, and the system proxy. Check the chip field in System Information before downloading to avoid an architecture mismatch.

M-series chip

Apple Silicon

Choose this package when About This Mac shows an Apple M-series chip, including common M1, M2, M3, and later processors in the same family.

v2rayN-arm64.dmg

Download Apple Silicon edition

Intel processor

Intel

Choose this package when About This Mac shows an Intel processor. Do not identify the chip solely by the device’s appearance or purchase year.

v2rayN-64.dmg

Download Intel edition

macOS System Requirements and Selection

Item	Available option	How to identify it
Chip architecture	Apple Silicon	The Chip field in System Information shows an Apple M-series chip.
Processor architecture	Intel x64	The Processor field in System Information shows Intel.
Package format	DMG	Open the disk image and move the app to the system Applications directory.
First launch	System confirmation	Follow the security settings to open the app and confirm network permissions.

Check the chip: Open “About This Mac” or “System Information” from the system menu. An Apple Silicon chip is usually shown under “Chip”; choose the Intel package when “Processor” includes Intel.

Android: v2rayNG and v2flyNG

Choose the client by core requirements first, then select a package for the device architecture. Most mainstream phones released after 2015 should use arm64.

Recommended

v2rayNG

Current version 2.2.6

Android client built on the Xray core, supporting common subscriptions, QR-code imports, split routing, and local VPN connections. For most phone users, v2rayNG is the straightforward default.

Mainstream devices

arm64 edition

For most mainstream Android phones released after 2015, built for 64-bit ARM processors.

v2rayNG_2.2.6_arm64-v8a.apk

Download v2rayNG arm64

Compatibility option

Universal edition

Use the universal edition if you cannot identify the device architecture or the arm64 installer reports an architecture mismatch.

v2rayNG_2.2.6_universal.apk

Download v2rayNG universal edition

Alternative

v2flyNG

Current version 1.10.31

Android client built on the v2fly core, with subscription import, node selection, routing, and connection controls. Choose it if you already use v2fly configurations or specifically need its core behavior.

Mainstream devices

arm64 edition

For most modern 64-bit ARM phones. Download this first when the device is confirmed to use arm64.

v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Download v2flyNG arm64

Compatibility option

Universal edition

Use this version when the processor architecture is unclear or the architecture-specific package cannot be installed.

v2flyNG_1.10.31-fdroid_universal.apk

Download v2flyNG universal edition

Android System Requirements and Selection

Item	Recommendation	Details
Primary client	v2rayNG	Suitable for most subscriptions and common protocol configurations, using the Xray core.
Alternative client	v2flyNG	For users who specifically need v2fly core behavior or already have matching configurations.
Mainstream architecture	arm64	Most mainstream phones released after 2015 should try this package first.
Compatible package	Universal	Choose the universal edition when the device architecture is unknown or the dedicated package is incompatible.

Installation note: If the system asks you to confirm the installation source, first verify the client name and file name, then authorize the installation in the device settings. Disable the temporary authorization afterward.

Linux: Download v2rayN by Distribution and Architecture

Choose deb for Debian-based systems and rpm for Fedora and RHEL-based systems. Each format is available for x64 and arm64.

Desktop Client

v2rayN

Current version 7.24.1

Linux graphical client with controls for subscriptions, nodes, routing, the system proxy, and TUN. Confirm the distribution’s package format first, then use a system architecture command to identify x64 or arm64.

Debian / Ubuntu · x64

deb x64

v2rayn_7.24.1_amd64.deb

Download deb x64

Fedora / RHEL family · x64

rpm x64

v2rayN-7.24.1-1.el10.x86_64.rpm

Download rpm x64

arm64 package

For ARM desktops or development boards, confirm that the system architecture is arm64, then choose the format matching the distribution.

Download deb arm64 Download rpm arm64

v2rayn_7.24.1_arm64.deb v2rayN-7.24.1-1.el10.aarch64.rpm

Linux System Requirements and Selection

Distribution or device	Package format	Architecture
Debian, Ubuntu, and derivatives	deb	Choose x64 for common PCs and arm64 for ARM devices.
Fedora, RHEL, and compatible systems	rpm	x86_64 corresponds to x64; aarch64 corresponds to arm64.
Intel / AMD desktop devices	Choose by distribution	Usually use the x64 package.
ARM desktop or development board	Choose by distribution	Choose arm64 after confirming the system reports aarch64 or arm64.

Check the architecture: Run uname -m in a terminal. Choose x64 for x86_64; choose arm64 for aarch64 or arm64.

Before You Install

Four checks before choosing a package

The client name may be the same, but not every package will run on your device. Check the platform, architecture, format, and interface edition in order to avoid repeat downloads.

The operating system must match

Use the Desktop installer inside the ZIP on Windows, DMG on macOS, APK on Android, and deb or rpm on Linux according to the distribution. Different extensions require different installation methods. Do not rename an extension to run a package on another platform.

The processor architecture must match

x64 generally means 64-bit Intel and AMD desktop processors; arm64 means 64-bit ARM devices; Apple Silicon is the ARM architecture used by macOS. Dedicated packages are usually the most direct choice, while universal packages are intended for Android devices with unclear architectures.

Evaluate the client and core separately

Use v2rayN on desktop platforms. On Android, v2rayNG with the Xray core is the default choice; choose v2flyNG if you already use v2fly configurations or specifically need its behavior. Import subscriptions or server configurations after installation; no separate component is required.

Preserve existing settings before updating

If you have subscription groups, custom routes, DNS, or local inbound settings, export or back up the configuration through the client before updating. Afterward, check the subscription groups, active node, system proxy mode, and TUN status against the previous setup.

After Downloading

From Installation to Connection

The package only provides the graphical client. A working server configuration or subscription URL is still required; then choose the system proxy, routing mode, or TUN mode based on the apps you want to cover.

Complete installation and launch
Extract, install, or authorize the app according to the platform. On first launch, make sure the client opens normally before configuring subscriptions and the proxy.
Import a subscription or individual configuration
Copy the complete subscription URL and add it to a subscription group, or import an individual server configuration through a link, QR code, or clipboard. Update the subscription after importing.
Choose a node and routing mode
Select the current node from a subscription group. A common choice is a route that bypasses local-network and mainland China addresses; switch to global mode only when all supported traffic should use the proxy.
Enable the proxy and verify
Enable the system proxy for browsers and other apps that follow system settings. Configure TUN mode when more app traffic needs to be captured. Reconnect after changing modes and check the target apps individually.

Read the complete setup guide Read Advanced Config

Download FAQ

Package, Architecture, and Client Selection

These answers cover the packages listed on this page. For detailed troubleshooting of connections, subscriptions, routing, and DNS, continue to the Help Center.

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

Try the Desktop edition first. Its next-generation cross-platform UI provides a similar structure across Windows, macOS, and Linux, making it suitable for new installations and use across devices. The classic WPF edition retains the traditional Windows interface and familiar menu paths for users who have built their workflow around it. Both are v2rayN and support subscriptions, system proxy, routing, DNS, and TUN.

How do I know whether to download the Apple Silicon or Intel package for macOS?

Open “About This Mac” from the system menu or go to “System Information,” then check the chip or processor field. Choose Apple Silicon when an Apple M-series chip is shown; choose Intel when an Intel processor is listed. Use the system field as the authority rather than judging by appearance or purchase date.

Should Android users choose arm64 or the universal edition?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is the best first choice. The universal edition supports a broader range of architectures and is suited to devices with an unknown processor or those that report arm64 incompatibility. Both packages provide the same client features; the main difference is the target processor architecture.

How should I choose between v2rayNG and v2flyNG?

Most Android users should start with v2rayNG. It uses the Xray core and supports common subscriptions, QR-code imports, split routing, and local VPN connections. v2flyNG uses the v2fly core and is intended for users who specifically need its behavior, already have a matching configuration, or want to keep a separate client setup on the same device.

Should Linux users download deb or rpm?

Debian, Ubuntu, and derivatives generally use deb; Fedora, RHEL, and compatible distributions generally use rpm. Then confirm the processor architecture: x86_64 maps to x64, while aarch64 or arm64 maps to arm64. Run uname -m in a terminal to check.

How do I connect after installing the client?

Start with a working server configuration or subscription URL. Add and update the subscription in the client, or import an individual configuration. Then choose a node and routing mode, and enable the system proxy or TUN mode based on the apps you need to cover. The system proxy mainly affects apps that follow system settings; TUN mode uses a virtual network adapter to handle more traffic and usually requires network permission the first time.

Open the Help Center for installation, configuration, and Troubleshooting →