CLIENT PACKAGES · Four-platform overview

V2Ray client downloads and package selection

Choose v2rayN, v2rayNG, or v2flyNG for your current operating system. Each entry identifies the interface version, processor architecture, and package format. Check your device details first, then download the matching installer.

Desktop: v2rayN Android: v2rayNG / v2flyNG Formats: EXE / DMG / APK / DEB / RPM
Read the user guide after downloading

PLATFORM SELECTOR

Choose a client by platform

Platform selections are reflected in the page URL, making it easy to save or share a specific download entry. If you are unsure about the processor architecture, review the detection steps and system requirements on the card before choosing the standard or compatibility package.

WINDOWS CLIENT

Windows：v2rayN

Windows offers two interface versions: Desktop and classic WPF. Both use the same core logic for subscriptions, routing, and the system proxy; the main difference is the interface technology and layout. New installations can start with Desktop, while users familiar with the traditional v2rayN interface can continue with WPF.

v2rayN

v2rayN

7.24.1
Recommended

v2rayN is a desktop GUI client for managing subscription groups, server configurations, the system proxy, TUN mode, DNS, and routing rules. After installation, you usually do not need to change advanced settings first: add a subscription, update the list, select a configuration, and enable the required proxy mode.

Recommended for new installations

Desktop edition

A modern cross-platform UI with a layout consistent across macOS, Linux, and other desktop versions. It suits first-time v2rayN users and anyone who wants a similar workflow across multiple desktop devices.

Download the Desktop version
Classic interface

Classic WPF edition

Uses the classic Windows layout, with menus and workflows closer to earlier v2rayN releases. It suits users with an established routine who prefer to keep the traditional interface.

Download the WPF version

Windows system requirements and installation checklist

Check Recommendation How to choose
Processor architecture 64-bit x86 processor Both Windows packages on this page are x64 builds. Confirm this in the system settings under “System type.”
Installation permissions Allow desktop application installation Windows may request confirmation during installation and when configuring startup at login. Follow the management policy for the current device.
Proxy settings Record the current system proxy first If another proxy tool is already in use, quit it before switching to avoid multiple programs changing the system proxy at the same time.
Configuration preparation Have a valid subscription URL ready The client does not provide server configurations. Obtain a subscription URL or an individual configuration from your service provider.

PACKAGE CHECKLIST

Package selection order

Before downloading, check four layers in order: operating system, client, processor architecture, and package format. This prevents interface versions, system versions, and chip architectures from being confused.

  1. Confirm the current operating system

    Use v2rayN on Windows and macOS; choose v2rayNG first on Android, or v2flyNG when the v2fly kernel implementation is required; use the deb or rpm v2rayN package on Linux. Do not apply another device’s choice directly.

  2. Confirm the processor architecture

    On macOS, distinguish Apple Silicon from Intel; on Android, distinguish arm64 from universal; on Linux, distinguish x64 from arm64. The operating system version cannot replace processor architecture information.

  3. Confirm the interface version or package system

    Windows Desktop and WPF are interface choices; Linux deb and rpm are distribution package-system choices. The former determines the interface, while the latter determines the installation method. They are not interchangeable concepts.

  4. Import the subscription after installation

    The client package provides only the graphical management tool. After launch, add a valid subscription URL, update the list, select a configuration, and enable the system proxy or TUN according to your needs. New users can continue with the complete setup guide.

    Read the v2rayN setup guide

DOWNLOAD FAQ

Common questions about downloads and version selection

These questions cover interface versions, chip architectures, Android client differences, and Linux package formats. For subscription import, proxy modes, and troubleshooting after installation, see the user guide and the all-platform guide.

Should Windows users download the v2rayN Desktop or WPF version?

The Desktop version uses a modern cross-platform interface and suits users who want a consistent desktop experience. The WPF version keeps the classic Windows interface and suits users familiar with the traditional workflow or who prefer its established stability. Both are v2rayN, and their core subscription import and proxy settings work similarly. For a first installation, start with Desktop; there is no need to install both.

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 field. Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. Do not infer the architecture from the purchase year, device color, or screen size; the system’s chip information is more reliable. The package architecture must match the processor.

Should Android users choose arm64 or the universal version?

Most mainstream Android phones released after 2015 can start with arm64, which has a smaller package. Use the universal version when the architecture is unknown, arm64 will not install, or the device uses an unusual processor. Both packages offer the same client features; the main difference is the range of processor architectures included.

What is the difference between v2rayNG and v2flyNG?

Both are Android GUI clients. v2rayNG uses the Xray kernel family and is the recommended Android option here; v2flyNG uses the v2fly kernel and suits users who specifically need that ecosystem implementation. Most first-time users should choose v2rayNG, while users whose existing configuration requires a particular kernel should follow the service provider’s instructions.

Should Linux users download a deb or rpm package?

Debian, Ubuntu, and derivatives generally use deb packages; Fedora, Rocky Linux, AlmaLinux, openSUSE, and other RPM-based distributions generally use rpm. After identifying the format, run uname -m to check the processor: x86_64 maps to x64, while aarch64 or arm64 maps to arm64.

What should I do after the download finishes to import a subscription?

After installing and launching the client, open the subscription group or subscription settings, add the subscription URL from your service provider, run an update, select a configuration, and enable the system proxy or TUN mode as needed. If the list is empty after updating, check that the subscription group is enabled, the URL is complete, and the current network can reach the subscription source. See the user guide for detailed steps.