Installers for four platforms

V2Ray Clients
Downloads and Version Selection

Choose v2rayN, v2rayNG or v2flyNG for your operating system. Each entry lists the interface edition, processor architecture and package type. Check your device details before downloading.

Desktop: v2rayN Android: v2rayNG / v2flyNG Core families: Xray / V2Fly

Platforms and clients

Choose your device platform

After switching platforms, only compatible clients and installers are shown. Check the architecture details on each card before downloading to reduce installation failures caused by a mismatched package.

Windows

v2rayN desktop client

Windows offers two entry points: Desktop and classic WPF. Both manage subscriptions, server configurations, routing rules and the system proxy; the main difference is the interface technology and workflow. For a first installation, Desktop is the recommended choice. Users familiar with the traditional v2rayN interface can continue with classic WPF.

v2rayN

Recommended

Windows GUI client · Current version 7.24.1

v2rayN is designed for managing subscriptions, manual settings, routing modes and proxy status from a Windows desktop. Extract the downloaded archive and run its installer, then import a subscription or enter server details. When migrating from an older version, record your existing subscription URLs, routing mode and custom settings first, then restore them one by one in the new version.

Preferred

Desktop edition

A modern cross-platform UI with a layout similar to other desktop systems, suitable for new installations and users who want future desktop features.

Processor architecture: x64
Installation method: installer inside the archive
File: v2rayN-Desktop-Setup-x64-7.24.1.zip

Download v2rayN Desktop

Traditional interface

Classic WPF edition

Retains the traditional Windows client's menus and window layout for users familiar with the older v2rayN workflow.

Processor architecture: x64
Installation method: installer inside the archive
File: v2rayN-Setup-x64-7.24.1.zip

Download classic WPF

Windows system requirements

Check	Requirements and how to verify them
Processor architecture	The Windows installer on this page is x64. Check processor and operating-system architecture under System type in Windows Settings.
Installation permissions	The installer needs to write to the application directory. Managed devices may require administrator approval.
Network configuration	After installation, import a valid subscription or configure the server manually, then select a configuration and set the system proxy mode.
Migrating from an older version	Record subscription groups, routing settings and custom ports first. Do not overwrite the directory of an older program that is still running.

macOS

Choose v2rayN by chip

macOS installers come in Apple Silicon and Intel architectures. Open About This Mac from the system menu and check the Chip or Processor field: choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. The architecture must match the device or the app may not start.

v2rayN

Desktop client

macOS GUI client · Current version 7.24.1

The macOS version of v2rayN provides a desktop interface for managing subscriptions, connection settings and routing rules. Installer architecture is the first choice; other settings can be handled after installation. Open the matching DMG, move the app to the Applications folder, then follow the system prompts for running and network configuration permissions.

M-series chip

Apple Silicon

For Macs with an Apple M-series chip. Newer devices generally use this architecture, but always confirm with About This Mac.

Processor architecture: arm64
Package type: DMG
File: v2rayN-arm64.dmg

Download Apple Silicon version

Intel processor

Intel

For devices that explicitly show an Intel processor in About This Mac. Do not rely only on the device's appearance or purchase year.

Processor architecture: x64
Package type: DMG
File: v2rayN-64.dmg

Download Intel version

macOS system requirements

Check	Requirements and how to verify them
Chip architecture	Choose an arm64 installer for Apple M-series chips and an x64 installer for Intel processors.
Applications folder	After opening the DMG, move the client to the Applications folder instead of running it long-term from the temporary mounted window.
Launch authorization	The first launch may trigger a system security confirmation. Follow the prompt in System Settings, verify the app name and complete authorization.
Proxy permissions	When enabling the system proxy or network extension, macOS may ask for the local account password to confirm the setting.

Android

Choose v2rayNG first

