Choose by platform and system architecture

V2Ray Client Download

Use v2rayN on Windows, macOS, and Linux; choose v2rayNG for Android in most cases, and consider v2flyNG when you specifically need the V2Fly kernel route. Confirm the operating system, processor architecture, and edition before downloading.

GUI clients Platform installers System requirements Architecture selection

Choose a Download Platform

Switching platforms displays the matching client, installer links, and system requirements. The platform marker in the address bar can return you to the current category.

Desktop platforms

Windows client

Choose the x64 installer for standard 64-bit Windows PCs. v2rayN offers Desktop and classic WPF editions; their interfaces differ, but both manage subscriptions, nodes, system proxy settings, and routing rules.

v2rayN

Windows · x64 · 7.24.1

Recommended

For a first installation, start with the Desktop edition. It uses a modern cross-platform interface with menus and settings organized for current desktop use. The classic WPF edition keeps the traditional Windows interface for users familiar with its existing menu locations and workflow. The client edits and manages configuration; after installation, you still need to import a subscription or individual server parameters.

Preferred choice

Desktop edition Desktop

A modern cross-platform interface for first-time installations and users who want a consistent desktop experience.

Download Desktop edition

Alternative edition

Classic WPF edition

Keeps the classic Windows interface for users familiar with its existing menus and settings workflow.

Download classic WPF edition

Windows requirements and selection guide

Check	Recommendation	Why it matters
System architecture	Choose x64 for 64-bit Windows	The Windows packages on this page target x64 processor environments.
Interface edition	Prefer Desktop for new installations	Desktop uses a cross-platform UI; WPF keeps the classic interface.
Before updating	Exit the client and back up configuration	Prevent running files from being locked and preserve subscriptions, routes, and custom settings.
After installation	Import a subscription before choosing proxy mode	Installing the client does not connect applications to a proxy automatically; configuration is still required.

Desktop platforms

macOS client

macOS uses the v2rayN Desktop client. Confirm the chip type before downloading: choose the Apple Silicon installer for Apple M-series chips and the Intel installer for Intel processors. A mismatched architecture may prevent installation or startup.

v2rayN

macOS · DMG · 7.24.1

Desktop client

The two links target different processor architectures but provide the same client functionality. Open About This Mac or System Information and check the Chip or Processor field: choose arm64 for an Apple M-series name and x64 for an Intel name. Do not rely only on the device’s appearance or purchase year; system information is more accurate.

M-series chip

Apple Silicon · arm64

For devices with Apple M-series chips, which are common in newer Macs.

Download Apple Silicon edition

Intel processor

Intel · x64

For devices whose system information explicitly lists an Intel processor.

Download Intel edition

macOS requirements and selection guide

System information	Installer	Instructions
Apple M-series chip	Apple Silicon · arm64	Choose v2rayN-arm64.dmg.
Intel processor	Intel · x64	Choose v2rayN-64.dmg.
First launch	Approve app permissions as prompted	Proxy settings and network extensions may require system authorization.
Application connectivity	Check browser and terminal settings separately	The system proxy does not automatically cover every command-line program.

Mobile platforms

Android client

Prefer v2rayNG with the Xray kernel route; choose v2flyNG when you need the V2Fly kernel route. Both clients offer arm64 and universal builds, and most mainstream phones released after 2015 should generally use arm64.

v2rayNG

Android · Xray kernel · 2.2.6

Recommended

v2rayNG is the main choice on Android. Its GUI handles subscription imports, configuration switching, routing, and per-app proxying, while the Xray kernel handles connections. On first launch, approve the system VPN connection request. If another VPN-style app is already running, resolve the conflict before starting the client.

Mainstream phones

arm64 build

Suitable for most mainstream phones and tablets released after 2015, with a package optimized for the common 64-bit ARM architecture.

Download v2rayNG arm64

Architecture compatibility

Universal build

Choose this when the architecture is unknown, the arm64 installation fails, or the device is older.

Download v2rayNG universal build

v2flyNG

Android · V2Fly kernel · 1.10.31

Alternative

v2flyNG is for Android users who need the V2Fly kernel route. Confirm that your existing subscription or manual configuration matches the required kernel capabilities before choosing it; do not switch solely based on the client name. Without a specific kernel requirement, start with v2rayNG above. Choose v2flyNG when you need to keep an existing V2Fly configuration consistent.

Mainstream phones

arm64 build

For common 64-bit ARM devices; choose this when the processor architecture is confirmed.

Download v2flyNG arm64

Architecture compatibility

Universal build

For unclear architecture information or when broader device compatibility is needed.

Download v2flyNG universal build

Android requirements and selection guide

Check	Recommendation	Details
Client	Usually choose v2rayNG	Choose v2flyNG only when you need the V2Fly kernel route.
Processor architecture	Prefer arm64 for mainstream devices	Use the universal build when the architecture is unknown or installation is incompatible.
First connection	Approve system VPN access	The client uses the system network interface to route application traffic.
Background operation	Check battery optimization and background restrictions	Power-saving policies may stop the client’s background process.
Per-app proxy	Check app include and exclude rules	Apps outside the selected scope will not use the current proxy connection.

Desktop platforms

Linux client

Linux uses the v2rayN Desktop client. Choose deb or rpm according to the distribution’s package system, then choose x64 or arm64 for the processor. Package format and processor architecture are separate requirements and must both match.

v2rayN

Linux · deb / rpm · 7.24.1

Desktop client

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and similar distributions generally use rpm. Standard Intel or AMD desktop PCs usually use x64, while ARM development boards, workstations, and other ARM devices use arm64. If you are unsure, check the distribution information and package manager type first.

