Free Downloads / CLIENT PACKAGES

V2Ray Client Downloads and Package Selection

Choose a client based on the operating system, processor architecture, and interface version. Use v2rayN on desktop platforms, v2rayNG on Android by default, and v2flyNG when you need the v2fly core.

PLATFORM / DOWNLOAD

Four-platform packages

Platform tags sync with the URL hash, so you can save an entry point for the current platform. Before installing, read the version and architecture notes on the card to avoid choosing again after downloading.

WINDOWS / V2RAYN

Use v2rayN on Windows

v2rayN offers desktop and classic WPF editions. The desktop edition uses a newer cross-platform interface and suits first-time installations or users who want a consistent workflow across platforms. The WPF edition keeps the classic Windows interface and suits users familiar with its menus, tray controls, and configuration paths.

v2rayN
Top choice Windows Desktop

v2rayN

Current version 7.24.1 · GUI client · Supports subscriptions, routing, and system proxy settings

DESKTOP / X64

Desktop edition

A newer cross-platform UI. Recommended for first-time users, those who prefer a more consistent layout, or anyone planning to move configurations between desktop systems.

Download desktop edition
WPF / X64

Classic WPF edition

A familiar, stable interface. Ideal for keeping an established workflow, with recognizable menu placement, tray controls, and traditional Windows desktop behavior.

Download classic WPF edition

SYSTEM / REQUIREMENTS

Windows installation requirements

Before downloading, confirm the system architecture, write permissions, and installation directory. After launch, the client stores configuration in the user or program directory, so avoid protected locations that a standard account cannot write to.

Check Recommendation
Processor architecture x64; the Windows packages on this page target 64-bit desktop systems
Runtime environment The desktop and WPF editions use different UI technologies; install any required runtime indicated when the application starts
Installation directory Use a fixed directory that the current account can read and write normally; avoid frequently moving configuration files
Port status If the first launch reports a port conflict, close the old client or change the local listening port

Installation sequence after download

  1. Save and extract the package. Place the program in a directory you plan to keep using instead of launching it from a temporary downloads folder each time.
  2. Launch v2rayN. If the system asks for network access, grant permission according to the networks you actually use.
  3. Import configuration. Use a subscription URL or share link to create the node list, then run a subscription update.
  4. Choose a proxy mode. Enable the system proxy or routing rules as needed, and check the logs to confirm that the configuration loaded.

BEFORE / INSTALL

Four checks before downloading

The client name, operating system, processor architecture, and package format are four separate layers. Checking them in order can eliminate most installation failures before they happen.

01

Client name

Use v2rayN across desktop platforms. For typical Android use, choose v2rayNG; choose v2flyNG when the configuration explicitly relies on the v2fly core or must match its behavior. The clients have similar configuration entry points, but their core capabilities, settings fields, and update schedules are not identical.

02

Operating system

Packages cannot be shared across operating systems. Windows uses the desktop program in a ZIP archive, macOS uses DMG, Android uses APK, and Linux uses deb or rpm. The extension shows the packaging method but not the processor architecture, so continue to the next check.

03

Processor architecture

x64 is common on Intel and AMD desktop processors; arm64 is common on Apple M-series chips, newer Android devices, and some ARM Linux systems. A mismatch often causes the installer to refuse to run, an incompatible-package warning, or an immediate exit after launch.

04

Package format and interface track

Linux also requires choosing between deb and rpm. Windows requires choosing between the newer desktop edition and the classic WPF edition. These differences concern packaging and interface technology; you do not need to keep multiple versions installed. Choose the route that fits your current environment.

FIRST RUN / CONFIG

Configuration order after installation

Installing the client only creates a graphical control environment. To establish a usable connection, import configuration, update nodes, choose a running mode, and review the logs. Do not repeatedly toggle the system proxy before importing configuration; without a valid outbound configuration, system traffic cannot be handled correctly.

Read the usage guide
  1. CONFIG SOURCE

    Import a subscription or share link

    A subscription URL is an updateable node list, while a single vmess:// or vless:// link describes one node. Preserve the complete prefix and parameters when copying, as chat apps may truncate long links automatically.

  2. UPDATE LIST

    Run a subscription update

    After adding a subscription URL, update it manually so the client can request and parse the node list. If the list is empty, first check that the URL is complete and network permission works, then review the response and parsing details in the update log.

  3. ROUTING MODE

    Choose a node and proxy mode

    Select a node with complete configuration first, then choose between the system proxy and routing rules. For a first setup, change one setting at a time; after confirming connectivity and DNS resolution, add more complex routing rules gradually.

  4. READ LOG

    Confirm status in the logs

    Runtime logs can show port conflicts, field formats, DNS resolution, and connection handshakes directly. When something fails, record the first clear error instead of changing several settings at once; this makes the source easier to locate.

DOWNLOAD / FAQ

Common download and installation questions

These questions cover release tracks, chip architectures, Android client selection, Linux package formats, and first-time configuration. If installation fails, return to the relevant platform card and verify the file type first.

Should Windows users download the desktop or classic WPF version?

Choose the desktop version first: it uses a newer cross-platform interface. Choose WPF if you prefer the classic Windows interface or want to preserve your existing workflow. Both are v2rayN and share similar core configuration and subscription workflows. Running both versions for comparison is not recommended because their default listening ports may conflict.

How can you tell whether a Mac uses Apple Silicon or Intel?

Open About This Mac from the system menu and check the Chip or Processor field. Choose the Apple Silicon build for Apple M-series chips and the Intel build for Intel processors. Use system information rather than guessing from the device's appearance, screen size, or purchase date.

Should Android users choose arm64 or the universal build?

Most mainstream Android phones released after 2015 should use arm64 first. Use the universal build when the architecture is unknown, the device is older, or arm64 installation fails. The universal build includes a wider range of processor components and follows the same feature path, but its file is usually larger.

Which should you choose: v2rayNG or v2flyNG?

Android users should generally start with v2rayNG, which uses the Xray core and covers common configuration needs. Choose v2flyNG when you need the v2fly core, already have matching configuration, or want to keep another client available. If the service configuration specifies a client or core, follow its provider's field requirements first.

Should Linux users download deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based distributions, and systems using RPM package management. Also confirm whether the device is x64 or arm64. After running uname -m, x86_64 maps to x64 and aarch64 generally maps to arm64.

Why can't I connect immediately after installation?

The client package only provides the application. Before first use, import a valid subscription URL or single-node share link, update the node list, select a node, and set the system proxy mode. If a node is visible but fails to connect, check the runtime logs and verify the local port, configuration fields, system time, and network permissions in order.