On Android, start with v2rayNG, which uses the Xray core family. Choose v2flyNG when you need the V2Fly core family. Both clients offer arm64 and Universal builds. Most mainstream phones released after 2015 should use arm64; use Universal when the architecture is unknown or the package is incompatible.

v2rayNG

Recommended

Android GUI client · Xray core family · Current version 2.2.6

v2rayNG supports subscription imports, QR code scanning, manual configuration, routing rules and connection logs. After installation, grant VPN connection permission, import a valid configuration and select a server from the list. The arm64 package targets mainstream 64-bit ARM devices; Universal has broader coverage for devices with unknown architecture.

Mainstream devices

arm64 edition

For most mainstream Android phones and tablets released after 2015. Prefer this version when the device is confirmed to use a 64-bit ARM processor.

Processor architecture: arm64-v8a
Target devices: mainstream 64-bit ARM devices
File: v2rayNG_2.2.6_arm64-v8a.apk

Download v2rayNG arm64

Compatibility choice

Universal edition

For devices with an unknown processor architecture or those that report the arm64 package as incompatible. The available features and entry points match the arm64 edition.

Processor architecture: Universal
Target devices: devices with unknown architecture
File: v2rayNG_2.2.6_universal.apk

Download v2rayNG Universal

v2flyNG

Alternative

Android GUI client · V2Fly core family · Current version 1.10.31

v2flyNG is intended for Android configurations that require the V2Fly core family. It is a separate client from v2rayNG; choose one based on the provider's instructions, protocol compatibility and existing configuration. Install v2flyNG when the current configuration explicitly requires V2Fly or must remain consistent with an existing V2Fly setup.

Mainstream devices

arm64 edition

For mainstream Android devices with 64-bit ARM processors. Prefer this version when the processor architecture is confirmed.

Processor architecture: arm64-v8a
Core family: V2Fly
File: v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Download v2flyNG arm64

Compatibility choice

Universal edition

Use this when the device architecture cannot be confirmed. After installation, import a subscription or manual configuration compatible with the V2Fly family.

Processor architecture: Universal
Core family: V2Fly
File: v2flyNG_1.10.31-fdroid_universal.apk

Download v2flyNG Universal

Android system requirements

Check	Requirements and how to verify them
Processor architecture	Most mainstream devices released after 2015 should use arm64 first; choose Universal when the architecture is unknown.
Installation permissions	After downloading from a browser, Android may ask you to allow installation from the current file source. Follow the system prompt to grant this one-time permission.
VPN permission	The first connection requires confirmation of the system VPN request. This permission allows the client to handle the device's network traffic.
Background operation	If the system frequently terminates connections, review the client's background activity policy in battery settings.

Linux

Choose v2rayN by distribution and architecture

Linux installers vary by package format and processor architecture. Debian, Ubuntu and derivatives generally use deb; Fedora, RHEL and derivatives generally use rpm. Most desktop PCs are x64, while ARM-based devices should use the arm64 entry.

v2rayN

Desktop client

Linux GUI client · Current version 7.24.1

The Linux version of v2rayN provides a desktop GUI. First determine whether the distribution uses deb or rpm, then distinguish x64 from arm64 using the system architecture. If you need to change the system proxy after installation, also check the desktop proxy settings, the client's listening status and the current routing mode.

Debian / Ubuntu family

x64 deb

For x64 desktop systems using deb package management, the common choice for PCs and laptops.

Processor architecture: amd64 / x64
Package format: deb
File: v2rayn_7.24.1_amd64.deb

Download x64 deb

Fedora / RHEL family

x64 rpm

For x64 desktop systems using rpm package management. Confirm that the distribution supports rpm packages before installing.

Processor architecture: x86_64
Package format: rpm
File: v2rayN-7.24.1-1.el10.x86_64.rpm

Download x64 rpm

ARM devices

arm64 installer

When the device architecture is shown as aarch64 or arm64, choose the matching package for your distribution below.

Download arm64 deb Download arm64 rpm