Debian / Ubuntu family

x64 deb

For common Intel and AMD 64-bit computers using the deb package system.

Download x64 deb

Fedora / RPM family

x64 rpm

For common Intel and AMD 64-bit computers using the rpm package system.

Download x64 rpm

ARM device installers

Use these links only when the system architecture is confirmed as arm64 or aarch64. The package format must still match the distribution.

Download arm64 deb Download arm64 rpm

Linux requirements and selection guide

Environment	Processor	Selection
Debian, Ubuntu, and derivatives	Intel / AMD 64-bit	x64 deb
Debian, Ubuntu, and derivatives	ARM 64-bit	arm64 deb
Fedora, Rocky Linux, AlmaLinux, and similar	Intel / AMD 64-bit	x64 rpm
RPM-based distribution	ARM 64-bit	arm64 rpm
Terminal application connectivity	All architectures	Check application parameters or proxy environment variables, not just the desktop system proxy.

Configuration Boundaries After Download

Installing the client only prepares the GUI. The subscription source, proxy connection method, and routing choices still need to be configured separately.

Client configuration management

v2rayN, v2rayNG, and v2flyNG provide GUIs for importing subscriptions, editing nodes, switching configurations, managing routes, and controlling proxy modes. The client name cannot replace a specific configuration, and installation does not generate server parameters automatically.

The kernel handles connections

The kernel reads the configuration generated by the client and handles connections. One key difference between v2rayNG and v2flyNG is their kernel route, so confirm existing protocol, transport, and routing requirements before switching clients instead of comparing interface names alone.

Proxy settings determine application connectivity

After enabling the system proxy, browsers and desktop apps that read system settings usually connect through it. Terminal programs, standalone network tools, and apps that manage their own connections may need a local proxy address entered separately. Application connectivity and route selection are separate concerns.

Subscriptions and nodes must be prepared separately

A subscription is a set of remote configuration sources, while a node contains specific server parameters. The client only stores, updates, and uses this information. Confirm the source, purpose, and configuration permissions before importing. If an update fails, check the subscription URL, network access, and client log messages separately.

Installer Selection Checklist

When several download buttons are available, use the order below to avoid treating platform, architecture, and client route as one choice.

Check the operating system

First confirm whether the device runs Windows, macOS, Android, or Linux. Each system has different file formats, permission models, and proxy settings; even when the client name is the same, installers cannot be used across platforms.

File format examples: Windows uses a compressed installer, macOS uses DMG, Android uses APK, and Linux uses deb or rpm.

Check the processor architecture

x64 generally means an Intel or AMD 64-bit desktop processor; arm64 covers Apple M-series chips, mainstream Android devices, and some ARM Linux devices. Use the architecture shown in system settings or by system commands.

On Android, use the universal build when the architecture cannot be confirmed; on other platforms, choose the exact architecture whenever possible.

Check the client route

Start with v2rayN on desktop platforms. On Android, v2rayNG is usually preferred; choose v2flyNG only when you specifically need the V2Fly kernel route. Check the protocol, subscription format, and kernel capabilities together.

The GUI client and proxy kernel are different layers; similar interfaces do not mean identical capabilities.

Check existing settings

Before updating or switching clients, record the local listening port, system proxy status, routing rules, per-app settings, and DNS options. If the port changes, update browser extensions, terminal environments, and other apps with manually entered proxy addresses.

Copying only the subscription URL may not restore all local custom settings.

Common Download Questions

These questions cover installer selection, client relationships, and update boundaries. For complete configuration steps, continue to the quick-start guide.

Should Windows users choose the v2rayN Desktop edition or the classic WPF edition?

The Desktop edition uses a modern cross-platform interface for users who want a consistent UI and future cross-platform experience. The classic WPF edition keeps the traditional Windows interface and workflow. Both are GUI clients: choose Desktop for a first installation, or consider WPF if you already rely on its familiar layout. Back up subscriptions, routing rules, and custom settings before switching editions.

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

Open System Information or About This Mac and check the chip or processor field. Apple M-series chips require Apple Silicon, meaning the arm64 installer; Intel processors require Intel, meaning the x64 installer. If the download will not start, first return to system information and verify the architecture rather than repeatedly changing proxy settings.

How should you choose between the arm64 and universal Android builds?

Most mainstream Android phones released after 2015 can use arm64, which targets today’s common processor architecture. Use the universal build if you cannot confirm the architecture, installation reports incompatibility, or the device is older. The installer architecture affects whether the app runs on the device; it does not change the subscription itself.

Should Linux users download deb or rpm?

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and similar distributions generally use rpm. Also check the processor architecture: choose x64 for standard Intel or AMD computers and arm64 for ARM devices. If the distribution uses a different package management method, consult its documentation before choosing a format provided on this page.

Does downloading the client include a ready-to-use proxy configuration?

The installer provides a GUI and configuration management, but usable server parameters or subscriptions must be prepared separately. After installation, import a legitimately obtained subscription or individual configuration, then choose system proxy, routing rules, or another way for applications to connect. If the browser works but the terminal does not, check the terminal program’s own proxy parameters and environment settings separately.

What happens to existing subscriptions and proxy settings after updating the client?

Exit the running client before updating and confirm its configuration directory and installation method. An in-place update usually keeps existing settings, but back up subscriptions, routing rules, and custom settings before changing editions, installation directories, or reinstalling. After updating, also check whether the local port changed and whether the system proxy still points to the correct listening address.

Continue configuration after installation

Next, import a subscription, choose a configuration, set the system proxy, and check the application scope in order.

View the quick start