INSTALL PACKAGE · PLATFORM PICKUP

V2Ray Client Downloads
Choose the package for your system

Choose v2rayN for desktop systems and v2rayNG for Android. Confirm the operating system first, then check the processor architecture and package format before downloading the matching file.

Four platforms organized by system v2rayN · v2rayNG · v2flyNG Free to use · Open source
Platform pickup list

Choose the current device's operating system

Each of the four platforms provides suitable clients and file formats. Switching platforms does not start a download; the file is retrieved only after you open the relevant package button.

WINDOWS · X64

Windows downloads

Windows desktop users should use v2rayN. This page provides the Desktop and classic WPF editions. Both support subscription imports, node switching, system proxy settings, routing, and log viewing; the main difference is their interface technology and layout.

1 client · 2 download options

v2rayN

Recommended 7.24.1

Windows · Desktop / WPF · 7.24.1

For a first installation, choose the Desktop edition. It uses the latest cross-platform UI with a more consistent page structure, making it suitable for users who want the current interface direction. The classic WPF edition uses the traditional Windows desktop interface, with menus and interactions closer to older versions, and suits users with established workflows.

You normally do not need both editions installed. If the existing WPF edition is stable, you can keep using it. For a new device or the latest interface, choose the Desktop edition directly.

Download Desktop edition Desktop x64 Download classic WPF edition WPF x64
DESKTOP

Choosing the Desktop edition

Best for first-time downloads, fresh deployments, or users moving to the latest interface. The download is a ZIP archive; save it, extract it completely, then run the installer from the extracted folder. Do not run it from the archive preview window.

WPF

Choosing the classic edition

Best for users familiar with traditional Windows menus, the system tray, and the classic configuration layout. If your tutorials and established workflow are based on WPF, staying with the classic edition avoids having to relearn where settings are located.

Windows requirements and package guide

Check Recommended choice Details
Processor architecture x64 Both Windows packages on this page target common 64-bit Intel or AMD processors.
First installation Desktop Use the current Desktop interface for a more direct path to future tutorials and settings updates.
Keep the older workflow WPF Retain the classic Windows layout for users with existing configurations and established procedures.
Launch permissions Start with standard permissions Standard system proxy features work directly; grant permission when prompted for virtual network adapter features.
Pre-installation checks

Three steps to confirm the package model

Download and installation failures usually come from choosing the wrong platform, architecture, or format. Check the following in order instead of repeatedly trying different files.

01

Confirm the device platform first

Windows, macOS, Android, and Linux use different installation formats, and files cannot be used across platforms. Confirm the operating system in system information, then return to the matching platform tab. Start with v2rayN on desktop systems and v2rayNG on Android.

02

Then confirm the processor architecture

On macOS, distinguish Apple Silicon from Intel; on Android and Linux, distinguish arm64 from x64 or universal packages. The chip, processor, or system architecture field in device settings is more reliable than the purchase year. Use the universal Android version when the architecture cannot be confirmed.

03

Finally confirm the package format

Fully extract the ZIP after downloading on Windows, use DMG on macOS, APK on Android, and deb or rpm on Linux according to the distribution. Downloading is only the first step; after installation, import a subscription, choose a node, and start the appropriate connection mode.

Download issues

Common package questions

Resolve version, architecture, and format issues before moving on to configuration. These six questions cover the most common download decisions.

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

The Desktop edition is recommended. It uses a next-generation cross-platform interface for first-time installations and users who want a consistent UI. The classic WPF edition preserves the traditional Windows workflow for users familiar with the older layout or existing habits. Both support common subscription, node, and system proxy operations.

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 Apple M-series chips and Intel for Intel processors. Do not infer the architecture from the device name, appearance, or purchase date.

Should Android users choose arm64 or the universal version?

Most mainstream Android phones released after 2015 should use arm64 first because the file is smaller. Switch to the universal version if the architecture is unknown, arm64 installation fails, or the device is older. The universal version supports more processor architectures; it does not provide additional features.

Should I choose v2rayNG or v2flyNG?

Android users should generally start with v2rayNG, which uses the Xray core and supports common protocols and configurations. Choose v2flyNG when the V2Fly ecosystem is needed or the configuration source specifically requires V2Fly. Installing both is unnecessary; keeping one subscription and connection state makes troubleshooting easier.

Should Linux users download a deb or rpm package?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions. Then select x64 or arm64 based on the processor architecture. Use uname -m to check it: x86_64 maps to x64 and aarch64 maps to arm64.

Why can't I connect immediately after installing the client?

The client only manages configurations and connections. After installation, import a working subscription or add a server manually, update the node list, choose a node, and enable the system proxy or TUN mode as needed. If no nodes appear after import, check that the subscription URL is complete and review the update messages and logs.