Four platforms · Three graphical clients

V2Ray Client Download

Choose a release by operating system, processor architecture, and installer format. Use v2rayN on desktop platforms, and choose between v2rayNG and v2flyNG on Android.

v2rayN 7.24.1 v2rayNG 2.2.6 v2flyNG 1.10.31

Platform installers

Choose your current device

After switching platforms, only the matching client is shown. Download buttons read the version list from the same origin; if the list is temporarily unavailable, the page keeps a direct entry for the current version.

Windows

v2rayN Windows installers

The Desktop and classic WPF editions use different interfaces. For a first installation, Desktop is the preferred choice; users familiar with the classic Windows interface can continue with WPF.

v2rayN

7.24.1

Recommended

v2rayN brings subscription management, node selection, the system proxy, routing rules, and runtime logs into one desktop interface. Desktop is the newer cross-platform UI, with a structure closer to other desktop systems; WPF is the classic Windows edition for users who want to keep their established workflow.

Desktop edition

A modern cross-platform interface, suited to first-time installation and regular updates.

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download the Desktop edition

Classic WPF edition

Keeps the classic Windows interface and established workflows.

v2rayN-Setup-x64-7.24.1.zip

Download the classic WPF edition

Windows system and installation guide

Check	Recommendation	Why it matters
Processor architecture	x64 desktop device	Both Windows installers provided on this page target common x64 desktop environments.
Before installation	Fully quit the old client	Processes in the system tray may still hold configuration files, local ports, or program files being updated.
First launch	Allow required network access	The client needs to create a local proxy listener and, depending on the selected mode, handle application or system network requests.

macOS

v2rayN macOS installers

The main difference between the two DMG installers is processor architecture. Check the chip information in About This Mac first, then choose the matching file.

v2rayN

7.24.1

Desktop client

The macOS edition uses the same cross-platform interface as the newer desktop client, with in-app management for subscriptions, nodes, the system proxy, and routing settings. The Apple Silicon and Intel installers offer the same functionality; the only difference is the device chip.

Apple Silicon

For devices with Apple M-series chips.

v2rayN-arm64.dmg

Download the Apple Silicon edition

Intel

For devices whose processor is listed as Intel.

v2rayN-64.dmg

Download the Intel edition

macOS chip selection and first launch

System information	Choose	Installation guidance
Apple M-series chip	Apple Silicon	Use the arm64 DMG to match the current processor architecture.
Intel processor	Intel	Use the x64 DMG and avoid an installer built for a different processor architecture.
First launch	Review the system security prompt	Follow the system prompts to allow the app to launch and grant network-related permissions, then check the client status in the menu bar.

Android

v2rayNG and v2flyNG installers

v2rayNG is the preferred choice. Choose v2flyNG when you need the V2Fly core. Each client offers arm64 and universal installers.

v2rayNG

2.2.6

Recommended

v2rayNG is a widely used graphical client for Android. It uses the Xray core and supports subscription updates, node groups, routing rules, per-app proxying, and connection logs. Most mainstream phones released after 2015 can start with arm64.

arm64 edition

Suitable for recent mainstream Android phones and tablets.

v2rayNG_2.2.6_arm64-v8a.apk

Download the v2rayNG arm64 edition

Universal edition

Use this when the device architecture is unknown; it supports a wider range of devices.

v2rayNG_2.2.6_universal.apk

Download the universal v2rayNG edition

v2flyNG

1.10.31

Alternative

v2flyNG uses the V2Fly core and follows familiar workflows for mobile proxy clients. It suits users who specifically need V2Fly configuration compatibility. Protocol and transport settings must still match the subscription or server configuration.

arm64 edition

For mainstream 64-bit ARM devices.

v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Download the v2flyNG arm64 edition

Universal edition

For devices with unknown architecture or those unable to install the arm64 edition.

v2flyNG_1.10.31-fdroid_universal.apk

Download the universal v2flyNG edition

Android architecture and installation guide

Option	Suitable for	How to decide
arm64	Mainstream devices released after 2015	Most recent 64-bit ARM phones can try this first, and the package is usually more focused in size.
Universal edition	Unknown architecture or broader compatibility needed	If the device information is unavailable or the arm64 build reports an architecture mismatch, use the universal edition instead.
Client choice	Everyday use or a specific core requirement	Choose v2rayNG for everyday use; choose v2flyNG when you specifically need V2Fly configuration behavior.

Linux

v2rayN Linux installers

Choose deb or rpm for the distribution, then x64 or arm64 for the processor. Common desktop computers usually use x64, while ARM devices use arm64.

v2rayN

7.24.1

Desktop client

The Linux edition uses a cross-platform desktop interface. deb suits Debian, Ubuntu, and derivatives; rpm suits distributions using the RPM package system, such as Fedora, Rocky Linux, and AlmaLinux.

x64 deb

For common Debian and Ubuntu x64 desktop environments.

v2rayn_7.24.1_amd64.deb

Download x64 deb

x64 rpm

For x64 distributions using the RPM package system.

