v2rayN / v2rayNG / v2flyNG

V2Ray Client Downloads

v2rayN covers Windows, macOS and Linux desktops, while v2rayNG and v2flyNG target Android. Switch platforms to see installer links, and each card lists system requirements and setup steps; if you are unsure which one to pick, read the selection notes below.

Windows client

v2rayN ships two archives, the desktop build and the classic WPF build. Protocol support and the core are the same, so pick whichever interface you prefer.

v2rayN

Windows 10 / 11 · 64-bit desktop client

Recommended

The recommended desktop client. VMess, VLESS, Trojan, Shadowsocks and other protocols are managed in one interface, with subscription import, routing rules and the system proxy switch all in the main window. The archive includes the core files, so you can unzip it and run the main program directly with no extra runtime setup.

The desktop build is the new cross-platform interface, sharing one layout with the macOS and Linux builds so settings sit in the same place on all three. The classic WPF build uses the native Windows framework and keeps the older interface, which means less to relearn for long-time users. Both packages are actively maintained, so just pick one for the long run.

Desktop build · x64 Classic WPF build · x64

Current version 7.24.1 · unzip and run v2rayN.exe

System requirements

OS version	Windows 10 / Windows 11 (64-bit)
Processor architecture	x64
Permissions	Run as administrator on first launch to write system proxy settings
Network	A standard network connection that can reach your subscription URL
Disk	Free space for core files and runtime logs

Installation steps

Download the desktop or classic WPF archive and unzip it to a fixed directory, for example D:\v2rayN.
Open the folder and double-click the main program; on first launch, right-click and choose Run as administrator.
Open Subscription → Subscription settings, paste your subscription URL, save, then run Update subscription.
Select a server in the list and switch the system proxy to Automatically configure system proxy.

macOS client

v2rayN offers separate dmg installers for Apple Silicon and Intel chips. Check your chip first so you do not install the wrong architecture.

v2rayN

macOS 11 or later · desktop client

Recommended

It belongs to the same project as the Windows build, with the same layout and settings, and one subscription can be copied across several devices. Open the dmg and drag the app into the Applications folder to install; on first launch, allow it under Privacy & Security as macOS prompts.

Choosing your chip: click the Apple menu in the top-left corner → About This Mac and check the Chip line. Apple M series means the arm64 package, Intel means the x64 package. Both packages work the same way and differ only in build architecture; if you install the wrong one the app will not start, so just download the matching package.

Apple Silicon (M series) Intel chip

Current version 7.24.1 · open the dmg and drag it into Applications

System requirements

OS version	macOS 11 or later
Chip	Apple Silicon takes the arm64 package, Intel takes the x64 package
Installation method	Open the dmg and drag the app into the Applications folder
First launch	Allow it under System Settings → Privacy & Security
Permissions	Confirm the system prompt when writing proxy settings

Installation steps

Check your chip type in About This Mac first, then download the matching dmg file.
Double-click the dmg, drag the app icon into the Applications folder, then eject the disk image.
If macOS blocks the first launch, go to System Settings → Privacy & Security and click Allow.
Add a subscription and update the servers, select one and turn on the system proxy to start browsing.

Android client

Two clients are available for Android: v2rayNG runs on the Xray core and v2flyNG on the V2Fly core. You can install both side by side for comparison.

v2rayNG

Android 8.0 or later · Xray core

Recommended

The recommended Android client, built on the Xray core with support for VMess, VLESS, Trojan and other protocols plus subscription import. Tap a server in the list to switch, choose a routing mode in settings for your use case, and grant the VpnService permission on first connection — a persistent notification appears in the status bar.

Choosing an architecture: mainstream devices released after 2015 are almost all arm64, so the arm64-v8a package is smaller and more efficient. For older or unknown hardware, choose the universal build, which bundles several native libraries and covers more devices. Add the client to your battery optimization whitelist so the system does not kill it in the background and drop the connection.

arm64-v8a · mainstream devices from 2015 onward Universal build

Current version 2.2.6 · VpnService permission required on first connection

v2flyNG

Android 8.0 or later · V2Fly core

Alternative

An alternative client built on the V2Fly core, with an interface and workflow close to v2rayNG; subscription URLs and settings carry over between the two. When one of them has compatibility trouble on a particular device, switching to the other is the first troubleshooting step.

The two clients use different package names, so they can be installed on the same device and tested with the same subscription. If both behave the same way, the problem is most likely on the server side rather than the client side. For everyday use, keep just one of them.

arm64-v8a · mainstream devices from 2015 onward Universal build

Current version 1.10.31 · installs alongside v2rayNG

System requirements

OS version	Android 8.0 or later
Processor architecture	arm64-v8a for mainstream devices from 2015 onward; universal if unsure
Permissions	VpnService permission required on first connection; a persistent notification appears in the status bar
Background running	Add it to the battery optimization whitelist to avoid being killed
Network	A standard network connection that can reach your subscription URL

Installation steps

Download the arm64-v8a or universal installer and save it to your phone storage.
Allow Install unknown apps for the current source in system settings, then open the installer to finish.
Open the client, add your subscription URL under Subscription group and update; the server list is generated automatically.
Accept the VpnService authorization request on first connection; a persistent notification in the status bar means the connection is up.

Linux client

v2rayN ships deb and rpm packages covering Debian-based and Red Hat-based distributions. x64 is the main option, with arm64 available through the smaller link.

v2rayN

Linux desktop · x64 and arm64

Recommended

It belongs to the same project as the Windows and macOS builds, with the same interface and settings. Use deb on Debian, Ubuntu and Linux Mint, and rpm on Fedora, RHEL and openSUSE; installs, upgrades and removals are all tracked by the package manager, which suits long-term use.

