Windows, macOS, Android, and Linux client packages

V2Ray client downloads and package selection

Choose v2rayN for desktop platforms. On Android, choose v2rayNG or v2flyNG, which uses the v2fly core. Confirm the operating system, processor architecture, and package format before downloading for the relevant platform.

Choose a package by platform Compare the three clients

v2rayN desktop client
v2rayNG Android client
v2flyNG Android alternative
Free to use
Open source

Platform packages

Choose the client for your device

Platform selections are reflected in the page URL. Read the architecture notes on the card before downloading. If the device details are unclear, check System Settings or System Information instead of guessing from the filename.

Windows

v2rayN Desktop and classic WPF editions

Windows provides v2rayN in both editions. Desktop uses a newer cross-platform UI and suits first-time installations or users who want a similar experience across desktop platforms. WPF is the long-standing classic Windows interface, with tray behavior and settings closer to established workflows. Both editions manage subscriptions, routing, DNS, system proxy settings, and local listening ports; the main differences are UI technology and desktop interaction.

Recommended

v2rayN

Windows · x64 · GUI client

Recommended for desktop platforms

If you have not used v2rayN before, start with the Desktop edition. Users with existing WPF settings and habits can continue with classic WPF. Before updating, record subscription groups, routing rules, the local SOCKS port, and system proxy mode.

Desktop edition Newer cross-platform UI, Windows x64

Download Desktop edition

Classic WPF edition Classic Windows interface for established workflows

Download WPF edition

Current version: 7.24.1

Windows system requirements and selection guide

Check	Recommended choice	Details
Processor architecture	x64	The Windows packages on this page target 64-bit x86. Confirm the system type in System Information before downloading.
Interface type	Desktop or WPF	Consider Desktop for a first installation; choose WPF if you are familiar with the classic v2rayN workflow.
Post-install setup	Subscriptions, routing, system proxy	After launch, import a valid configuration and choose a system proxy mode suited to your use case.

macOS

v2rayN packages for Apple Silicon and Intel

On macOS, use the v2rayN Desktop edition and choose a package based on processor architecture. Devices with Apple M-series chips need the Apple Silicon package; devices showing an Intel processor in System Information need the Intel package. The architecture must match the device, while subscription import, routing, DNS, and system proxy workflows remain the same.

Desktop client

v2rayN

macOS · DMG · Avalonia desktop interface

Open About This Mac or System Information and check the chip or processor field. Apple M-series devices use the arm64 package; Intel devices use the x64 package. Do not infer the architecture only from the purchase year.

Apple Silicon edition For Apple M-series chips, arm64 architecture

Download Apple Silicon edition

Intel edition For Intel processors, x64 architecture

Download Intel edition

Current version: 7.24.1

macOS system requirements and selection guide

System information	Matching package	How to identify it
Apple M-series chip	Apple Silicon DMG	When System Information shows an Apple M-series model in the chip field, use the arm64 package.
Intel processor	Intel DMG	When System Information shows an Intel model in the processor field, use the x64 package.
First launch	Confirm system permissions	When opening the app for the first time, follow system prompts for app launch and network access, then configure the system proxy.

Android

v2rayNG and v2flyNG packages

On Android, start with v2rayNG, which uses the Xray core and supports common configurations such as VMess, VLESS, Trojan, and Shadowsocks. Choose v2flyNG when your workflow requires the v2fly core. Both clients offer arm64 and universal packages; most mainstream phones released after 2015 should use arm64, while the universal edition is the fallback when the architecture is unknown.

Two core options

v2rayNG

Android · Xray core

Recommended

For Android users who need the Xray core and its related protocol capabilities. Choose arm64 first; use the universal edition if the device is older, the architecture is unknown, or the arm64 package cannot be installed.

arm64 edition For most mainstream Android phones released after 2015

Download v2rayNG arm64

Universal edition Choose when the architecture is unknown or arm64 is incompatible

Download v2rayNG universal edition

Current version: 2.2.6

v2flyNG

Android · v2fly core

Alternative

For users who specifically need v2fly core behavior or already have a compatible configuration workflow. Choose based on configuration compatibility; installing both apps is unnecessary for the same everyday connection setup.

arm64 edition For common 64-bit ARM phones and tablets

Download v2flyNG arm64

Universal edition Choose when broader processor coverage is needed

Download v2flyNG universal edition

Current version: 1.10.31

Android system requirements and selection guide

Check	Preferred choice	Details
Mainstream 64-bit ARM devices	arm64	Most mainstream phones released after 2015 use this architecture, keeping the package focused on the target architecture and size.
Architecture unknown	Universal edition	The universal package covers more architectures and suits devices with incomplete system information or arm64 compatibility errors.
Client path	v2rayNG first	Use v2rayNG for regular setups; choose v2flyNG only when the v2fly core is specifically required.

Linux

v2rayN deb and rpm packages

On Linux, use the v2rayN desktop client. Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. After choosing the format, select the correct x64 or arm64 architecture. This page does not provide a generic archive; use the distribution's package manager for installation and upgrades.

Desktop client

v2rayN

Linux · deb / rpm · x64 / arm64

Typical desktop computers use x64, while devices with ARM processors use arm64. Then choose deb or rpm according to the distribution. Before downloading, run the system's architecture query tool or check the processor type in System Information.

x64 deb Debian, Ubuntu, and derivatives

Download x64 deb

