Client installers · Four platforms

V2Ray client downloads and platform selection

Choose v2rayN for desktop platforms and v2rayNG for Android. Confirm your operating system and processor architecture before downloading the matching installer.

Desktopv2rayN Android first choicev2rayNG Android alternativev2flyNG Platforms4

Platform switcher

Choose an installer by operating system

When you switch platforms, the page URL updates to the corresponding anchor. Returning to this page restores the platform you selected.

Windows

Windows download: v2rayN

The same client is available in Desktop and classic WPF editions. For a first installation, start with the Desktop edition. If you are familiar with the traditional Windows interface and its existing settings paths, you can continue using the classic WPF edition.

WINDOWS · X64

Recommended Windows

v2rayN

7.24.1

v2rayN is the primary GUI client for Windows desktops. The Desktop edition uses a modern cross-platform UI, with an interaction structure closer to the macOS and Linux versions. The classic WPF edition retains the established Windows interface, with menus that are more consistent with earlier releases. The two installers represent different interface paths; you do not need to install both.

Recommended Desktop edition

Best for first-time installations and users who want a modern cross-platform interface. The package is an x64 ZIP-wrapped installer.

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download Desktop edition

Classic interface Classic WPF edition

Best for users already familiar with v2rayN's traditional menus, subscription groups, and system proxy workflow.

v2rayN-Setup-x64-7.24.1.zip

Download classic WPF edition

Windows requirements and selection guide

Check	Recommendation	Instructions
Processor architecture	`x64`	Both available Windows installation options target 64-bit x86 processors.
First installation	Desktop edition	Start with the modern cross-platform UI so the workflow is easier to follow when moving between desktop operating systems later.
Existing workflow	Classic WPF edition	Keeps the traditional Windows menu logic, making it easier to follow older guides for subscription, routing, and system proxy settings.
Switching editions	Exit the current program first	Before changing interface editions, exit the running v2rayN and note where your subscriptions and custom settings are stored.

macOS

macOS download: v2rayN

The macOS installers are split between Apple Silicon and Intel architectures. Both provide the same client features; only the compilation target differs. Check your device chip first, then choose the matching DMG file.

MACOS · DMG

Recommended macOS

v2rayN

7.24.1

The v2rayN Desktop edition uses a cross-platform GUI on macOS, bringing subscription imports, configuration selection, routing settings, and runtime status into one client. The most important step before installation is identifying the chip type: Apple M-series devices use the arm64 file, while Intel processors use the x64 file. Choosing the wrong architecture may prevent the installer from running.

Apple M-series Apple Silicon arm64

For devices whose System Information shows an Apple M-series chip.

v2rayN-arm64.dmg

Download Apple Silicon edition

Intel processor Intel x64

For devices whose System Information explicitly shows an Intel processor.

v2rayN-64.dmg

Download Intel edition

macOS chip check and installation steps

Where to check	What it shows	Matching installer
Chip field in System Information	Apple M-series	`arm64 DMG`
Processor field in System Information	Intel	`x64 DMG`
Installation method	Open the DMG	Follow the window instructions to move the app to the Applications folder, then launch it from Applications.
First launch	System security prompt	Confirm this launch on the Privacy & Security page in System Settings, then return to the client to continue configuration.

Android

Android download: v2rayNG and v2flyNG

Install v2rayNG first. Choose v2flyNG only when you need a v2fly core implementation. Both clients offer arm64 and universal builds; mainstream phones released after 2015 can usually start with arm64.

ANDROID · APK

Recommended Android

v2rayNG

2.2.6

v2rayNG is the preferred client for Android and uses the Xray core. Common tasks include scanning QR codes, importing configurations from the clipboard, adding subscription groups, updating subscriptions, and starting the system VPN service. For a first installation, try the arm64 build first. If you cannot confirm the device architecture or installation reports incompatibility, use the universal build.

Mainstream devices arm64 build

For most 64-bit ARM phones and tablets released after 2015.

v2rayNG_2.2.6_arm64-v8a.apk

Download v2rayNG arm64 build

Architecture compatibility Universal build

For cases where the processor architecture is unknown or the arm64 installer does not match the device.

v2rayNG_2.2.6_universal.apk

Download v2rayNG universal build

Alternative Android

v2flyNG

1.10.31

v2flyNG uses the v2fly core and serves as an alternative Android client. Consider it only when the subscription notes, server configuration, or usage requirements explicitly target the v2fly ecosystem. The everyday rule is simple: use v2rayNG when unsure, and choose v2flyNG only when a v2fly core is specifically required.

v2fly core arm64 build

For mainstream 64-bit ARM Android devices; the package is built for the corresponding architecture.

v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Download v2flyNG arm64 build

Architecture compatibility Universal build

Use this when the device architecture is unknown. Before installation, confirm that the system allows the downloaded APK file to open.

v2flyNG_1.10.31-fdroid_universal.apk

Download v2flyNG universal build

Android installer selection table

Use case	Client	Package
First installation or regular subscriptions	v2rayNG	Start with `arm64`; switch to the universal build if it does not match the device.
v2fly core explicitly required	v2flyNG	Check for arm64 first, then decide whether the universal build is needed.
Processor architecture unknown	Choose based on the client requirement	Download the universal build for the corresponding client; do not mix up application names.
Start the connection service	Run one client at a time	After importing a configuration, start the VPN service only for the client currently in use to prevent the service states from overriding each other.

Linux

Linux download: v2rayN

