// CLIENT PACKAGES

V2Ray Client Download and Version Selection

Use v2rayN on desktop platforms and generally choose v2rayNG on Android. Confirm the operating system, processor architecture and UI edition before downloading the matching package.

View Platform Packages View First-Time Setup
v2rayN · DESKTOP v2rayNG · ANDROID GUI CLIENTS

// PLATFORM SELECTOR

Choose a Package by Platform

Each of the four platforms lists compatible clients, primary packages, alternative architectures and baseline system requirements. When you switch platforms, the page URL updates to the corresponding anchor.

// WINDOWS PACKAGES

Windows：v2rayN

The Desktop edition uses a newer cross-platform UI and suits first-time installations or users who want a consistent desktop experience. The classic WPF edition retains the traditional Windows interface and layout for established workflows. Both entries are v2rayN; the main difference is the UI technology and interaction layout.

v2rayN
Recommended

v2rayN

A Windows x64 GUI client with Desktop and classic WPF interface editions.

Desktop edition

Newer cross-platform UI. Preferred for first installations and users who want the updated interface.

Download Desktop edition
7.24.1 v2rayN-Desktop-Setup-x64-7.24.1.zip
Classic WPF edition

Classic, stable interface. Choose it if you know the older menu structure or need to preserve an existing workflow.

Download WPF edition
7.24.1 v2rayN-Setup-x64-7.24.1.zip

Windows system requirements and installation order

Check Recommendation
Processor architecture The Windows packages on this page target x64 systems. Confirm this in the System type field under System Information.
Installation permissions The installer needs to write to the application directory. If a managed device requests permission, follow the device's administrative policy.
First launch After launching, import a subscription or individual configuration, update the subscription group, select a profile, and start the core.
System proxy Launching the client does not route system traffic automatically. Enable the system proxy or configure an application proxy according to your needs.

// AFTER DOWNLOAD

First-Time Setup Order After Downloading

Installing the client is only the preparation stage. Before using it, import a configuration, choose a profile, define the proxy scope and check the connection status.

STEP 01

Install and launch for the first time

Install the package that matches the system and architecture. After the first launch, confirm that the main client window opens normally. Do not change the port, DNS, routing and system proxy all at once. Handle one step at a time to make issues easier to isolate.

STEP 02

Import a subscription or configuration

Add a valid URL in the subscription group and update it, or import an individual vmess, vless or trojan configuration. After importing, check that the protocol, server address, port and transport settings were recognized correctly, then select the profile to run.

STEP 03

Start the core and set the proxy scope

After starting the core, choose a system proxy, in-app proxy or routing rules according to your needs. Direct, proxy and block rules affect the final access path. For an initial setup, use the client's standard routing mode, confirm the connection, and then add custom rules.

// SUBSCRIPTION

Importing a subscription does not connect automatically

After adding a subscription URL, update it, open the relevant group and select a profile. If the update fails, first check that the URL is complete, the device time is accurate and the current network can reach the subscription source. Do not change the client, port and protocol repeatedly during one troubleshooting session, or the real fault will be difficult to identify.

View the subscription import guide

// ROUTING

Check the system proxy and routing rules separately

The system proxy determines whether an app sends requests to the client; local routing rules determine whether the client uses a direct connection, proxy or block after receiving a request. If the client is running but the browser still cannot connect, check the selected profile, local listening port, system proxy status and routing mode separately rather than watching just one switch.

Read the protocol and core reference

// UPDATE PATH

Record key settings before updating

Before a major-version update, record the subscription groups, local listening port, routing mode, DNS options and custom rules. After installing the new version, verify each setting against your current needs. If you are only troubleshooting a connection, check the client logs and error messages first; upgrading should not be the only remedy.

View troubleshooting questions

// PACKAGE NOTES

Four Checks for Choosing a Package

01

Choose the client before the file format

Use v2rayN on desktop platforms, v2rayNG as the usual Android choice, and v2flyNG when you specifically need the v2fly core. Identify the client first, then choose the architecture and package format within the same card to avoid downloading similarly named files with different purposes.

02

Architecture names may vary

x64, x86_64 and amd64 usually refer to the same class of desktop processor architecture; arm64 and aarch64 usually refer to the same 64-bit ARM architecture. Package filenames and system information may use different wording, so match the meaning rather than looking for an identical string.

03

Use the universal edition for compatibility checks

The Android universal edition supports a wider range of architectures and suits devices with unknown specifications or cases where a dedicated package cannot be installed. If the device is confirmed to use arm64, prefer the arm64 package. The universal edition does not add features; the main difference is its processor architecture coverage.

04

Continue checking the configuration after installation

A client opening successfully only shows that installation is largely complete. You still need to check the subscription, protocol parameters, active profile, system proxy and routing rules. If a port is already in use, identify the process holding it or change the local listening port, then update any application proxy settings that depend on it.

// DOWNLOAD FAQ

Common Questions About Downloading and Installation

These questions cover versions, architectures, package formats and first launch. For subscription updates, routing rules and connection errors, continue to the common questions page.

Should Windows users choose the v2rayN Desktop edition or the WPF edition?

For a first installation, choose the Desktop edition with its newer cross-platform UI. If you are familiar with the classic Windows interface or an existing maintenance workflow depends on the WPF menu layout, continue with the classic WPF edition. Both are v2rayN with essentially the same core purpose; there is no need to install and run both.

How do I know whether to download the Apple Silicon or Intel package for macOS?

Open System Information and check the chip or processor field. Choose Apple Silicon arm64 for Apple M-series chips and Intel x64 for Intel processors. Do not rely only on the device name, since similar-looking models may use different processors.

Should Android users download arm64 or the universal edition?

Most mainstream Android phones released after 2015 should use arm64 first. It contains resources for the matching architecture only, keeping the file focused. Download the universal edition if the architecture is unknown or the arm64 package reports incompatibility. The main functionality is the same; the difference is processor architecture coverage.

How should I choose between v2rayNG and v2flyNG?

For typical Android use, choose v2rayNG with the Xray core. Choose v2flyNG when you specifically need the v2fly core, maintain existing configurations according to v2fly behavior, or the service documentation specifies that core. Before importing, confirm that the protocol and transport parameters are compatible.

Should Linux users choose a deb or rpm package?

Use deb for Debian, Ubuntu and derivatives; use rpm for Fedora, RHEL-based systems and distributions using rpm. After identifying the package format, check whether the system is x86_64 or arm64. Both checks must be correct for the package to match the environment.

Why can't I connect immediately after installation?

The package only installs the client. After the first launch, import a valid configuration or subscription, update the subscription group, select a specific profile and start the core. To connect a browser or another app, enable the system proxy or point the app proxy to the client's local listening port.