CLIENT PACKAGES / STABLE

V2Ray Client Download: Choose a package by platform

Use v2rayN on desktop systems and v2rayNG on Android; choose v2flyNG when you need the V2Fly core. Before downloading, confirm the operating system, processor architecture, and package format to avoid an architecture mismatch during installation.

Free forever Open source Graphical client Stable release

PLATFORM SELECTOR

Choose an operating system and client

Switching platforms updates the page URL. Copying a link with a platform marker and reopening it will return you to the matching download section. Each client card lists package differences and supported architectures.

WINDOWS / X64

Windows：v2rayN

Windows offers Desktop and classic WPF interface editions. For a new installation, start with Desktop; if you are familiar with the traditional v2rayN interface, shortcut menu, and settings locations, choose WPF. Exit any older client before installing to prevent configuration files from being locked.

v2rayN

Recommended

7.24.1

v2rayN is a graphical desktop client for managing subscriptions, nodes, the system proxy, routing rules, and TUN mode. The Desktop edition uses a modern cross-platform UI, while the WPF edition retains the classic Windows interface. Both support the same everyday configuration tasks.

Desktop edition Modern cross-platform interface · Windows x64

Download the Desktop edition

Classic WPF edition Traditional Windows interface · Windows x64

Download the classic WPF edition

Windows system requirements and selection guide

Check	Recommendation	Details
Processor architecture	`x64`	The Windows packages on this page target common 64-bit Intel and AMD processors.
Edition selection	Desktop first	Choose Desktop for a new installation; choose WPF when you need the classic interface and familiar menu paths.
Upgrade preparation	Exit the old edition and record your settings	Save your subscription URLs, routing mode, and custom rules before upgrading, then verify each item after installation.

MACOS / ARM64 / X64

macOS：v2rayN

macOS packages are split between Apple Silicon and Intel. Open About This Mac from the system menu and check the chip or processor field: choose Apple Silicon for Apple M-series chips and Intel for Intel processors. The architecture must match; the interface and configuration workflow remain the same.

v2rayN

Desktop client

7.24.1

On macOS, v2rayN provides subscription management, node selection, system proxy, and routing settings. The two packages differ only by processor architecture, not feature level; choose based on the device chip rather than its appearance or purchase year.

Apple Silicon Apple M-series chip · arm64

Download the Apple Silicon edition

Intel Intel processor · x64

Download the Intel edition

macOS requirements and chip identification

Device information	Package	How to identify it
Apple M-series chip	`arm64 dmg`	The chip field in About This Mac shows an Apple M-series model.
Intel processor	`x64 dmg`	The processor field in About This Mac explicitly shows Intel.
First launch	Confirm the system prompt	After installation, follow the system interface to confirm that the app can open, then configure subscriptions and proxy mode.

ANDROID / ARM64 / UNIVERSAL

Android: v2rayNG and v2flyNG

Android clients differ by core family and package architecture. For everyday configuration, start with v2rayNG; choose v2flyNG when an existing setup depends on V2Fly core behavior. Most mainstream phones released after 2015 can use arm64; if the architecture is unclear or installation reports incompatibility, use the universal edition.

v2rayNG

Recommended

2.2.6

v2rayNG is an Android graphical client built on the Xray core, supporting subscription imports, QR-code scanning, node switching, routing settings, and connection status checks. Use the arm64 package first on mainstream 64-bit ARM phones.

arm64 edition Mainstream 64-bit ARM phones

Download v2rayNG arm64

Universal edition For uncertain architectures

Download the v2rayNG universal edition

v2flyNG

1.10.31

v2flyNG uses the V2Fly core and covers the same subscription, node, routing, and connection controls. Choose it when you already have a V2Fly configuration, need compatible core behavior, or want to compare differences.

arm64 edition Mainstream 64-bit ARM phones

Download v2flyNG arm64

Universal edition For uncertain architectures

Download the v2flyNG universal edition

How to choose an Android package

Selection	Priority condition	What to do
v2rayNG	Regular use and Xray configurations	Use it as the everyday default; after importing a subscription, check the groups, active node, and routing mode.
v2flyNG	V2Fly configuration compatibility	Use it for existing V2Fly configurations or scenarios requiring matching core behavior.
arm64	Mainstream phones released after 2015	Most modern devices can start with this version, which targets a more focused architecture and package size.
Universal edition	Architecture cannot be confirmed	Use it when arm64 reports incompatibility or the device information does not identify the architecture clearly.

LINUX / DEB / RPM

Linux：v2rayN

Linux packages are separated by distribution package manager and processor architecture. Debian, Ubuntu, and their derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. Most desktop computers use x64, while ARM devices use arm64.

v2rayN

Desktop client

7.24.1

The Linux edition of v2rayN provides a graphical desktop interface. Before installing, confirm the distribution's package format, then identify the architecture through system information or command output. The wrong package format is usually rejected by the package manager; the wrong processor architecture will prevent installation or startup.

deb · x64 Debian, Ubuntu, and their derivatives

