Official Releases Four platform categories

V2Ray Client Downloads

Choose an installer by operating system and processor architecture. Use v2rayN on desktop systems, v2rayNG on Android by default, or v2flyNG when the v2fly core is required.

Latest installers Free forever Open source Chinese usage guides

Choose a platform and installer View the setup guide after installation

PLATFORM PACKAGES

Choose an installer by operating system

The platform label is added to the page URL. Save a platform-specific URL to return directly to the relevant download section next time.

WINDOWS CLIENT

Windows：v2rayN

v2rayN provides subscription management, server switching, system proxy, routing rules, and TUN support on desktop. For a first installation, Desktop is recommended; users familiar with WPF can continue with the classic version.

Current release: 7.24.1

Recommended Desktop client

v2rayN for Windows

Manage subscription updates, servers, system proxy settings, and routing rules from one interface.

Desktop version

A modern cross-platform UI for first-time installations and users who want a consistent workflow across desktop systems.

Download the Desktop version

Classic WPF version

The classic Windows interface keeps the familiar menu layout and closely follows existing tutorials, making it suitable for users who want to retain the original workflow.

Download the classic WPF version

Windows system requirements and selection guide

Check	Recommended choice	Details
Processor architecture	x64	For current mainstream Intel and AMD desktop processors.
First installation	Desktop	The interface structure is updated, making it easier to keep a consistent workflow when switching desktop platforms later.
Keep the classic interface	WPF	For users familiar with the classic menus, system tray entry, and settings layout.
Post-installation setup	Subscription group	Add the subscription URL and update it first, then choose a server and system proxy mode.

MACOS CLIENT

macOS：v2rayN

macOS installers are available for Apple Silicon and Intel processors. Before downloading, check the Chip or Processor information in About This Mac, then install the matching architecture.

Current release: 7.24.1

Desktop choice Universal architectures

v2rayN for macOS

Provides familiar subscription, server, system proxy, and routing settings across desktop systems.

Apple Silicon

For devices whose Chip section in About This Mac shows an Apple M-series chip.

Download the Apple Silicon version

Intel

For devices whose Processor section in About This Mac shows Intel.

Download the Intel version

macOS system requirements and selection guide

Device information	Installer	How to check
Apple M-series chip	Apple Silicon	Open About This Mac from the system menu and check whether the Chip field shows an M-series model.
Intel processor	Intel	The Processor field in About This Mac explicitly shows Intel.
First launch	Confirm system permissions	Follow the system prompts to grant the permissions required for app launch, network access, and proxy configuration.
Import configuration	Subscription URL	Add the subscription, update the list, and then choose a server and proxy mode.

ANDROID CLIENTS

Android: v2rayNG and v2flyNG

For everyday use, v2rayNG is the first choice. It uses the Xray core and covers common tasks such as subscriptions, routing, per-app proxying, and connection control. Choose v2flyNG only when v2fly core behavior is specifically required.

Recommended Xray core

v2rayNG

An Android graphical client for importing subscriptions, switching servers, configuring routes, and managing everyday connections. Current release: 2.2.6

arm64 version

For mainstream Android phones released after 2015. Its focused package size makes it the recommended first choice.

Download v2rayNG arm64

Universal version

Choose this when the device architecture is unknown, arm64 cannot be installed, or broader compatibility with older architectures is needed.

Download the v2rayNG universal version

Alternative v2fly core

v2flyNG

Its workflow is similar to other Android graphical clients and suits configurations that specifically use the v2fly core. Current release: 1.10.31

arm64 version

For current mainstream 64-bit ARM phones; choose it first when the device architecture is confirmed.

Download v2flyNG arm64

Universal version

Use this when the device architecture is unknown or the arm64 package cannot be installed.

Download the v2flyNG universal version

Android system requirements and selection guide

Choice	Recommended result	Use case
Everyday use	v2rayNG	Requires the Xray core, subscription management, routing, and per-app proxy controls.
Specific configuration	v2flyNG	The configuration provider explicitly requires the v2fly core or its implementation behavior needs to be verified.
Mainstream phones	arm64	Most Android phones released after 2015 can try this architecture first.
Unknown architecture	Universal version	Use this when device information is unclear or arm64 installation fails.

LINUX CLIENT

Linux：v2rayN

For Linux, first distinguish deb from rpm by the distribution's package system, then choose x64 or arm64 based on the processor. After confirming both, select the matching file.

Current release: 7.24.1

Desktop client deb / rpm

v2rayN for Linux

Provides graphical subscription, server, system proxy, and routing management, with installers for common desktop distributions and both processor architectures.

x64 deb

For x64 desktop devices running Debian, Ubuntu, or another distribution using the deb package system.

Download x64 deb

x64 rpm

For x64 desktop devices running Fedora, Rocky Linux, or another distribution using the rpm package system.

Download x64 rpm

ARM desktop devices

Choose these installers only when the processor architecture is confirmed as arm64.

arm64 deb arm64 rpm

Linux system requirements and selection guide

