OFFICIAL CLIENT PACKAGES

V2Ray Client Downloads and Platform Installers

Choose a GUI client by operating system and CPU architecture. Desktop platforms use v2rayN; Android users can choose v2rayNG or v2flyNG. Versions and download links are updated from a same-origin release manifest.

Windows macOS Android Linux

4 PLATFORM TARGETS GUI CLIENT PACKAGES MANIFEST: SAME ORIGIN

PACKAGE SELECTOR

Choose a client by platform

Identify your operating system first, then verify the CPU architecture and installer format. Switching platforms also updates the URL anchor, so you can copy the current link and return directly to the selected platform.

WINDOWS · X64

Windows client

Windows uses v2rayN. The desktop and classic WPF editions share the same core configuration workflow; the differences are mainly their UI technology, layout, and operating conventions.

v2rayN

Windows · Current version 7.24.1

Recommended

The desktop edition uses a modern cross-platform UI, making it suitable for first-time installations and users who want a consistent workflow across desktop systems. The classic WPF edition follows the traditional Windows interface and suits users familiar with older menu structures, tray controls, and settings paths.

Desktop edition Desktop

x64 · Installer included in ZIP · Modern cross-platform interface

Download v2rayN Desktop

Classic WPF edition

x64 · Installer included in ZIP · Traditional Windows layout

Download the classic WPF edition

Recommendation: use the desktop edition for a new installation; choose WPF when you need the classic interface and workflow. There is no need to install both packages.

Windows system requirements and installation

Check	Requirement	Details
CPU architecture	x64	For common 64-bit Intel and AMD PCs.
Disk permissions	Writable directory	The program directory must be writable during installation and updates so runtime files can be saved.
Network permissions	Allow local listening	When the system firewall asks for the first time, grant the client the permissions it needs according to your network environment.

Download and extract. After obtaining the appropriate ZIP file, extract it completely. Do not run the installer from the archive preview window.
Finish the installation. Launch the installer and choose a writable location. After the first run, verify that the main window, log window, and system tray icon all open normally.
Import a configuration. Add a valid address in the subscription group and update the server list, or import an individual server configuration from the clipboard.
Choose a proxy method. Start with the system proxy for browsers and applications that support it. To route more application traffic, read the documentation before configuring TUN mode.

client: v2rayN · packages: desktop / wpf · architecture: x64

MACOS · ARM64 / X64

macOS client

macOS uses v2rayN. Check the device chip type before installation: choose Apple Silicon for M-series devices and the x64 installer for older Intel-based devices.

v2rayN

macOS · Current version 7.24.1

Recommended

The two DMG installers target different CPU architectures but provide the same features and configuration entry points. Choosing the wrong architecture may prevent the app from launching or cause it to run through system translation, so confirm the chip information in About This Mac before downloading.

Apple Silicon edition

arm64 · DMG · For devices with M-series chips

Download the Apple Silicon edition

Intel edition

x64 · DMG · For devices with Intel processors

Download the Intel edition

Chip check: choose arm64 when System Information shows Apple M1, M2, M3, or a later M-series chip; choose x64 when it shows an Intel Core processor.

macOS system requirements and installation

Check	Requirement	Details
Chip type	arm64 or x64	Must match the architecture of the downloaded DMG.
Applications directory	Write access required	Move the app to the Applications directory before launching it. Do not run it long-term from the mounted disk image.
Network settings	Allow proxy changes	When enabling the system proxy or virtual network mode, macOS may ask you to confirm administrative permissions.

Check the chip. Open About This Mac from the system menu, note the chip or processor field, and choose the arm64 or x64 installer.
Mount the DMG. Open the downloaded file and drag v2rayN to the Applications directory. Eject the installer image after copying is complete.
Launch for the first time. Open the client from Applications, approve the startup and network-setting permissions requested by macOS, and then check the menu bar status.
Add a subscription. Enter the subscription address and update it, select the current server, and enable the system proxy. If only some apps need proxying, continue using their individual proxy settings.

client: v2rayN · packages: dmg · architectures: arm64 / x64

ANDROID · ARM64 / UNIVERSAL

Android client