Download x64 deb

rpm · x64 RPM-based distributions

Download x64 rpm

ARM64 package

Choose this only when the device processor architecture is confirmed as arm64 or aarch64.

Download arm64 deb Download arm64 rpm

Linux package formats and architectures

System type	Package format	Architecture label
Debian, Ubuntu, and derivatives	`deb`	Choose amd64 for common desktop computers and arm64 for ARM devices.
Fedora, Rocky Linux, AlmaLinux, and others	`rpm`	Choose x86_64 for common desktop computers and aarch64 for ARM devices.
Confirm the architecture	Check system information	Before installing, confirm that the system reports x86_64, amd64, aarch64, or arm64.

PACKAGE DECISION

Package selection rules

Client name, operating system, package format, and processor architecture are four separate conditions. Identify the platform first, then the client, and finally verify the architecture and package format; this is more reliable than guessing from the filename alone.

Choose the client first

Use v2rayN on Windows, macOS, and Linux. For everyday Android use, start with v2rayNG; switch to v2flyNG only when an existing configuration requires V2Fly core behavior. The two clients may use different data directories and settings structures, so do not directly overwrite one app's directory with the other's.

Then identify the processor architecture

In this guide, x64, amd64, and x86_64 refer to common 64-bit Intel or AMD desktop processors; arm64 and aarch64 refer to 64-bit ARM architecture. Architecture is determined by the processor, not by interface language, screen size, or memory capacity.

Finally, confirm the package format

macOS uses dmg, Android uses apk, and Linux uses deb or rpm according to the distribution. The two Windows zip packages contain the Desktop and WPF installers respectively. After downloading, open the package through the system's normal installation process; do not run the program long-term directly from inside the archive.

AFTER DOWNLOAD

Installation and first launch after downloading

Installation only means that the client has been added to the system; subscriptions, nodes, routing, and the system proxy still need to be configured in order. Complete one step before moving to the next so that any issue is easier to locate.

Close old processes and keep configuration notes

If an older version is installed, exit it from the client menu, then confirm that no process remains in the taskbar or system status area. Record the current subscription groups, active node, proxy mode, local listening port, and routing settings. Direct installation over the old version usually preserves data, but notes still help compare fields across versions.

Finish installation and check the launch location

Complete the installer on desktop systems and confirm the app through the system installation flow on mobile devices. On first launch, check the client version and data directory before deciding whether to import an old configuration. If the system reports an architecture mismatch, return to this page and choose the correct architecture instead of repeatedly trying the same file.

Import a subscription and update it

Open subscription management, add the subscription link, save it, and run an update. If the node list is empty, check that the URL is complete, that group filters are not hiding results, and that the update actually finished. Do not repeatedly switch system proxy modes before a node list has been generated.

Choose a node, routing mode, and proxy status

Select a node from a subscription group, then choose a routing mode for your use case. For the first test, keep settings as simple as possible: confirm that the client can establish a connection before enabling TUN, custom rules, or LAN sharing. Changing several switches at once makes troubleshooting harder.

Need the full configuration walkthrough?

The quick-start guide walks through subscription import, node selection, proxy mode, and connection checks in order.

Open the quick start

DOWNLOAD FAQ

Common download and installation questions

These questions cover edition branches, processor architectures, package formats, and upgrade paths. For subscription imports, connection status, and routing settings, see the FAQ and quick-start pages.

Should Windows users choose v2rayN Desktop or the WPF edition?

The Desktop edition uses a modern cross-platform interface and suits new installations or users seeking a consistent desktop experience. The WPF edition retains the classic Windows interface for users familiar with the older workflow and traditional settings layout. Both handle the same core configuration tasks; do not run them simultaneously, or system proxy and local listening ports may conflict.

How do you tell Apple Silicon from Intel on macOS?

Open About This Mac from the system menu and check the chip or processor field. Choose the Apple Silicon package for Apple M-series chips and the Intel package for Intel processors. The purchase year is only a supporting clue and should not replace the system field.

Should Android users download arm64 or the universal edition?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is usually the best choice. Use the universal edition if the device architecture is unknown or the arm64 package reports incompatibility. The universal edition supports more architectures; it does not provide extra features.

Which should you choose: v2rayNG or v2flyNG?

For everyday Android use, start with v2rayNG, which uses the Xray core and supports common protocol configurations. Choose v2flyNG when you need V2Fly core behavior or an existing configuration depends on V2Fly. Compatibility differs between the two, so record the original settings before switching.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and their derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. You must also choose x64 or arm64 based on the processor; a correct package format cannot compensate for the wrong architecture.

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

Usually, you can exit the client and install the new version directly. Before upgrading, export or record your subscriptions, routing mode, and custom settings. When crossing several major versions, compare the new interface for configuration-field and data-directory changes. If something goes wrong, first determine whether the program failed to start, the configuration failed to migrate, or the subscription update failed.

Connection and configuration issues

Subscription import failures, empty node lists, TUN mode, and system proxy differences are covered on the FAQ page.

Go to the FAQ