After installation, open v2rayN from the application menu or launcher; importing a subscription, selecting a server and enabling the system proxy work the same way as on the desktop build. A graphical desktop (X11 or Wayland) is required — a headless server environment is not a good fit for this graphical client.

deb package · Debian / Ubuntu (x64) rpm package · Fedora / RHEL (x64)

arm64 installers: deb package rpm package

Current version 7.24.1 · launch from the application menu after installing

System requirements

Distribution	deb：Debian / Ubuntu / Linux Mint；rpm：Fedora / RHEL / openSUSE
Processor architecture	x64 is the main option; arm64 installers are also available
Desktop environment	A graphical desktop (X11 or Wayland) is required
Permissions	Authorize the prompt from your distribution when writing proxy settings
Dependencies	Follow the package manager prompts to install any missing runtime libraries

Installation steps

First identify your distribution family: run cat /etc/os-release in a terminal and check the ID and ID_LIKE fields.
Download the deb or rpm package for your family — use the buttons above for x64 devices and the smaller link below for arm64.
Install with your package manager: sudo dpkg -i package.deb on Debian-based systems, sudo dnf install ./package.rpm on Red Hat-based systems.
Launch v2rayN from the application menu, import your subscription, select a server and enable the system proxy.

Package formats

Four package formats for four kinds of systems

Check the file extension before downloading and you save yourself a wasted install.

ZIP · Windows

The Windows package for v2rayN is an archive: unzip it to a fixed directory and run the main program. The program, core and configuration all stay in that directory, so you can copy the whole folder to a new machine and keep going.

DMG · macOS

A disk image format. Open it, drag the app into Applications, then eject the image. Configuration files live in your user directory, so replacing the app itself does not affect subscriptions you have already imported.

DEB / RPM · Linux

Two distribution package formats. deb goes to Debian-based package managers and rpm to Red Hat-based ones; installs, upgrades and removals are all recorded by the package manager, so version state is easy to see.

APK · Android

Android installers. arm64-v8a matches mainstream devices from recent years, while the universal build bundles several native libraries for broader compatibility with older hardware. Both clients can be installed on the same device.

Selection

Pick a client by platform

Three clients cover four kinds of systems: one project handles all three desktop platforms, and Android gets an extra alternative.

Windows / macOS / Linux v2rayN — one project covers all three desktop platforms, with the same interface and settings, and one subscription can be copied to several devices; the desktop and classic WPF builds work the same, so pick by interface preference.
Android first choice v2rayNG — built on the Xray core with full protocol coverage; subscription management and server switching happen in one screen, making it the default pick for Android.
Android alternative v2flyNG — built on the V2Fly core with a workflow close to v2rayNG, useful for comparison when troubleshooting compatibility; for everyday use, keep just one of the two.

Compare all three clients →

Next steps

Three steps after downloading

Installing is only the beginning — importing a subscription is what makes it usable.

Import a subscription: add your subscription URL in the client and run an update; the server list is generated automatically, with no need to add entries by hand.
Choose a mode: switch between system proxy, routing rules or TUN mode for your use case; routing rules decide which traffic goes through the proxy and which connects directly.
Verify the connection: open a browser and visit any page to confirm traffic is being forwarded by the rules you chose; if something goes wrong, check the log page for the error line.

Full setup guide → Configuration file field reference →

Download FAQ

Six questions about downloading and installing

Package choice, architecture, permissions and upgrades are where people get stuck before and after downloading.

Desktop build or classic WPF build of v2rayN: which should you choose?

Both packages belong to the same project, with the same protocol support and core, and both are actively updated. The desktop build is the new cross-platform interface with one shared layout across Windows, macOS and Linux, so settings sit in the same place on all three; the classic WPF build uses the native Windows framework and keeps the older interface, which means less to relearn for long-time users.

Pick the desktop build for the new interface, or the WPF build to keep your familiar workflow — choose one for the long run rather than keeping both.

Should Android phones download arm64 or the universal build?

Mainstream devices released after 2015 are almost all arm64, so the arm64-v8a package is the first choice: smaller and more efficient. For older or unknown hardware, choose the universal build, which bundles several native libraries and covers a wider range of devices.

Both Android clients offer these two packages; if you pick the wrong one, just reinstall with the other package — subscriptions you have already imported are not lost.

How do I know which macOS package to download?

Click the Apple menu in the top-left corner, open About This Mac and check the Chip line: Apple M series means the arm64 package, Intel means the x64 package. The two packages have identical interfaces and features; only the build architecture differs.

If you install the wrong architecture the app will not start; download the matching package and replace it, and your subscriptions and settings stay intact.

deb or rpm on Linux: which one?

It depends on the distribution family: Debian, Ubuntu and Linux Mint use the deb package, while Fedora, RHEL and openSUSE use the rpm package. If unsure, run cat /etc/os-release in a terminal and check the ID and ID_LIKE fields.

Use the two buttons at the top of the card for x64 devices and the smaller link below it for arm64; both architectures work the same.

Do I need to install a core separately after downloading?

No. The v2rayN package already includes the core files it needs; v2rayNG uses the Xray core and v2flyNG uses the V2Fly core, called automatically when the client starts, so everything for everyday use can be done from the graphical interface.

Swapping the core manually is an advanced task that involves matching configuration file fields, and it is not needed for everyday use.

Will upgrading overwrite my existing configuration?

Unzip or install the new package into the same directory and the client keeps reading your existing configuration files, so subscriptions and servers usually do not need to be added again.

To be safe, copy the configuration directory as a backup before upgrading so you can roll back to the previous version quickly if something goes wrong.