Installer Downloads

V2Ray Client Download

The page lists installer downloads for v2rayN, v2rayNG and v2flyNG across Windows, macOS, Android and Linux, with the architecture and file format noted for each entry. v2rayN is the first choice on desktop, v2rayNG on Android, and v2flyNG stays available as an alternative with the v2fly core. Check your device architecture before downloading, then install according to the system requirements.

3 clients · 4 platforms · Xray / V2Fly cores · GPL-3.0 open source license

Platform List

Get installers by platform

The client list for the four platforms is fixed: Windows, macOS and Linux use v2rayN, Android uses v2rayNG, and v2flyNG is the option when the v2fly core is needed. Switch to a tab to see that platform's installers, system requirements and installation notes.

Windows Platform

Windows offers one client, v2rayN, split into two packages by UI framework: the desktop edition and the classic WPF edition. Both share the same subscription and routing configuration, so settings carry over when you switch. The download is a zip archive; extract it and run the main program inside the folder.

v2rayN

Windows / macOS / Linux

Top Pick Xray Core zip

The main desktop client, with subscription import, node speed tests, routing rules and system proxy switching, plus the Xray core built in. The two packages below differ only in interface style; features and configuration format are the same.

Desktop Edition

Modern UI

Built on a cross-platform UI framework; interface updates and new features land here first, which suits new users.

Version 7.24.1 v2rayN-Desktop-Setup-x64-7.24.1.zip

Download Desktop Edition (x64)

Classic WPF Edition

Classic & Stable

Keeps the older WPF layout, maintained long term and consistent in behavior; suits users who are used to the old interface or follow older tutorials.

Version 7.24.1 v2rayN-Setup-x64-7.24.1.zip

Download Classic WPF Edition (x64)

System Requirements

v2rayN system requirements on Windows
OS version	Windows 10 version 1809 or later, Windows 11
CPU architecture	x64 (64-bit)
Installation method	zip archive; extract it and run the main program in the folder
Disk space	A few hundred MB for program files and subscription cache
Permissions	Switching the system proxy writes to system settings; virtual network adapter mode requires administrator privileges

Installation Notes

Extract the archive into your user folder rather than a system path that needs administrator rights. If the browser shows no change after switching the system proxy, quit any other proxy tools that are running first; several tools writing the system proxy setting at once will overwrite each other.

macOS Platform

macOS also uses v2rayN; the package is a dmg disk image, so open it and drag the app into the Applications folder. The macOS and Windows builds share the same configuration format, and subscription links and routing rules carry over directly. Two packages are provided by chip architecture, so check your model before downloading.

v2rayN

macOS / Windows / Linux

Xray Core dmg Dual Architecture

A desktop client that lives in the menu bar, with subscription import, node switching, routing rules and system proxy support. The dmg packages are split by chip architecture; the two entries below cover Apple Silicon and Intel Macs.

Apple Silicon(arm64)

M-series chips

For Macs with M1 and later M-series chips; runs natively with faster startup and lower power draw.

Version 7.24.1 v2rayN-arm64.dmg

Download Apple Silicon version

Intel(x64)

Intel chips

For Macs with Intel processors; M-series Macs can run it through translation, but performance and power draw are worse than the native build.

Version 7.24.1 v2rayN-64.dmg

Download Intel version

System Requirements

v2rayN system requirements on macOS
OS version	macOS 11 or later
Chip architecture	Apple Silicon (arm64) or Intel (x64)
Installation method	Open the dmg and drag the app into the Applications folder
First launch	If the developer cannot be verified, allow it under System Settings → Privacy & Security
Permissions	Changing the system proxy requires user authorization; quit any older version before the first run

Installation Notes

Quit any running older version before installing the new one, so two instances do not write the system proxy at the same time. When switching between architecture builds, close the old version first; you can keep using your configuration by importing the subscription again in the new version.

Android Platform

Android offers two clients, v2rayNG and v2flyNG. The first uses the Xray core, the second the v2fly core, and their interfaces and workflows are similar. For everyday use, v2rayNG comes first; pick v2flyNG if you already have v2fly core configurations or need to compare core behavior. Both packages are APKs, so download and install directly.

v2rayNG

Android

Top Pick Xray Core apk

The most widely used V2Ray client on Android, with subscription import, node grouping, latency tests and per-app proxy. The packages come in two entries by processor architecture: arm64 and universal.

arm64 version

Mainstream devices

For mainstream phones and tablets released after 2015, which almost all use 64-bit processors; the package is smaller.