v2rayN-7.24.1-1.el10.x86_64.rpm

Download x64 rpm

arm64 deb v2rayn_7.24.1_arm64.deb Download arm64 deb

arm64 rpm v2rayN-7.24.1-1.el10.aarch64.rpm Download arm64 rpm

Linux package selection table

Environment	Package	Architecture
Debian, Ubuntu, and derivatives	deb	Most standard desktops use x64; choose arm64 for ARM devices.
Fedora, Rocky Linux, AlmaLinux, and similar distributions	rpm	x86_64 corresponds to x64; aarch64 corresponds to arm64.
Processor architecture unknown	Check system information first	Confirm the result before downloading and installing to avoid an architecture mismatch reported by the package manager.

Before you install

A reliable order for downloading, updating, and configuring

Handling installer selection separately from node configuration makes it easier to avoid confusion between architecture, permissions, and proxy status.

STEP A

Confirm the system and architecture

First identify whether the device runs Windows, macOS, Android, or Linux, then check the processor architecture. On macOS, distinguish Apple Silicon from Intel; on Android, distinguish arm64 from universal; on Linux, also choose between deb and rpm package systems. A mismatch may cause the app not to open, an architecture error, or the package manager to reject the installation.

STEP B

Back up existing configuration

If the client is already installed, save the subscription URL, manual nodes, routing rules, and local port settings before updating. Graphical clients can usually retain existing settings, but a quick backup prevents repeated setup after an OS upgrade, directory change, or cross-version migration. Store backups somewhere under your control, and do not share subscription URLs publicly.

STEP C

Quit the old version before installing

Closing the main window does not always end the process. On desktop systems, also check the system tray or menu bar and make sure the old client has fully quit before installing the new version. This releases configuration files, program files, and local listening ports. On mobile devices, wait for the update to finish before reopening the client.

STEP D

Restore the subscription and verify the connection

After launching the client, confirm that the subscription is still present and run a subscription update. Choose a node with complete parameters, enable the system proxy or the client's connection mode, then access a familiar online service to verify resolution and connectivity. If something fails, check the client log and local proxy status first rather than changing several protocol parameters at once.

Recognizing installer files

Architecture and format in file names

Installer names usually include the platform, processor architecture, and file format. Learning these terms makes it easy to rule out releases that do not fit the current device.

x64 / amd64 / x86_64

These names usually refer to common 64-bit desktop processor architectures. Windows and most Intel or AMD desktop computers typically use x64; Linux package names may use amd64 or x86_64.

arm64 / aarch64

Both usually describe 64-bit ARM architectures. Apple M-series chips use arm64; most recent Android phones use the same architecture; Linux RPM file names commonly use aarch64.

DMG / APK

DMG is a common macOS app distribution format; open it and follow the system prompts to install. APK is the Android app package format; follow the source and permission prompts shown by the system.

deb / rpm

These are Linux package formats. deb is common on Debian, Ubuntu, and derivatives; rpm is common on Fedora, Rocky Linux, AlmaLinux, and similar distributions.

Common download questions

Version selection and installation troubleshooting

These questions cover desktop edition choice, chip identification, mobile architecture, Linux packages, and connection checks after an update.

Should you download the Desktop or WPF edition of v2rayN for Windows?

The Desktop edition uses a modern cross-platform interface and suits first-time installations, users who want the newer UI, or anyone who wants a similar workflow across desktop systems. WPF keeps the classic Windows interface for users familiar with its menus, tray controls, and settings paths. Both manage subscriptions, nodes, the system proxy, and routing rules, so installing both is unnecessary. If you have no established preference, start with Desktop.

How do you 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 when an Apple M-series chip is shown, or Intel when an Intel processor is listed. Both installers provide the same client features; the difference is the compilation target. Matching the device architecture can reduce translation overhead and launch problems.

Should you download the arm64 or universal version on Android?

Most mainstream Android phones released after 2015 can use the arm64 version first. The arm64 file targets common 64-bit ARM devices and is more focused in size. Choose universal if the architecture is unknown, the device is older, or the system reports that the arm64 package is incompatible. Universal supports more architectures and may therefore be larger.

Should you choose deb or rpm on Linux?

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and similar distributions generally use rpm. After identifying the format, check the processor architecture: standard Intel and AMD desktops commonly use x64, while ARM single-board computers and some ARM desktops use arm64. Both the distribution format and processor architecture must match.

Do you need to delete existing subscriptions before installing a new version?

Usually not. Before updating, export or record the current configuration and fully quit the old client. After installation, check the subscription list, current node, system proxy status, local listening port, and routing mode. For an update spanning several major versions, backing up first is the safer approach.

What should you check first if nodes are present but cannot connect after installation?

Manually update the subscription first and confirm that all node parameters loaded correctly. Then check the system time, client runtime status, and whether the system proxy or connection mode is enabled. A local listening port occupied by another program can also prevent the browser from connecting through the proxy. If only one node fails, try another node from the same subscription to distinguish a node-side issue from a local setting.