Use v2rayNG by default; choose v2flyNG when you specifically need the V2Fly core. Both clients offer arm64 and universal installers, and arm64 is usually the preferred choice for mainstream phones released after 2015.

2 CLIENTS

v2rayNG

Android · Xray core · Current version 2.2.6

Recommended

v2rayNG is the primary choice for Android, offering subscription updates, server switching, routing rules, per-app proxying, and a VPN takeover interface. Choose arm64 for the initial download; use the universal edition only when the architecture is unknown or the arm64 package cannot be installed.

arm64 edition

arm64-v8a · APK · For most recent Android phones

Download v2rayNG arm64

Universal edition

Universal · APK · Supports more CPU architectures

Download the v2rayNG universal edition

The architecture choice affects only the native components included in the installer. It does not change the subscription format, routing interface, or everyday connection workflow.

v2flyNG

Android · V2Fly core · Current version 1.10.31

Alternative

v2flyNG uses the V2Fly core and suits users who specifically need its behavior or already have compatible configurations. The basic workflow remains importing a configuration, choosing a server, starting VPN takeover, and checking the connection log. Without a specific core requirement, use v2rayNG above.

arm64 edition

arm64-v8a · APK · For most 64-bit ARM devices

Download v2flyNG arm64

Universal edition

Universal · APK · For devices with an unknown architecture

Download the v2flyNG universal edition

v2flyNG is an alternative Android client. If an existing configuration depends on specific features, read the protocol and parameter guidance provided by the service provider first.

Android system requirements and installation

Check	Requirement	Details
CPU architecture	Prefer arm64	Most mainstream phones released after 2015 use arm64-v8a.
Installation permissions	Allow this source	When Android asks you to confirm the installation source, authorize only the file manager or browser currently being used.
VPN permission	Confirm at launch	The client uses the Android VPN interface to take over traffic, and Android displays a system confirmation dialog the first time you connect.

Choose a client. Use v2rayNG in most cases; use v2flyNG when you specifically need V2Fly core behavior. There is no need to install both clients.
Determine the architecture. Download the arm64 edition first for mainstream devices. If the system reports that the package is incompatible, switch to the universal edition instead of repeatedly installing packages for different architectures.
Install the APK. Open the downloaded file and allow installation from the current source when prompted. After installation, you can disable the temporary permission for that source.
Import and connect. Import servers using a subscription address, clipboard content, or configuration file. Select a node, tap Connect, and approve the VPN permission request shown by Android.
Check background restrictions. If the connection frequently drops after the screen locks, review battery optimization and background activity rules, and allow the client to run while connected.

clients: v2rayNG / v2flyNG · packages: apk · targets: arm64 / universal

LINUX · DEB / RPM

Linux client

Linux uses v2rayN. Choose deb or rpm for your distribution, then select x64 or arm64 for the processor. Typical desktops and laptops use x64; ARM devices use arm64.

v2rayN

Linux · Current version 7.24.1

Recommended

Debian, Ubuntu, and related distributions generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. The main button provides the common x64 installer, with arm64 links listed below.

deb · x64

amd64 · Debian / Ubuntu family

Download x64 deb

rpm · x64

x86_64 · Fedora / RHEL family

Download x64 rpm

arm64 packages

For ARM64 workstations, development boards, and some low-power devices. Confirm the architecture in system information first.

Download arm64 deb Download arm64 rpm

The distribution and package format must match. Check the CPU architecture in system settings or run uname -m in a terminal: the common output x86_64 corresponds to x64, while aarch64 corresponds to arm64.

Linux system requirements and installation

Check	Common choices	Details
Package system	deb or rpm	Choose the distribution's native package format rather than judging only by the desktop environment.
CPU architecture	x64 or arm64	Choose x64 for `x86_64` and arm64 for `aarch64`.
Desktop session	Graphical desktop	v2rayN is a GUI client and requires an available desktop session with tray or window-management support.

Identify the distribution. Check system settings or /etc/os-release to determine whether the system uses the deb or rpm package system.
Check the architecture. Run uname -m. Standard PCs commonly report x86_64; ARM devices commonly report aarch64.
Install with the package manager. Open the downloaded file with the system software installer, or use the distribution's local package installation command to resolve dependencies.
Launch the GUI client. Open v2rayN from the application menu, verify that the configuration directory is writable, then import a subscription and select the current server.
Configure the desktop proxy. Whether the system proxy affects every app depends on the desktop environment and each app's own settings. If a program is not covered, check both the desktop proxy and the app's proxy options.