Version 2.2.6 v2rayNG_2.2.6_arm64-v8a.apk

Download arm64 version

Universal version

Compatibility first

Includes both 32-bit and 64-bit libraries, for older devices or when the processor architecture is unknown; the package is larger.

Version 2.2.6 v2rayNG_2.2.6_universal.apk

Download universal version

v2flyNG

Android

Alternative v2fly Core apk

An Android client built on the v2fly core, with a feature layout close to v2rayNG. It suits users who already have v2fly core configurations or need to compare behavior against v2fly; if you have no specific requirement, use v2rayNG.

arm64 version

Mainstream devices

For phones and tablets released after 2015 with 64-bit processors.

Version 1.10.31 v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Download arm64 version

Universal version

Compatibility first

Includes both 32-bit and 64-bit libraries, for older devices or when the processor architecture is unknown.

Version 1.10.31 v2flyNG_1.10.31-fdroid_universal.apk

Download universal version

System Requirements

v2rayNG and v2flyNG system requirements on Android
OS version	Android 8.0 or later
CPU architecture	arm64-v8a (most devices) or 32-bit (use the universal build)
Installation method	Install the APK directly
Permissions	The first connection shows a VPN request that must be confirmed in the system dialog
Background activity	Allow background activity for the app in the system battery settings so the connection is not killed

Installation Notes

When installing an APK, the system asks whether to allow apps from that source; confirm to continue. The first connection must be approved in the system VPN request, otherwise the client cannot take over traffic. Some customized systems also restrict background starts separately, which you need to allow in app management.

Linux Platform

Linux uses v2rayN, with deb and rpm package formats to match your distribution's package manager. x86_64 is the main entry point; ARM devices (Raspberry Pi, ARM servers, some ARM laptops) use the secondary entry below. The packages install through the system package manager, and the program itself is the same as the Windows and macOS builds.

v2rayN

Linux / Windows / macOS

Xray Core deb rpm

A desktop client with subscription import, node speed tests, routing rules and system proxy support; start it from the application menu after installing. The deb and rpm packages differ only in package manager; features and configuration format are identical.

deb package (amd64)

Debian-based

For Debian, Ubuntu, Linux Mint and other distributions that use dpkg and apt.

Version 7.24.1 v2rayn_7.24.1_amd64.deb

Download deb package (amd64)

rpm package (x86_64)

Red Hat-based

For Fedora, RHEL, CentOS Stream, openSUSE and other rpm-based distributions.

Version 7.24.1 v2rayN-7.24.1-1.el10.x86_64.rpm

Download rpm package (x86_64)

ARM64 builds

For Raspberry Pi, ARM servers and some ARM laptops; x86_64 devices should use the packages above.

System Requirements

v2rayN system requirements on Linux
OS version	A stable release from the past two years of a mainstream distribution
CPU architecture	x86_64 (amd64) or arm64 (aarch64)
Installation method	Install the deb or rpm package with the system package manager
Desktop environment	A graphical desktop environment (X11 or Wayland) is required
Permissions	Changing the system proxy uses user-level permissions; virtual network adapter mode needs the corresponding authorization

Installation Notes

If the architecture does not match, the package manager refuses to install; switch to the package for your architecture as prompted. If the app icon does not appear in the application menu right after installation, logging out and back in refreshes the menu cache.

Selection Guide

Which of the three clients to choose

All three clients come from the Project V ecosystem, and subscription links and configuration options are largely interchangeable between them; the differences are the platform they run on and the core they bundle. Choose in this order: settle the device platform first, then decide whether you need to stay on the same core family as your existing configuration.

Platform, core and typical use case comparison for v2rayN, v2rayNG and v2flyNG
Client	Platform	Bundled core	Typical use case
v2rayN	Windows / macOS / Linux	Xray	Everyday desktop use, with subscription management, routing, speed tests and logs in one window
v2rayNG	Android	Xray	Everyday phone and tablet use, with per-app routing and per-app proxy
v2flyNG	Android	V2Fly	Existing v2fly core configurations, or when comparing behavior against v2fly

Desktop: v2rayN first

Windows, macOS and Linux share the same desktop client, and configuration files migrate between systems. The desktop interface puts the subscription list, node list, routing settings and runtime log in one window, so you can see the outbound node and the error line while diagnosing problems, which suits long-term, stable use. The classic WPF edition shares the configuration format, so pick whichever interface you prefer.

Mobile: v2rayNG first