x64 rpm Fedora, Rocky Linux, AlmaLinux, and RHEL-based systems

Download x64 rpm

arm64 packages

Choose these links only after confirming that the device processor architecture is arm64.

arm64 deb arm64 rpm

Current version: 7.24.1

Linux system requirements and selection guide

Distribution or device	Package	Architecture notes
Debian, Ubuntu, and derivatives	deb	Typical Intel or AMD desktop devices use x64; ARM devices use arm64.
Fedora, Rocky Linux, AlmaLinux, and RHEL-based systems	rpm	x86_64 corresponds to x64, while aarch64 corresponds to arm64.
Desktop session	Graphical environment	v2rayN is a GUI client and requires a working desktop session with a system tray or equivalent desktop capability.

Pre-installation checks

How version, architecture, and configuration relate

The package only deploys the client program. Whether a connection works also depends on the configuration format, client support, local listening settings, routing rules, and system proxy state.

Version numbers identify updates

The versions shown on the cards are updated from the same release list. Before upgrading, record your current settings and review field changes in the new interface. When changing package architecture for the same client, do not keep both the old- and new-architecture programs as everyday entry points.

Architecture determines whether the program can run

x64, arm64, Apple Silicon, and Intel describe processor or program architectures. A mismatch commonly causes the installer to refuse execution, the program not to start, or the system to report that the app is incompatible. Check System Information first, then download the matching file.

The client determines configuration support

v2rayN targets desktop platforms, while v2rayNG and v2flyNG target Android. Their names are similar, but their platforms, interfaces, and core paths differ. Do not apply desktop installation steps directly to mobile devices, and do not confuse package selection with protocol selection.

Quick check

Four questions to ask when unsure

What operating system is the device running?Choose exactly one platform: Windows, macOS, Android, or Linux.
What processor architecture does it use?Look for x64, arm64, Apple M-series, or Intel in System Information.
Which package format does the system use?On Linux, distinguish deb from rpm; on Windows, choose Desktop or WPF.
Which client path does the existing configuration require?Use v2rayN on desktop; use v2rayNG on Android normally, or v2flyNG when the v2fly core is specifically needed.

Installation and first launch

Configuration order after download

A successful installation does not finish the connection workflow. On first launch, follow a fixed sequence so problems can be narrowed quickly to subscriptions, routing, ports, or the system proxy.

Install and launch the client

On Windows, install the selected edition; on macOS, open the DMG for the matching architecture; on Android, use a package matching the device architecture; on Linux, install deb or rpm with the distribution's package tool. During first launch, follow system prompts for required app and network permissions.

Import a subscription or configuration

Add a valid address through the client's subscription group or import feature, or import a supported share link or configuration file. After importing, check that server entries are complete and verify that the protocol, transport, and security fields were not lost due to format incompatibility.

Choose routing and local listening

Common settings include the local SOCKS listening port, LAN access, traffic sniffing, DNS, and routing mode. If the default port is in use, change it and update every app that calls that port. Start with simple routing rules, then add domain or IP matches as needed.

Start the connection and verify proxy status

Start the connection with a valid configuration, then enable the system proxy or enter the local proxy address in the target app. Verify the client log, system proxy switch, app proxy settings, and DNS behavior separately. If only one app fails, first check whether it bypasses the system proxy.

Read the complete Getting Started guide Read the configuration reference Open Troubleshooting

Download questions

Package selection and update FAQ

These questions cover interface editions, processor architectures, Linux package formats, first connections, and upgrade preparation. For client runtime issues, continue to the troubleshooting page and check logs and settings step by step.

Should Windows users download the v2rayN Desktop or WPF edition?

Desktop uses a newer cross-platform interface for users who want a similar workflow across desktop systems. WPF is Windows-only, with interface, tray behavior, and settings closer to classic v2rayN. For a first installation, start with Desktop; choose classic WPF if you already use it or need to preserve an established workflow. Both provide core settings for subscriptions, routing, DNS, local ports, and the system proxy.

How do I choose between the Apple Silicon and Intel package on macOS?

Open System Information and check the chip or processor field. Choose Apple Silicon for Apple M-series chips and Intel for Intel processors. The main difference is processor architecture; subscription and routing configuration work the same way. If installation reports a mismatch, return to System Information and verify it instead of repeatedly reinstalling the same file.

Should Android users download the arm64 or universal edition?

Most mainstream Android phones released after 2015 should use arm64 for the common 64-bit ARM architecture. Use the universal edition when the architecture is unknown, system information is unclear, or installation reports incompatibility. It supports more architectures, but does not add features beyond the same-version arm64 package.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions generally use rpm. Then check the architecture: typical Intel and AMD desktops use x64, while ARM devices use arm64. Package format and processor architecture are separate requirements, and both must match.

Why can't I access the network immediately after installation?

Installing the client only means it can run. Import a valid subscription or configuration, select a working entry, choose a routing mode, start the connection, and enable the system proxy when needed. For apps with their own proxy settings, confirm the proxy type, address, and port match the client's local listener. Check the client log first, then the system and app proxy settings; change one variable at a time.

What should I keep before updating the client?

Record subscription groups, routing rules, DNS settings, local listening ports, system proxy mode, and custom startup options. In-place updates usually preserve configuration, but interface changes or major upgrades may alter field names and defaults. After installation, verify key settings one by one, test with a single configuration, and then restore complex routing.