V2Ray client installers

V2Ray Download: Choose a Client by Platform

Use v2rayN on desktop systems. On Android, choose v2rayNG; use v2flyNG when you need the V2Fly core path. Confirm your operating system and CPU architecture before downloading the matching installer.

Free to use Open source Graphical clients Chinese configuration guides

Platforms and installers

Choose the current device platform

The selected platform is preserved in the page URL. Copy the current URL to open the download panel for that operating system directly.

Windows client

v2rayN: Desktop and classic WPF

Both interface versions support subscription groups, server lists, the system proxy, routing rules, and log viewing. For a first installation, Desktop is a good starting point; users familiar with traditional Windows menus and WPF workflows can continue with the classic version.

Recommended Desktop

v2rayN

7.24.1

v2rayN is the primary graphical client for Windows. Desktop uses a newer cross-platform UI with layouts similar to the macOS and Linux versions; WPF retains the classic Windows interface, with menu locations and workflows suited to users accustomed to older releases.

Desktop edition

A newer cross-platform interface for first-time installations and users who want a consistent desktop workflow.

Download the Desktop edition
Classic WPF edition

A familiar, stable interface for users accustomed to server lists, tray menus, and traditional settings windows.

Download the classic WPF edition

Windows requirements and installation steps

Check Recommendation Details
System architecture x64 The Windows installers on this page target common 64-bit desktop devices.
Disk permissions Allow writes to the configuration directory Subscriptions, routing rules, logs, and interface settings must be saved in the client configuration directory.
Network settings Enable the system proxy as needed Starting the client does not enable the system proxy automatically. Confirm its current status from the tray menu.

After downloading the ZIP, extract it completely before running the installer from the extracted directory. Do not launch it from the archive preview window. Once installation is complete, open v2rayN and import a subscription or a single server configuration. Select a server and set the routing mode. Enable the “system proxy” when browsers and other applications that support system proxy settings should use the current configuration. To route traffic from more applications, read the guide’s TUN mode section.

First launch

Complete the basic setup in four steps

Installing the client is only the first step. Confirm the subscription, server selection, routing mode, and system-level traffic handling in order. Start with the smallest working configuration, then adjust TUN, DNS, or custom rules.

1

Import a subscription or single configuration

Subscription URLs are usually added under “Subscription groups” or “Subscription settings.” After entering a name and URL, run an update so the server list is written to the current group. A single share link can be imported from the clipboard; Android also supports QR-code scanning. After importing, check that the protocol, address, port, and transport are shown completely.

2

Choose a server and active group

When multiple subscriptions exist, first confirm which group you are viewing, then select the server to use. Desktop clients usually let you set an active server from the server list, while Android lets you select one from the configuration list. Latency tests only help assess the connection path and do not represent actual download speed; consider stability and everyday results as well.

3

Set routing and proxy mode

For the first connection, use the client’s standard rules mode and change it only after confirming basic connectivity. Rules are matched from top to bottom, and the corresponding outbound is used after a match. Common rules include direct access for geosite:cn and geoip:private, while other domain sets can use proxy outbounds as needed.

4

Check system proxy or VPN status

After starting a desktop client, enable the system proxy if needed. Android requires confirmation of system VPN authorization on the first connection. If a browser connects but other apps do not, check whether those apps read system proxy settings. If no app has traffic, review the client logs first, then check the local port, active server, and system time.

View the complete configuration guide Read advanced configuration

Installer selection

The difference between architecture, format, and client

Installation failures are usually caused by a mismatch between the platform, processor architecture, or package format, not by configuration. Make these three checks before downloading.

x64 and arm64

x64 is common on Windows PCs and traditional Linux desktops. arm64 is common on Android phones, Apple M-series devices, and some ARM Linux systems. Different architecture installers contain code for different processors, so do not rely on the version number in the filename alone.

DMG, APK, deb, and rpm

DMG is for macOS, and APK is for Android. deb and rpm are two Linux package formats determined by the distribution’s package system. For Windows, this page provides a compressed installer package; extract it completely before running it.

v2rayNG and v2flyNG

Both are graphical Android clients, but they use different core paths. v2rayNG uses Xray and suits most common configurations; v2flyNG uses V2Fly and is an alternative for configurations in that ecosystem. Manage subscriptions separately in each client to avoid confusing which configuration is actually running.

Updates and migration

Update the client while keeping its configuration

Client updates can usually retain existing subscriptions and routing rules, but the configuration directory, desktop edition, and system permissions may change. Exit the running program before updating so configuration files are not still in use.

On desktop, note the current subscription group, active server, system proxy mode, local listening port, and custom routes. On Android, check the subscription URL, per-app proxy list, and VPN permission. After backing up, install the new version and confirm each item has loaded.

Update checklist

  • Exit the current client and tray process
  • Back up subscription groups and custom routes
  • Choose the same platform and processor architecture
  • Run one subscription update after installation
  • Check the system proxy, VPN, or TUN status
  • Review the logs to confirm the configuration loaded successfully

Download FAQ

Installer selection and update guide

These questions cover the clients and installers provided on this page. For more detailed guidance on subscriptions, routing, DNS, TUN, and troubleshooting, continue to the tutorials and FAQ.

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

Desktop is the newer cross-platform interface for first-time installations and users who want more consistent workflows across Windows, macOS, and Linux. The classic WPF edition retains the traditional Windows interface, with server lists, tray menus, and settings windows positioned more like older releases.

Both versions support subscription import, server selection, the system proxy, and routing configuration. The choice mainly depends on interface preference, and both should not be run at the same time. Exit the current client and back up important subscription groups and custom rules before switching.

How can macOS users tell whether to choose the Apple Silicon or Intel installer?

Open the system menu in the top-left corner and select “About This Mac.” If the Chip field shows an Apple M-series chip, choose the Apple Silicon installer; if the Processor field shows Intel, choose the Intel installer. Do not infer the architecture from the device’s age, appearance, or screen size.

After downloading the correct DMG, move the app to the Applications folder. When enabling the system proxy or TUN-related features for the first time, follow the system prompts for network permissions, then return to the client and confirm the switch state.

Should Android users download the arm64 or universal version?

Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is the preferred choice. The arm64 package contains only the matching architecture components. If the device architecture is unknown or installation says the app is incompatible, choose the universal version.

The arm64 and universal clients offer essentially the same features; the main difference is the processor architectures included in their installers. After installation, import a subscription, select a configuration, and confirm Android VPN connection authorization.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and derivatives use deb. Fedora, RHEL, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. Then determine whether the device is x64 or arm64; both conditions must match for the correct installer.

Common PCs usually report x86_64, which corresponds to x64; ARM devices often report aarch64, which corresponds to arm64. Prefer the system package manager during installation so the distribution can handle dependencies properly.

Do existing configurations need to be deleted before updating the client?

Usually not. Exit the client first and back up subscription groups, routing rules, custom outbounds, and other important settings. After installing the new version, check that the original configuration directory is recognized, run a subscription update, and confirm the active server and proxy mode.

When switching from Windows WPF to Desktop or updating across several versions, the interface layout and configuration directory handling may differ. Keep the old directory for now rather than deleting it; organize old files only after the new version passes connection tests and the rules work correctly.

V2Ray client download