// CLIENT PACKAGES

V2Ray Client Download

Choose a graphical client installer for your operating system. Use v2rayN on desktop platforms, and choose between v2rayNG and v2flyNG on Android.

Download options are separated by platform, processor architecture, and package format. Confirm your system and device architecture first, then choose the matching file; most devices need only one client installed.

4 PLATFORMS 3 CLIENTS GUI PACKAGES

// PLATFORM SELECTOR

Choose an installer by operating system

After switching platforms, the page shows only the corresponding client, architecture details, and installation requirements. The platform identifier in the page URL can be used directly for bookmarking.

WINDOWS · X64

Windows installers

Windows desktop systems use v2rayN. The Desktop and classic WPF versions mainly differ in UI technology and layout; most users do not need to install both.

v2rayN
Recommended

v2rayN

Windows · x64 · Current version 7.24.1

v2rayN provides desktop features including subscription management, server lists, system proxy controls, routing rules, and log viewing. For a new installation, the Desktop version is generally the best choice. Users familiar with traditional Windows menus and window layouts can continue with the classic WPF version.

Desktop version Desktop

A modern cross-platform UI with a structure close to the macOS and Linux desktop versions, suitable for first-time installations.

Download Desktop version ZIP →
Classic WPF version

Uses the classic Windows desktop interface, with menu placement and controls suited to users who already know the workflow.

Download classic WPF version ZIP →

Windows system requirements

Check the system architecture and write permissions before installing.
Item Requirement Details
Processor architecture x64 Supports common 64-bit Intel and AMD Windows computers.
Installation permissions Able to run the installer Managed devices may require administrator approval.
Network configuration Allow system proxy changes When system proxy mode is enabled, the client adjusts the current user's proxy settings.

client = v2rayN · package.arch = x64

// PACKAGE DECISION

Installer selection order

The platform, architecture, and format in a filename each address a different requirement. Check them in this order to avoid repeatedly trying multiple download options.

  1. 01

    Confirm the operating system

    First identify whether the device runs Windows, macOS, Android, or Linux. Desktop platforms default to v2rayN; on Android, start with v2rayNG and consider v2flyNG only when you have a clear core preference. Installers cannot be shared between platforms.

  2. 02

    Confirm the processor architecture

    The Windows page provides x64 installers. macOS requires a choice between Apple Silicon and Intel. Android and Linux also require distinguishing arm64 from other architectures. A mismatch typically causes installation or startup failure, or an incompatibility warning.

  3. 03

    Confirm the package format

    macOS uses DMG and Android uses APK. Linux also requires deb or rpm based on the distribution. The two Windows ZIP options represent the Desktop and classic WPF versions; they are not two steps for installing the same program.

  4. 04

    Import configuration after installation

    Installation only means the client is ready. Next, import a subscription or server share link, update the server list, select an active server, and configure the system proxy, routing mode, or other connection options for your environment.

// BEFORE INSTALL

What to do after downloading

STEP A

Keep one client

Most platforms need only one graphical client. Choose v2rayN on Windows, macOS, and Linux; on Android, choose either v2rayNG or v2flyNG. Installing multiple similar clients makes configuration management and proxy-status checks more complicated.

STEP B

Complete the first launch

On first launch, the system may ask you to confirm app execution, network settings, or proxy configuration permissions. Follow the normal prompts for the current system. Organization-managed devices may restrict software installation or system proxy changes, so follow the device management rules.

STEP C

Import a subscription or share link

The client does not generate server configurations automatically. Once you have a subscription link, add it to a subscription group and update it. For an individual share link, import it from the clipboard or use the scanning option provided by the client.

STEP D

Choose a server and proxy mode

After importing successfully, select an active configuration from the server list, then enable the system proxy or the client's connection mode. If the client is running but the browser still uses the previous network path, check the active server, system proxy status, and routing rules first.

View installation and configuration guide View troubleshooting

// DOWNLOAD FAQ

Common questions about downloads and version selection

These questions explain the differences between installers. For subscription updates, proxy modes, and connection logs, continue to the usage documentation and troubleshooting page.

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

The Desktop version uses a modern cross-platform interface, making it suitable for first-time installs and users who prefer a consistent look across desktop systems. The classic WPF version retains the familiar Windows interface and controls for users accustomed to the older menu layout. Both are v2rayN, so you usually need to install only one.

If you have no preference based on past use, choose the Desktop version. Users already working with the WPF version and familiar with its menus can continue with the classic WPF version; there is no need to keep both versions installed.

How do you choose between the Apple Silicon and Intel installers on macOS?

Open About This Mac from the system menu and check the Chip or Processor field. Choose the Apple Silicon version when an Apple M-series chip is shown, or the Intel version when an Intel processor is listed. The installer architecture must match your computer's processor.

The two versions provide the same main client features. Do not infer the chip from file size or the year the device was purchased; the system's displayed chip information is the most reliable guide.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is usually the best choice. Use the universal version if you cannot confirm the device architecture, installation reports incompatibility, or the device is older.

The main difference between arm64 and the universal version is the range of processor architectures included. For most users, start with arm64 and switch to the universal version only when a clear architecture compatibility warning appears.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and derivatives generally use deb. Fedora, Rocky Linux, AlmaLinux, and other distributions based on RPM package management use rpm. You also need to choose x64 or arm64 based on the processor.

Package format and processor architecture are independent requirements. For example, an Ubuntu device with an ARM processor needs arm64 deb, while a typical Fedora desktop with an Intel or AMD processor generally uses x64 rpm.

What else should you prepare after downloading a client?

The client handles importing and managing connection configurations. After installation, prepare a working subscription link or an individual server share link, then follow the usage documentation to import and update it, select an active server, and set the proxy mode.

If the list is empty after importing a subscription, first confirm that the link is complete, then run a manual subscription update. If the server appears in the list but is not active, select the target server and enable the corresponding proxy mode.