For Linux, first choose deb or rpm based on the distribution's package system, then choose x64 or arm64 based on the processor. Do not determine the package format solely from the desktop environment's appearance.

LINUX · DEB / RPM

Recommended Linux

v2rayN

7.24.1

The v2rayN Linux Desktop edition provides deb and rpm packages. Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions generally use rpm. Most standard desktop computers use x64, while ARM devices use arm64.

Debian-based x64 deb

For common x64 Debian, Ubuntu, and derivative distributions.

v2rayn_7.24.1_amd64.deb

Download x64 deb

RPM-based x64 rpm

For common x64 Fedora, Rocky Linux, AlmaLinux, and similar distributions.

v2rayN-7.24.1-1.el10.x86_64.rpm

Download x64 rpm

arm64 packages

Choose these only when the system architecture shows aarch64 or arm64.

Download arm64 deb Download arm64 rpm

Linux package and architecture reference

System information	File to choose	How to tell
Debian, Ubuntu, and derivatives	`deb`	The system uses the Debian package management system.
Fedora、Rocky Linux、AlmaLinux	`rpm`	The system uses the RPM package management system.
`x86_64` or `amd64`	`x64`	Common Intel or AMD 64-bit desktop and laptop processors.
`aarch64` or `arm64`	`arm64`	64-bit ARM devices; choose deb or rpm based on the distribution.

Selection rules

Client, format, and architecture mapping

Downloads are selected in three layers: choose the client, choose the operating system, then verify the processor architecture or package format.

Choose the client based on the device

Use v2rayN on Windows, macOS, and Linux. For a first Android installation, use v2rayNG; choose v2flyNG only when a v2fly core implementation is explicitly required. The client name determines the configuration interface, core implementation, and update path, so do not choose solely by package size.

Choose the architecture based on the processor

macOS distinguishes Apple Silicon from Intel; Android mainly distinguishes arm64 from universal; Linux distinguishes x64 from arm64. The currently available Windows Desktop and classic WPF editions both target x64. A processor mismatch may prevent the installer from starting.

Confirm the file format last

macOS uses DMG and Android uses APK. Linux also requires choosing deb or rpm based on the distribution. The two Windows entries represent the Desktop and classic WPF editions, not duplicate links to the same file. Check the filename before downloading to avoid repeating the process after choosing the wrong installer.

Import configuration after installation

Installing the client does not automatically add subscriptions or server configurations. Next, add a subscription URL or import a single configuration, update the subscription group, select a configuration, and start the system proxy or VPN service for your platform. See the usage tutorial for detailed instructions.

View the complete tutorial →

Installation workflow

From download to first connection

The installer only deploys the client. Subscriptions, configuration selection, and proxy mode must be completed after the first launch.

Verify the download

Confirm the current platform, client name, processor architecture, and file extension. The notes above each download button describe the primary compatibility range, while the requirements table covers edge cases. Do not apply another platform's installation method to this device.

Complete the client installation

Follow the installer prompts on Windows; open the DMG and move the app to Applications on macOS; open the APK and follow the system installation flow on Android; on Linux, install the deb or rpm package with the package manager that matches the distribution.

Add a subscription or configuration

After copying the subscription URL, add an entry under the client's subscription groups and update it. Individual VMess, VLESS, Trojan, or Shadowsocks configurations can be imported from the clipboard, a QR code, or manual fields; the exact entry point depends on the client interface.

Select a configuration and start

After the subscription update completes, select the item you want to use from the configuration list. On desktop platforms, set the system proxy or routing mode according to your needs; on Android, start the client's VPN service. Stop the previous client before switching to another one.

Download FAQ

Common installer questions

These answers cover edition choices, chip architectures, file formats, and initial configuration issues.

Should you choose the v2rayN Desktop edition or the classic WPF edition on Windows?

The Desktop edition uses a modern cross-platform interface for users who want a consistent desktop experience. The classic WPF edition retains familiar Windows layouts and settings paths for users accustomed to the legacy interface. Both are v2rayN; for a first installation, the Desktop edition is recommended. After choosing, run only one edition to prevent their system proxy states from overriding each other.

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

Open System Information and check the chip or processor field. If it shows an Apple M-series chip, choose the Apple Silicon arm64 installer; if it shows an Intel processor, choose the Intel x64 installer. The architecture must match the device processor; the model name and physical appearance are not reliable indicators.

What is the difference between the arm64 and universal Android builds?

The arm64 build targets mainstream 64-bit ARM devices and focuses its contents on the corresponding processor architecture. Most mainstream phones released after 2015 can start with arm64. If you cannot confirm the architecture or the arm64 package will not install, switch to the universal build. The universal build broadens architecture compatibility; it does not provide more client features.

Which should you choose: v2rayNG or v2flyNG?

For a first Android installation, choose v2rayNG. It uses the Xray core and supports a broad range of common subscription formats and protocols. v2flyNG uses the v2fly core and is an alternative when you need that ecosystem. Do not start VPN services in both clients; stop the current connection before switching apps.

Should you choose a deb or rpm package on Linux?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions. You must also distinguish between x64 and arm64 processor architectures. Package format and processor architecture are independent conditions, and both must match.

What configuration is needed after installation?

After installing the client, import a working subscription URL or a single configuration, update the subscription group, select a configuration, and enable the system proxy or VPN service for your use case. The installer itself does not include subscriptions or server configurations. If you already have a subscription, save its URL first, then add and update it in the client.