On Android, start with v2rayNG: it uses the Xray core, subscription import and node switching are both on the main screen, and you can decide per app which traffic goes through the proxy. v2flyNG uses the v2fly core with a similar workflow, and suits users who already have v2fly configurations or need to compare core differences. Both clients use the same subscription link format, so switching means importing it again.

Installation Flow

Four steps after downloading

Installation differs by platform, but the rest of the flow is the same: import a subscription, choose a node, confirm the proxy mode and verify the connection. The full step-by-step guide with interface references is on the tutorial page.

Install or extract the client

On Windows, extract the zip and run the main program; on macOS, open the dmg and drag the app into Applications; on Android, allow apps from the current source in the system dialog and install the APK; on Linux, install the deb or rpm package for your architecture with the package manager.
Import the subscription link

Copy the subscription address from your provider, create a new subscription in the client's subscription settings and paste it, then run an update once. The node list appears automatically after a successful update; there is no need to add nodes one by one.
Choose a node and proxy mode

Pick a node with a suitable latency from the list, then choose system proxy or routing mode as needed. On desktop you can configure domain routing rules in the settings; on mobile you can decide per app which traffic goes through the proxy.
Verify the connection

Open a browser and load a page to confirm connectivity, and check the client log for errors at the same time. If the connection fails, look at the timestamps and the outbound node in the log first, then narrow the range step by step following the troubleshooting order.

View the full setup guide

Download FAQ

Download and installation FAQ

The questions below focus on choosing and installing packages; for client connections, subscription updates and routing configuration, see the FAQ page and the diagnostics page.

What is the difference between the v2rayN desktop edition and the classic WPF edition?

Both editions share the same configuration format and subscription links; the difference is the UI framework. The desktop edition uses a new cross-platform UI and is where feature updates and interface changes land first, which suits new users. The classic WPF edition keeps the older layout, is maintained long term and behaves consistently, which suits users who are used to the old interface or need to follow older tutorials. When switching editions, just carry over your configuration folder or subscription link; there is no need to set up nodes again.

Should I download the Apple Silicon or Intel version on macOS?

Open About This Mac and check the chip line: Apple M-series (M1 and later) means the Apple Silicon version, Intel means the Intel version. M-series Macs can also run the Intel version through translation, but the native build starts faster and draws less power. Checking the architecture before downloading saves you from swapping packages after installing.

Should I pick the arm64 or universal build for an Android phone?

Mainstream phones released after 2015 almost all use 64-bit processors, so the arm64 build is the right choice and the package is smaller. Only older devices, or cases where the processor architecture is unclear, need the universal build that includes both 32-bit and 64-bit libraries. Both packages offer the same client features; only the bundled libraries differ.

Which should I choose on Linux, deb or rpm?

Check which package manager your distribution uses: Debian, Ubuntu, Linux Mint and similar take deb; Fedora, RHEL, CentOS Stream, openSUSE and similar take rpm. The installed program is the same either way; only the package management differs. ARM devices (Raspberry Pi, ARM servers, some ARM laptops) need the arm64 and aarch64 packages, and the package manager will refuse to install a mismatched architecture.

Do the downloaded packages need a separate core installation?

No. v2rayN bundles the Xray core, v2rayNG also uses the Xray core, and v2flyNG bundles the v2fly core, so you can connect right after importing a subscription. Only advanced cases such as tuning core parameters require knowledge of the core configuration options; the docs page covers those under Protocols.

The downloaded package will not install or open; what should I check first?

First confirm the package matches your device architecture and that your system version meets the requirements. If macOS says the developer cannot be verified, allow it under System Settings → Privacy & Security. On Android, allow apps from the current source in the system dialog when installing. On Windows, if the extracted program reports missing runtime components, install the system components it asks for and run it again. If it still will not open, note the exact error message and work through the symptoms on the diagnostics page.

Next Steps

What to read after installing

Downloading and installing is only the first step; subscription updates, routing and troubleshooting each have their own page.

V2Ray Client Download

Get installers by platform

Windows Platform

v2rayN

System Requirements

macOS Platform

v2rayN

System Requirements

Android Platform

v2rayNG

v2flyNG

System Requirements

Linux Platform

v2rayN

System Requirements

Which of the three clients to choose

Desktop: v2rayN first

Mobile: v2rayNG first

Four steps after downloading

Install or extract the client

Import the subscription link

Choose a node and proxy mode

Verify the connection

Download and installation FAQ

What to read after installing

Setup Guide

FAQ

Diagnostics