client: v2rayN · packages: deb / rpm · architectures: x64 / arm64

BEFORE INSTALL

Four checks before downloading

A single client may offer multiple architectures and installer formats. Complete these four checks in order to reduce problems such as failed launches, incompatibility warnings, or unrecognized packages.

Choose the operating system first

Windows, macOS, and Linux use v2rayN; Android users should generally choose v2rayNG, or v2flyNG when they specifically need the V2Fly core. Installer formats are platform-specific and cannot be mixed. Even when filenames contain the same client name, download from the panel for the matching platform.

Then check the CPU architecture

x64 is common on Intel and AMD desktop PCs; arm64 is common on M-series Macs, modern Android phones, and some ARM Linux devices. Use the architecture reported by system settings or system commands rather than inferring it from the device's release year.

Confirm the installer format

Windows provides ZIP archives containing installers, macOS uses DMG, Android uses APK, and Linux uses deb or rpm. Linux format depends on the distribution's package system; the Android arm64 and universal editions mainly differ in the range of native architectures included.

Import configuration after installation

Installing the client does not create a server automatically. After the first launch, import a valid subscription or individual server configuration, update the list, select the current node, and choose system proxy, app proxy, or TUN mode according to the apps that need coverage. Keep the sequence clear so any problem can be isolated to a specific step.

INSTALLATION NOTES

Basic configuration after installation

Downloading is only the first step. Interface layouts vary slightly by platform, but the basic path from configuration source to traffic takeover remains the same.

SOURCE

Add a subscription or individual configuration

A subscription address maintains a server list in bulk, while an individual link or configuration file is useful for temporarily adding one server. Confirm the source and permitted use before importing, update once after adding it, and check that the list shows the protocol, address, port, and remarks.

SELECT

Select the current server

Completing a subscription update does not switch servers automatically. Select the target node in the list and verify that the client's status area shows the new current server. With multiple subscriptions, filter by group or remarks first to avoid choosing a similarly named node by mistake.

ROUTE

Choose the traffic coverage

The system proxy suits browsers and desktop apps that follow system proxy settings. Android uses the system VPN interface to take over traffic. TUN can cover more apps that ignore system proxy settings, but adds a virtual network interface and extra routing rules; understand the existing network environment before enabling it.

OBSERVE

Confirm the connection through logs

After connecting, check the client log for configuration parsing, port conflicts, DNS, or handshake errors. If a webpage will not open, do not switch several settings at once; check the current server, system proxy, local port, DNS, and routing rules one by one.

DOWNLOAD FAQ

Common download and installation questions

These questions focus on version selection, CPU architecture, Linux package formats, and initial configuration after installation.

Should Windows users download the v2rayN desktop edition or the classic WPF edition?

For a first installation, the desktop edition is preferred because it uses a modern cross-platform interface with a more consistent window structure across desktop systems. If you are familiar with the traditional Windows layout or want to retain existing menu and tray workflows, choose the classic WPF edition. Both are v2rayN; the main differences are UI technology and interaction layout, and they do not need to be installed together.

How do you tell 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 field. Choose Apple Silicon for an M-series chip and Intel for an Intel processor. The installer architecture must match the device processor. On organization-managed devices, also confirm whether management policies restrict app installation or network-setting permissions.

Should Android users choose the arm64 or universal edition?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so start with arm64. If the architecture is unknown, installation reports incompatibility, or the device uses an unusual processor environment, switch to the universal edition. It supports a wider range of devices and usually contains more native architecture components.

Should Linux users download a deb or rpm package?

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. Then verify the CPU architecture: ordinary PCs are usually x64, while some workstations, development boards, and low-power devices use arm64. If unsure, consult the distribution documentation and the output of uname -m.

Why can't I connect immediately after installation?

The installer provides only the GUI and runtime components. After the first launch, import a valid subscription or server configuration, select an available node, and enable the system proxy or TUN mode as needed. If the connection fails, check the configuration, system time, local port, DNS, and proxy status in order, rather than changing several options at once.