deb file: v2rayn_7.24.1_arm64.deb
rpm file: v2rayN-7.24.1-1.el10.aarch64.rpm

Linux system requirements

Check	Requirements and how to verify them
Package format	Debian and Ubuntu families generally use deb; Fedora and RHEL families generally use rpm.
Processor architecture	`x86_64` corresponds to x64; `aarch64` or `arm64` corresponds to arm64.
Desktop environment	The GUI client requires an available desktop session. A command-line-only environment is not suitable for the desktop programs provided here.
System proxy	Proxy settings are located in different places across desktop environments. After enabling the client, check that the desktop environment is using the intended settings.

Pre-installation checklist

Match the platform first, then configure the client

The installer only handles program installation. Subscription URLs, server parameters, routing rules and system proxy status must be configured separately after installation.

Check the operating system

Confirm whether the device runs Windows, macOS, Android or Linux. Each platform has a different program structure, permission model and installation process, so installers cannot be used across platforms.

Check the processor architecture

x64, arm64, Apple Silicon and Intel are key installer selection fields. System Settings or system information tools provide accurate results; do not infer the architecture from the device's purchase date alone.

Keep configuration details

Before upgrading or migrating, record subscription URLs, manual server parameters, routing mode and local ports. Restore them one by one after installation to avoid mixing a program update with configuration changes.

Complete the first connection

After launching the client, import a valid configuration, select the entry to use, then enable the system proxy or mobile VPN service. If the connection fails, check the client logs first, followed by system proxy and DNS settings.

Common download questions

Installer and architecture selection

This section covers the most common download-stage questions about editions, chips, architectures and initial setup. For connection issues, continue to the troubleshooting page and check by symptom.

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

The Desktop edition uses a modern cross-platform interface for new installations and users who want the newer layout. Classic WPF retains the traditional Windows workflow, with menus closer to the older experience. You do not need both; if unsure, start with Desktop, or choose WPF if an established workflow matters more.

How do I know whether to download the Apple Silicon or Intel version for macOS?

Open About This Mac from the system menu and check the chip or processor details. Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. This choice depends only on the device chip, not the subscription type, server protocol or routing mode.

Should Android users choose arm64 or Universal?

Most mainstream Android phones released after 2015 should use arm64. If system information confirms a 64-bit ARM processor, download arm64 directly. If the architecture is unknown or installation reports that the package is incompatible, use Universal instead. Both packages provide the same client features and entry points.

Should Linux users choose deb or rpm?

Debian, Ubuntu and derivatives generally use deb; Fedora, RHEL and derivatives generally use rpm. After choosing the format, check the processor architecture: common desktop computers are usually x64, while devices showing aarch64 or arm64 should use the corresponding arm64 package.

Why is there no ready-to-use configuration after installing the client?

The client reads, manages and runs configurations; the installer does not include server parameters. After installation, import a valid subscription link or manually enter the address, port, user ID, transport method and security settings supplied by the server. Update the list, select a configuration, then enable the system proxy or VPN service.

Continue configuring after installation

Follow the complete workflow for importing subscriptions, choosing a routing mode, setting the system proxy and verifying the connection.

View the Getting Started guide Open Troubleshooting

V2Ray ClientsDownloads and Version Selection

Choose your device platform

v2rayN desktop client

v2rayN

Desktop edition

Classic WPF edition

Windows system requirements

Choose v2rayN by chip

v2rayN

Apple Silicon

Intel

macOS system requirements

Choose v2rayNG first

v2rayNG

arm64 edition

Universal edition

v2flyNG

arm64 edition

Universal edition

Android system requirements

Choose v2rayN by distribution and architecture

v2rayN

x64 deb

x64 rpm

arm64 installer

Linux system requirements

Match the platform first, then configure the client

Check the operating system

Check the processor architecture

Keep configuration details

Complete the first connection

Installer and architecture selection

V2Ray Clients
Downloads and Version Selection