Distribution or device	Architecture	Installer
Debian, Ubuntu family	x64	amd64.deb
Fedora, Rocky Linux family	x64	x86_64.rpm
Debian or Ubuntu ARM device	arm64	arm64.deb
rpm-based ARM device	arm64	aarch64.rpm

CLIENT DECISION

Choosing among the three clients

Choose the platform first, then the core required by the configuration. Use v2rayN on desktop systems; v2rayNG is the default choice on Android, while v2flyNG is for configurations that explicitly require the v2fly core.

v2rayN

A desktop graphical client for Windows, macOS, and Linux. It brings subscription groups, server lists, system proxy, routing rules, and runtime status into one desktop interface, making it suitable for everyday browsing, development testing, and domain-based traffic splitting.

Windows users can choose between Desktop and classic WPF.
macOS installers are separated by Apple Silicon and Intel architecture.
Linux installers are selected by deb, rpm, and processor architecture.

v2rayNG

An Xray graphical client for Android. It supports scanning or pasting subscriptions, updating server lists, per-app proxy settings, and routing rules. For most phones, arm64 is the more direct choice; use the universal version when the architecture cannot be confirmed.

Uses the Xray core.
Suitable for standard subscription and routing configuration.
Provides arm64 and universal installers.

v2flyNG

An Android client built around the v2fly core. It is not a duplicate choice based on UI preference, but an alternative for core-specific requirements. Choose it when configuration documentation explicitly specifies v2fly or when the corresponding implementation must be compared.

Uses the v2fly core.
For specific compatibility and configuration requirements.
Also available as arm64 and universal installers.

INSTALL WORKFLOW

Steps from download to a working connection

Installing the client is only the starting point. Complete the subscription import, server selection, proxy mode setup, and connection check in order; each step has a result you can verify.

Check the platform, architecture, and package type

Windows mainly differs by UI version; macOS by processor; Android by arm64 versus universal; and Linux additionally by deb versus rpm. Confirm the system information first to avoid unsupported package formats or architecture incompatibility.

Expected result: the platform, architecture, and device shown on the download button match.

Complete installation and handle system permissions

On desktop systems, follow the installer prompts to deploy the app; on Android, open the downloaded file and follow the system installation flow. On first launch, the system may request permission for network access, proxy configuration, or a virtual network connection. These permissions let the client handle network requests within the selected scope.

Expected result: the client opens its main interface normally, and menus and settings pages can be opened.

Add a subscription and update the server list

Copy the complete subscription URL, add a new subscription in the client's subscription group, and run an update. After a successful update, server entries are generated from the subscription. If the list remains empty, check that the URL is complete and the device date and time are correct before trying again.

Expected result: selectable configuration entries appear in the server list.

Choose a server and proxy mode

Choose a server first, then configure the system proxy. Common desktop options include enabling automatic system proxy configuration, clearing the system proxy, or leaving it unchanged; Android usually establishes a system-level network tunnel through the connection switch. For everyday use, start with rule-based routing and adjust it as needed when troubleshooting.

Expected result: the client shows an active status, and the system proxy or network connection is enabled.

Check access results and routing direction

Open a browser page that requires the proxy while checking that local or direct services still work as expected. If every request fails, switch servers and update the subscription first; if only some domains fail, inspect the routing rule order and final outbound.

Expected result: proxied and direct requests reach their respective exits according to the current routing rules.

DOWNLOAD FAQ

Common download and installation questions

These questions cover versions, architectures, package formats, and post-installation configuration. When connections fail, first determine whether the issue is with installation, the subscription, or routing.

Should Windows users download v2rayN Desktop or the WPF version?

For a first installation, Desktop is the recommended choice because it uses a modern cross-platform interface. Choose WPF if you prefer the classic Windows interface and want to keep the familiar workflow. Both versions support subscription imports, server selection, system proxy settings, and routing management; installing both is unnecessary.

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 section. Choose Apple Silicon when an Apple M-series chip is shown, and Intel when an Intel processor is listed. The installer architecture must match the device processor; purchase date is only a secondary clue.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 should use arm64 first, as its installer is more compact. Choose the universal version when the architecture is unknown, arm64 fails to install, or older devices need support. Universal means broader architecture coverage, not that it is always the preferred option.

How should I choose between v2rayNG and v2flyNG?

For everyday Android use, start with v2rayNG, which uses the Xray core and provides subscription, routing, and proxy controls. Choose v2flyNG only when v2fly core behavior is specifically required or an existing configuration depends on it. Base the decision on core and configuration requirements, not on running both clients.

What is the difference between Linux deb, rpm, and arm64 installers?

Debian, Ubuntu, and similar distributions generally use deb; Fedora, Rocky Linux, and similar distributions generally use rpm. Choose x64 for standard Intel or AMD computers and arm64 for devices with ARM processors. The distribution package type and processor architecture must both match.

Why can't I connect immediately after installing the client?

The client reads configuration and controls the proxy, but installation alone does not provide a connection. Import a valid subscription or configure a server manually, select an available server, set the system proxy or routing mode, and visit a test page in your browser to verify the traffic path. If the server list is empty, check the subscription update result first.