CLIENT DOWNLOADS / CHOOSE BY DEVICE
For desktop, choose v2rayN. On Android, start with v2rayNG; choose v2flyNG if you need a client with the V2Fly core. Check your operating system and processor architecture before selecting a package.
Choose an operating systemPLATFORM / DOWNLOADS
Your platform selection stays in the page URL, so you can return directly to the matching downloads next time.
WINDOWS / DESKTOP
One client, two interface options. Choose the one you prefer; there’s no need to install both for your first setup.
v2rayN is a desktop client for importing subscriptions, managing servers, and adjusting settings such as routing and the system proxy. The Desktop edition uses a newer cross-platform UI, while WPF retains the classic Windows interface. Choose based on your interface preference, not your subscription type. Have your subscription link or server settings ready before configuring the client.
| Check | What to do |
|---|---|
| Operating system | Make sure you’re running Windows and can install desktop applications. |
| Processor | Both Windows downloads on this page are x64. Check your system type in Windows Settings. |
| Configuration | After installation, you’ll need an existing subscription link or server settings. |
If your system type is listed as 32-bit, check your device and package architecture first; x64 files are not universal installers. If the download is an archive, extract it before following the installation steps for the included program. On first launch, import your subscription and select a server before checking the system proxy setting.
MACOS / DESKTOP
Open About This Mac from the Apple menu and check the chip or processor name before choosing a dmg.
The macOS version follows the same setup flow as v2rayN: add a server or import a subscription, select a server, then adjust the proxy mode as needed. Apple Silicon and Intel packages are built for different processors, so don’t guess based on the device’s release year. Check the chip in About This Mac to avoid downloading an incompatible package.
| Check | What to do |
|---|---|
| Chip | Apple M-series chips require the Apple Silicon package; Intel processors require the Intel package. |
| File format | Open the downloaded dmg disk image and follow the system prompts to install the app. |
| Network permissions | If you need the system proxy or related network features, review and confirm any permission prompts shown by macOS. |
System permission prompts and the client’s connection status are separate things. If the app launches, it’s installed; whether your browser connects as expected also depends on the selected server, proxy mode, and system proxy. If the app still won’t open after you switch packages, recheck the chip name and system prompts. Reimporting the same subscription won’t fix an installation issue.
ANDROID / MOBILE
The clients are listed in order. Start with v2rayNG; choose v2flyNG if you need an Android client with the V2Fly core.
v2rayNG is an Android graphical client powered by the Xray core. Use it to import subscriptions, switch servers, and manage connections on your phone. In most cases, start with arm64: mainstream Android phones released since 2015 generally use 64-bit ARM processors. If you’re unsure of your device’s architecture or see an architecture mismatch during installation, choose the universal package instead.
v2flyNG is an Android graphical client built on the V2Fly core. It’s a separate app from v2rayNG, not another processor variant. Choose it if your configuration is intended for the V2Fly core or you’re comparing compatibility between the two cores. As with any Android app, select arm64 or universal based on your phone’s architecture.
| Check | What to do |
|---|---|
| Device architecture | Choose arm64 if you’ve confirmed your device uses 64-bit ARM; otherwise, choose universal. |
| File format | Download the apk and follow the prompts on your device to install it. |
| Client | v2rayNG uses the Xray core; v2flyNG uses the V2Fly core. |
When installing an apk, Android may ask you to allow your file manager to install apps. Review the permission prompt for the installation you’re performing. After installation, open the client to make sure it loads before importing an existing subscription. If you install both clients, check subscriptions and connection status in each one; server lists aren’t automatically shared between apps.
LINUX / DESKTOP
Check whether your distribution uses deb or rpm, then choose x64 or arm64 for your processor.
Linux package selection depends on two things: your distribution’s package format and your processor architecture. Distributions such as Debian and Ubuntu generally use deb; Fedora and RHEL generally use rpm. For common x64 desktop systems, start with the two main downloads below. ARM devices should use the arm64 packages listed next. Once installed, import your configuration in the graphical client.
If your processor is arm64, choose the package format for your distribution. Don’t download the x64 packages above.
| Check | What to do |
|---|---|
| Package format | First check whether your distribution uses deb or rpm packages. |
| Processor architecture | Check whether your system reports x64 or arm64, then choose the matching package. |
| Desktop environment | Make sure your device has a desktop environment for running graphical clients. |
If your package manager reports an architecture mismatch, recheck the processor architecture rather than trying another file based only on its extension. Even deb packages for x64 and arm64 aren’t interchangeable; the same applies to rpm. If the client installs but connections don’t work as expected, check that it’s running, a server is selected, and the system proxy is configured before switching package formats.
BEFORE INSTALLING / HOW TO CHOOSE
For Windows, macOS, and Linux desktops, start with v2rayN. For Android, start with v2rayNG; v2flyNG is another Android client that uses the V2Fly core. The client name and package architecture are separate choices: one client may have several downloads.
Check your processor in system information, then choose x64, Apple Silicon, or arm64. The Android universal package is an option if you can’t confirm your architecture. On Linux, also check the distribution’s package format: choosing the right processor architecture but the wrong deb or rpm package won’t work.
After downloading and launching the client, import your subscription link or enter your server settings. The installer doesn’t provide servers. First confirm the app opens, then import your configuration, select a server, and check the proxy mode. This makes it easier to tell whether a problem is with installation, configuration, or the system proxy.
The quick-start guide walks you through importing a subscription, choosing a server and mode, and checking the connection. Follow the steps in order for your first setup, then consult troubleshooting for specific errors.
DOWNLOAD FAQ / COMMON QUESTIONS
These answers focus on choosing an installer. For subscriptions, routing, and connection issues after launch, see the guide or help center.
Choose Desktop for the newer cross-platform interface, or WPF for the classic Windows interface. Both are v2rayN; install either one to get started. You don’t need both packages just to import an existing subscription. Install and configure one version first to make it easier to pinpoint any issues.
Check the chip listed in About This Mac. Choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. Don’t guess based on the device’s appearance, purchase date, or macOS version. Confirm the chip before downloading to avoid reinstalling the app.
The arm64 package is for 64-bit ARM devices, which includes most mainstream phones released since 2015. If you’re unsure of your device’s architecture or see an architecture mismatch during installation, choose universal. These are different builds of the same client. Choose v2rayNG or v2flyNG first, then select one of that client’s two packages.
Choose deb for distributions such as Debian and Ubuntu, or rpm for Fedora, RHEL, and other rpm-based distributions. Also select x64 or arm64 to match your processor. The package format and architecture must both match; an arm64 deb won’t work as an x64 deb. If you’re unsure which format your distribution uses, check its package management system.
Install the graphical client for your operating system, then follow the quick-start guide to import an existing subscription or server settings, select a server, and check your system proxy. The installer doesn’t include server settings. If the client opens but won’t connect, check your subscription, server, and proxy settings before downloading the same installer again.
Questions about subscription updates or proxy settings? Visit the help center →